Something is blocking modbus/NIBE integration

Configuration
1

Hello,
I had a NIBE heat pump running on Modbus for more than a year without any problems. About a year ago, it stopped working, though I’m not sure exactly when it happened.

Recently, I checked whether Modbus is still running on the NIBE, and it is fine. I also installed a new instance of HASS on the same network (as a virtualbox on Windows 10), and it has no problem establishing a connection with the NIBE add-on.

However, on my original HASS installation (Odroid N2), when I run the NIBE add-on, it shows an error. Additionally, Modbus won’t read NIBE´s registers. BUT with other devices Modbus is running ok. I also tried to change IP of my HASS to check if there isn´t some ban in Nibe device but without success.
The issue must be related to other add-ons because both systems are running the latest OS version now. It seems like one of the add-ons, or something else, is interfering with a successful Modbus connection. However, nothing shows up in the standard log.

Of course, I could wipe everything, reinstall HASS, set up NIBE, and then install other components step by step. But I’d prefer to investigate and find the root cause.

Could you please advise where I should start?
Thank you.

2

Some logs files will help in this case. Without it… its because of magic :wink:

You might have changed something and you have a config error somewhere.

3

OK, but which log files? How to enable other than standard log? Debug: true is not usable anymore in config.

4

Start with:

website → settings → system → logs

See if there are any complaints / errors related to this problem
There is also a download button for all the logs :slight_smile:

If these have no errors regarding your modbus then ssh into the system might be needed.

5

As I wrote before. Nothing in standard logs. So any way how to get some specific logs for modbus or some live logs via SSH?

6

Try this also:

Then yes, after that SSH would be the next step and see if there is anything (but I doubt that there will be more info)

7

So I tried to disable all ather addons and all configs. NIBE addon is now able to see SMOS40. It works. But after restart it is broken again and shows:

homeassistant.components.nibe_heatpump
helpers/update_coordinator.py:386
Nibe Heat Pump (dokumentace, problémy)
17:47:30 (1 výskyty)
17:47:30

Error fetching Nibe Heat Pump data: Failed to update: Failed to read some or all coils (Timeout waiting for read response for hot-water-charging-bt6-30010, Timeout waiting for read response for roomsensor-1-1-30027, Timeout waiting for read response for priority-31029, Timeout waiting for read response for oper-mode-shunt-climate-system-1-31034, Timeout waiting for read response for current-hot-water-mode-31039, Timeout waiting for read response for alarm-number-31976, Timeout waiting for read response for hot-water-demand-mode-40057, Timeout waiting for read response for start-temperature-hw-high-temperature-40059, Timeout waiting for read response for start-temperature-hw-normal-temperature-40060, Timeout waiting for read response for start-temperature-hw-low-temperature-40061, Timeout waiting for read response for stop-temperature-hw-high-temperature-40063, Timeout waiting for read response for stop-temperature-hw-normal-temperature-40064, Timeout waiting for read response for stop-temperature-hw-low-temperature-40065, Timeout waiting for read response for cooling-with-room-sensors-40171, Timeout waiting for read response for use-room-sensor-climate-system-1-40203, Timeout waiting for read response for room-sensor-set-point-value-climate-system-1-40207, Timeout waiting for read response for oper-mode-40238, Timeout waiting for read response for room-sensor-set-point-value-climate-system-1-cooling-40989)
8

SOLVED - IMOU addon creates some kinf of problem which causes this to fail… don´t know more now but if I disable IMOU addon and reset NIBE addon it works.