No idea, no mention in the super basic guide that came with it.
There is a good chance the software doesn’t know to wait/delay messages and both the logger and the rs485 adapter try to get data at the same time and I assume that’s happening with the bogus data.
But the rs485 adapter reads the data just fine, only the logger is tripping.
Check this out: RS-485 Wiring with Circular Connector : Ginlong Solis
Is it similar to what you said about the resistor?
I know this is connecting 3 inverters together using one rs485 cable but maybe same needed for me?
(Not sure that the IN and OUT mean as there is only one COM port on the inverter)
Also does the wire size matter, I used a standard 6 core alarm cable that I had laying around?
I’m not familiar with HA, but if HA has a way to insert a delay between requests, you could try
that.
Modbus requires each of the two devices to have a unique address. Modbus is a polled system.
i.e. the slave doesn’t respond unless it’s polled by the master.
Yes tried delays of 15s to 60s, did not make a difference from Home Assistant but that doesn’t mean the wifi logger is doing a delay when it expects to be the only slave.
I have also tried different slave IDs in Home Assistant because they can be set there.
Here: https://electrical-engineering-portal.com/correct-cabling-modbus-rs485#connection-port it says to use shielded twisted pairs, use a 3 pairs from the cat5/6 cable for the 3 wires?
It also says 120ohm resistor not needed if the run is less than 50m, my rs485 cable is 150cm.
The article does mention a terminator, but they’re simply mentioning the need for one.
Some devices have the terminator built into them. In that case there will be either a physical connection
e.g. a jumper on a pair of pins, or a software command that “connects” the terminator to the bus.
I thought perhaps the datalogger might the the type controlled by a software command.
WRT the ground connection, yes. It should be connected only at one end.
Size, not really.
What’s important here is impedance. The Modbus spec calls for an impedance of 120 Ohms.
So no need for the GND cable to be connected on the rs485 adapter since the GND of the logger itself is connected to the inverter?
A 1 second delay should be more than enough. All that’s needed is enough time for the device to respond.
You lost me there. 
Not quite sure what you mean.
Yes, for such a short run a terminator is typically not needed.
What you want to avoid is a ground loop. IOW, everything is grounded, but at only one point.
e.g. you want to avoid this:
You want either of the 2 grounds shown, but not both.
I might have this then since isn’t the USB RS485 adapter grounded on the usb side already (connected to the RPI4)? Is there a need to ground it to the logger also?
i.e. Should I only connect the A and B wires from the RS485 adapter to the wifi logger?
I was saying I have no idea what the official Solis wifi logger is doing since I have no visibility on its workings.
Yes. As I mentioned a bit earlier…
Could that cause the bogus data? I can try it real quick and find out I guess
Yes. Electrical “noise” can cause lots of oddball stuff to happen. Bogus data is just one of them.
Running without the GND on the rs485 adapter now and data is coming through from both devices.
Can take a while to replicate the odd behaviour so will continue to monitor it and report back, many thanks for the assist 
YVW,S.
Here’s hoping you nailed it!
If you run the datalogger by itself, i.e. with the RS-495/USB interface not connected, do you still get the spikes?
Nope, all good then once I disable the polling from Home Assistant even with the cables still connected.
Ya lost me again. What happens when the cables are disconnected?
All works as expected and no spikes in the data like you can see in my graph above.
What results do you get when you run the RS485-USB interface by itself?