veista / nilan

Nilan integration for Home Assistant
Apache License 2.0
46 stars 11 forks source link

No Response received from the remote unit/Unable to decode response #14

Closed gllmlbrt closed 1 year ago

gllmlbrt commented 1 year ago

Hi, Currently on 1.1.1B, and since release 1.0.25 I have after many hours of perfect function and error as follow:

Logger: homeassistant.components.modbus.modbus
Source: components/modbus/modbus.py:391
Integration: Modbus (documentation, issues)
First occurred: 05:58:02 (1 occurrences)
Last logged: 05:58:02

Pymodbus: Nilan: Modbus Error: [Input/Output] No Response received from the remote unit/Unable to decode response

And then all entities generate an error like this one:

Logger: custom_components.nilan.device
Source: custom_components/nilan/device.py:2204
Integration: Nilan (documentation, issues)
First occurred: 05:58:02 (988 occurrences)
Last logged: 08:42:34
Could not read get_time

Reloading the integration does not fix it. Restarting Hass core does not fix it. To make it work again I need to reboot the bridge and then reload the integration. Then it work flowlessly for some 8-10 hours and crashes again...

I will try now to revert to pre-1.0.25 and see over long time if it occurs again...

My device is Comfort series we just added to the supported devices. This did not occur before 1.0.25 ( in the beta versions we tested before).

veista commented 1 year ago

That is weird. I have it running fine. It must be related to the bridge somehow. I remember you were using some odd rs485 tranceiver, if it is possible you could change it to max485 with de-re support.

veista commented 1 year ago

P.s. there shouldn't be anything different in the newest version in your case.

gllmlbrt commented 1 year ago

Issue appears to have disappeared in 1.1.2.B. maybe a coincidence... You can close the issue

veista commented 1 year ago

Ok, it must be a coincidence.