[Errno 104] Connection reset by peer and [Errno 111] Connect call failed after updating heat pump to 2.22.6 #102385
Comments
|
Hey there @elupus, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) nibe_heatpump documentation |
|
Looks like a bug in the new software. The pump disconnects us, then refuse a new connection. Are you you using some other modbus client at the same time perhaps? |
|
I also did the NIBE update just a few minutes ago and Home Assistant can not see any information anymore. I tried rebooting HA and disabled/re-enabled TCP/IP Modbus on the NIBE to no avail. I remember reading that you can boot the prior firmware somehow. Do you know how? |
|
Just installed the new firmware and have the same problem. All entities are unavailable. |
|
@elupus No other Modbus client is connected to the heat pump. Have tried to reboot the pump without any luck. |
|
@elupus Same issue here. I also used standard modbus integration, which worked paralell. With todays update the Nibe integration stopped working with my SMO S40, however the standard modbus still OK. |
|
Looks like a kind of DDoS-Protection. I tried to disable all entities except the 11 that I show on my dashboard, then the data will be served.
I will try to figure out when the connection abort will occur. |
|
That was my guess too. Us requesting some data that it consider invalid. |
|
Hi all, disabling all entities and whitelisting only the needed ones fixed the error on my side. Thanks for the hint! |
|
Can you find out which one caused the error. We should remove that option. |
|
I did research during 1am but without success.
I figured out that entitie "overload-pool" delivers wrong values.
…
Am 21.10.2023 um 09:28, Joakim Plate ***@***.***> schrieb:
Can you find out which one caused the error. We should remove that option. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID:
Achtung! Diese Nachricht stammt von außerhalb der Organisation!
sophospsmartbannerend
Can you find out which one caused the error. We should remove that option.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
It seems that many registers is changed. I had a saved file of all modbus registers for S1255 with the old software and after exporting the registers for 2.22.6 I got the difference below. New in the 2.22.6 Removed since old software: CSV file old Software: CSV file new software: |
|
Thanks, can you help how you did this, so I would try to do the same for SMO S40 |
|
I've tried disabling all entities and just re-enabling a single one (first tried Priority, and then Current Outdoor Temperature), and on both attempts it was still showing my single entity as unavailable. I've tried reloading the integration, and restarting HA, but neither helps. You people who've solved it by disabling entities, did it start working immediately upon disabling, or did you have to restart things, and how did you restart them in that case? |
|
Same here, but even worse. After updating to newest firmware, the Nibe S1255PC-6 is in a bootloop and unusable. After disabling Modbus TCP the device is working again. After downgrading to precision version everything is fine again... |
This indicates they have a major bug in their device. Should be reported to nibe. |
How did you downgrade to previous version? I did not find anything in the menu. |
I’d like to know the same. I am using a VVM S320. Besides the Modbus problem mine is working fine since the update. |
|
How to roll-back to previous Firmware on S1255PC6: 1. shutdown the device until Power Button is blue |
Already done... |
I can confirm that this steps works to downgrade to 2.21.12 on our S1255. When the button gets white and I pushed it got green immediately so I released it directly. Now the integration works again with the old firmware. |
|
Seems to be different with the VVM S320. Following these steps powers it off. Pressing the white button for only a second instead of holding it does nothing and boots regularly to the current 2.22.6 firmware. At least I found out that I can enter emergency mode (Notbetrieb in german) by pressing and holding the power button while the device is powered off. The button and the LED turn green/yellow and the display is off. I’ve contacted NIBE… |
same here, with Nibe SMO S40 / F2120 the control unit goes into endless reboot loop if there's a Modbus TCP request on the network. Only way is to disable request from home assistant otherwise heat pump is unusable... Please keep us posted on the feedback from Nibe! Meanwhile - do you know if it's possible to manually download older versions of firmware to downgrade from USB Stick? |
|
I finally got my HA-connection working again, with the new firmware. I have a Nibe S1255 for reference.
|
But if you need to reboot your control unit for any reason - you're back to the endless reboot loop. Correct? |
This made my HA NIBE integration and my own modbus setup work again together with my SMO S40 system. |
|
After the firmware update to 2.22.6, the heat pump have had problems to keep connected to the wifi. I will track it during some time to see if this is a problem or not |
|
I use my SMO S40 through Ethernet cable and have the same HA issue. I don't know if Ethernet has the connection instability but I don't faced it. I also use standard modbus integration and i have no issue there, just with the plugin.
…________________________________
From: ekamagn ***@***.***>
Sent: Friday, October 27, 2023 9:45:14 AM
To: home-assistant/core ***@***.***>
Cc: matebenyovszky ***@***.***>; Comment ***@***.***>
Subject: Re: [home-assistant/core] [Errno 104] Connection reset by peer and [Errno 111] Connect call failed after updating heat pump to 2.22.6 (Issue #102385)
After the firmware update to 2.22.6, the heat pump have had problems to keep connected to the wifi. I will track it during some time to see if that will a probable cause of this.
—
Reply to this email directly, view it on GitHub<#102385 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANVUQMRH5G5EYWBZIV2VBGTYBNRAVAVCNFSM6AAAAAA6I6WYNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBSGQ2TINBZGU>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Same issue with my SMO S40 after update to 2.22.6. HA can't make a connection. Interface seems to be inactive. No open ports. |
|
I am also using Ethernet, so I can’t comment on using WLAN, but I tested the workaround posted by MrWizardOfOz and it works for me, too. After just enabling a couple of entities I enabled all (nearly 800) NIBE entities to see what happens. After the usual ~30 s I could see all (maybe not all, but many) my entities suddenly filling with data for about 1 second. Then all of them switched back to the not available state. So the NIBE must have decided that it does not agree with something and closed the communication. I can reproduce this and, at least in my case, it is not necessary to reboot the NIBE. It suffices to
You can switch 3 and 4 if you want. The next step I suppose would be to re-enable your entities 1 by 1 until you find the culprit. Great Fun! 😵💫 |
|
New firmware for SMO S40 is available, but firmware revision 2.23.4 has the same issue. |
|
I did enable many (but not all) entities after my last post and it has worked without problems so far. This did continue with the newest firmware, which I installed today. |
What happens to the heat pump in case of a power outage? After power comes back I fear it will start its bootloop?! I tested 2.23.4 with my S1255PC6 and it caused again a bootloop like previous firmware. But I do not follow your comments about disabling some entities before. As long as I do not have the guarantee that a power outage does not cause any negative impact, I'll wait for a firmware, that is stable even with many entities enabled. |
|
In my case there are no boot loops (VVM S320). I just didn’t get any readings in HA anymore. I had all 792 entities enabled in HA, even though I did not incorporate all of them in my lovelace views. After disabling all entities and only enabling the ones used by me all was fine again and it continues to work with the newest firmware from yesterday. |
|
I have had the same problem. But before reading these work-arounds, I managed to delete my integration. Now I cannot re-install and re-connect. When connecting to modbus I get "Error on read request from pump. Verify your |
|
It does not look at entitles during setup, so does not matter which is enabled. You likely need to restart your pump. |
|
It worked, thanks!! |
|
Same issue here with S2125. With 20 enabled entities, after 10-20 minutes pump blocks modbus port 502, and i need to restart the pump. I dont have experience with Python, but looking at the code, modbus is polled every 60 seconds, with retries. Is it possible that new modbus polling request is executed while previous ones still havent finished, causing pump to shut the port down? @elupus is it possible to explicitly set PARALLEL_UPDATES to 1 to prevent such situation? |
|
It is not running in parallel. It is using a coordinator |
|
Any progress ? Its been a while since someone posted. |
I tried latest Nibe firmware 2.27.5 today with the same, negative result: boot loops of the heat pump and no data in HA. |
|
This can only be solved by nibe. Have you reported this to them? |
I have the same issue. My Nibe S1255 went into a bootloop and the only way to stop the bootloop was to disable modbus. I have not reported this to NIBE. I feel that its not worth the trouble anymore when Nibe constantly releases firmware that causes problems for the integration. Im losing data in my database and its the graphs I'm looking for to be able to see what's going on. Its not reliable enough for me to use anymore so I just stopped using it now. Thanks for the reply ! |
|
I can still report that even with the latest firmware update version 2.27.5 it runs fine for me with HA. There are just 2 values (Wärmemengenzähler, don’t know the english word) which no longer give any values, but that is a known bug I reported to NIBE and was confirmed by them for the current version. In my case disabling all entities and only enabling the ones I use has worked for all firmware versions since this problem first came up. But my VVM S320 never had boot loops. It was just that it stopped reporting to HA as soon as the "wrong" entities were pulled I suppose… |
How many entities do you pull via the Nibe integration? In my case I pull 158 values... |
yes - already done in November 2023, but no solution yet :-( Perhaps I should open a new ticket... |
In the NIBE integration settings there’s a total of 870 entities. If I select to show only disabled ones, it says 852 which implies 18 enabled ones, but on my NIBE dashboard page I just counted (manually) exactly 90 entities, from which 2 currently do not report any values. That is the known bug for quite some firmware versions now. I have a neighbour with another NIBE model and it’s the same with his unit. He does not have HA, so he’s just reading the values from the NIBE device itself. I don’t understand how to better count entities, but I know that enabling ALL of them results in the NIBE heatpump to stop sending ANY data. So I successively enabled more and more until I had anything I could ever want enabled. |
|
I found a solution for my S1255PC6 problem. I had 158 entities enabled and with firmware 2.21.12 all was fine. With all newer firmware versions the S1255 was in an unlimited boot loop. |
The problem
After updating the S1255 heat pump to software version 2.22.6 the integration is unable to fetch all information from the heat pump. I can see in the dashboard that the integration starts to fetch information but before all registers is read the integration throws the errors below. I suspect it may be because Nibe added new Modbus TCP/IP registers?
https://www.nibe.eu/webdav/files/myuplink_changelog/nibe-n.pdf
What version of Home Assistant Core has the issue?
core-2023.10.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
nibe_heatpump
Link to integration documentation on our website
https://www.home-assistant.io/integrations/nibe_heatpump
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: