Closed karolisju closed 3 months ago
Can it be that you have some wifi networking issues? The erros are reported for both MQTT and Modbus, but these connections are unrelated with each other.
Thank you for replay.
I did another test. started ping command from PC where debugging, to Inverter and to MQTT broker. Launched local-run.sh (this time haven't got DeyeMqttPublisher error)
so it makes sense why randomly getting DeyeMqttPublisher - ERROR, maybe it is possible to increase timeout or retry?
and any clue about this “DeyeModbusTcp - ERROR - Modbus device address does not match.”? (this error always repeats)
and any clue about this “DeyeModbusTcp - ERROR - Modbus device address does not match.”? (this error always repeats)
It indicates that the Modbus response contains unexpected values. Perhaps your inverter model uses different Modbus registers for date/time data?
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
Hello, help is appreciated or some hint where to look.
Hardware :
Software :
For a couple of days trying to figure out where is a problem, errors:
I guess the issue/error is related to writing inverter settings. First of all tried the function timeofuse (according to documentation), but there are no errors and nothing changes in the inverter. loglevel=debug
After enabling the feature flag “DEYE_FEATURE_SET_TIME=true” saw errors that Time could not be set and I guess due to Modbus error. Tried different protocols tcp and at (Inverter metrics receiving over MQTT)
Config.env
Logs: