Closed jwillmer closed 7 months ago
have you restarted Home Assistant after starting the docker-container? however you should always be able to see the published MQTT messages via something like MQTT Explorer
also, when setting the Waveshare device to Work Mode
TCP Server
the Dest. IP/Domain
and Dest. Port
are disabled
This is what I configured for master (IP and Gateway I removed in the screenshot)
the web interface really doesn't work well so I recommend using the VirCom (Windows) tool (works in Windows for ARM on macOS as well).
However I would go ahead and check MQTT Explorer first to see if it receives anything.
Great. Now I see both packs in Home Assistant. Sadly all sensors are marked unavailable.
see my previous message: check if the docker container actually retrieves data from the packs (with something like MQTT Explorer)
Ok, will do but can i be as simple as wrong wiring? Depending on the patch cable the colors are mapping to different pins:
MQTT Explorer:
should look like this in MQTT Explorer:
as for the wiring:
I used the 568B scheme
I also used that schema. I need to test my wiring since I used (cheap) keystone jacks. I will report back once done.
Resolved! The stupid keystone jacks did not work with flexible cables and I even had to bend the cutting blades to work with solid cables. But now it works and looks beautiful!
Is it required to set destination IP and port in Waveshare RS485?
I followed the setup and all seams to be working but I don't see any new device in my Home Assistant MQTT integration. Is there a way to confirm data is actually received by the seplos-mqtt-remote-rs485 container?