Waveshares - no link on Server?

[solarjones]

Hi,
Today I wired 2x Waveshare RS485 to POEs with some success, but feel I may have missed something in the config as the 'server' does not show a solid blue Link light. But everything appears to be working :)

• Solis Cloud via the Solis App is working (needed a datalogger reboot (unplug/plug) as it initially hung after ~20mins)
• HA using SolaX Inverter Modbus integration appears to be up and running to (early days - just spotted it had set my inverter to Backup mode without my say so. Had to set it to Timed Charge/Discharge in HA).

My setup:
Solis Hybrid inverter with an S2-WL using LAN datalogger.
Waveshare - Server IP .202 (labelled GW .202 as this is the gateway)
Waveshare - Client IP .203 (labelled DLG .203 as this is the datalogger)
HA - IP .235
Vircom - IP .120

Vircom configs:

Server:

Server advanced:

Client:

Client advanced:

In HA, I've successfully configured the integration and have telemetry coming through which is great. Pointed it at the Waveshare Server on .202.

So, the question I've got is why don't both my Waveshares have the solid blue Link light on?
Client: LINK = solid Blue
Client: ACT = flashes Blue with traffic
Server: LINK = solid Green
Server: ACT = occasionally flashes blue with traffic

Thanks for all your help, I would not have been brave or knowledgeable enough to try this otherwise!

[alienatedsec]

@solarjones Is your network liking Static IPs?

[solarjones]

Yes, playing nicely with other devices. My thinking was having DHCP allocate IPs could cause HA not to find the Waveshare Server. I assume that is the correct 'target' for the HA to use?

[alienatedsec]

@solarjones despite cabling, it should not be an issue unless you are using a mixed environment (DHCP Range +Static Range) If those are overlapping and you assigned the IP, which is in the DHCP range, it could be creating conflicts and disconnecting either device with the same IP.

[alienatedsec]

@solarjones is your data logger linked to the Server or Client?

[alienatedsec]

@solarjones potential problem

I noticed you are using two pairs of twisted cabling. For RS485 it's recommended to use a pair which is twisted but for both A and B on one twisted pair. So, your blue and white/blue twisted cables should be used for A(blue) and B(white/blue)

[solarjones]

Ah, ok, thats a rewire then :) In my excitement I didn't realise thats how to do it.
Would that make the difference on the LINK status? If the signals were 'bad', wouldn't I see very odd data on both Solis Cloud and HA?

[alienatedsec]

@solarjones it is likely to create interference in noisy (electrical) environments and at long distances, if not wired the proper way. You can find out more about it on the web or some quickly found details are available here.

I also used earthing, but it may not be necessary.

[alienatedsec]

@solarjones I just realised that at the very beginning, my setup acted similar (green instead of the blue LED). Maybe worth considering leaving it running (HA + Datalogger) as is overnight and check it again in the morning.

[solarjones]

Overnight running of both HA + data logger didn't change LED status.

[alienatedsec]

@solarjones Another suggestion is to increase some values and match the settings according to my screenshots on the main page. It's also worth comparing the firmware version V1.452 is definitely on both devices - I can't see it from your screenshots.

You could also swap them around and see if the same green LED is going to be on the other device if you change their roles and connect differently. You can easily unplug those green connectors and plug one into another without unscrewing wires.

[solarjones]

I increased the values using the exact same numbers as your screenshots. No change in LED status. Firmware versions are identical.

[solarjones]

I've just swapped the client/server units and reconfigured Waveshare. The lack of blue LED followed the unit. I'll leave it running today and if no change this evening, I think it could be a faulty LED light in one of the Waveshares.

[alienatedsec]

@solarjones that is unlucky - however, if everything works as expected, then you should be fine. You could order another one and return this faulty unit after receiving the replacement.

[solarjones]

Yep, Amazon are great!

2x LINK lights. All is well. Thanks for your guidance and help!

[solarjones]

Next improvement will be to add an earth from each Waveshare and install the Emergency Power Supply (or whatever its called) plug/cable to a double socket and back to earth. Its a shame there isn't a function like the Tesla Gateway to allow the inverter/batteries to power the house during an outage, but wouldn't want to pay Telsa prices for the solution!

[magichew]

Sorry to jump in here, I haven't purchased the Waveshare devices but I have a question about the above screenshots. Are those screenshots taken from the device's web server or is there an application to install to get to the config?

[solarjones]

Hi - they are from the Windows based app (Vircom) which is required for the initial setup. More info here https://www.waveshare.com/wiki/RS485_TO_ETH_(B)

[alienatedsec]

@magichew those screenshots are from the app VirCom. It allows you to configure Waveshare devices even if they don't have an IP address assigned. You can also change some advanced settings, which are not available via the web interface.

[magichew]

Thank you for confirming that. Is the software purely for configuration and not something that will be regularly needed to make them work?

@alienatedsec will I need to configure advanced settings if I am following your set up?

It's not a problem to run a Windows VM, I just want to know what I'm getting myself in to.

[alienatedsec]

@magichew you only do the configuration once, and it's not needed to run in the background or even on a separate VM.

[magichew]

@alienatedsec That's great. Thank you.