I found several problems with my config. serial slave id was wrong. And also Type “holding” was wrong.
I used minimalmodbus python code to check something on my Docker host system (Pi).
Many thanks for @Sebastian_A post about item / thing configuration.
I’m still not finished with my configuration and need to debug further. But at least received some values.
Can you expand on this, what is your configuration? Earlier you mentioned dev/tty style port names, not Windows COM ports.
What have you got connected to where?
I don’t mean Windows COM ports, but ids which I set for the modbus devices.
But I think what I intend to do can’t work actually since the inverter is the Modbus master.
The Openhab binding act as Modbus Master too, right? And the bus can only have one master.
That’s probably the reason why it doesn’t work.
Most of these inverters can run a “private” serial Modbus, where the inverter is master and one or more external meters are the slave(s). You cannot hack into that bus from openHAB.
The inverters usually provide a completely separate “public” Modbus interface, often TCP/IP, which you can use with openHAB etc. The inverter plays the slave role on this interface. The inverter might well provide a copy or a version of some of the info it gets from the external meter.
Sorry for digging up this thread but I have the same issue.
I use a hybrid inverter from Aiswei/Solplanet with a direct Modbus connection between inverter and SDM630 smart meter and a CAN Bus connection between inverter and battery.
I would like to get some data points that I can not get via the meager developer debug interface with the http binding.
The inverter has a wifi stick with an ESP32 that is connected via RS485 to the inverter (It uses an usb port for connection). I guess this wifi stick is a modbus master and the inverter and smart meter are slaves.
Now it is problematic to poll between the polls of the wifi stick master because it polls very frequently (<5s).
Fortunately sometimes I get lucky and get data without an interruption and resulting CRC error.
I could live with this luck based polling but it is annoying to see all these CRC errors on the logviewer.
Can I maybe just hide the Modbus errors in the logviewer? Also the Modbus Things flicker between online and offline (from CRC errors), which is not looking nice…
This thread is 1 year old. Maybe there are new ways now?