-
-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intergas intergration failing after core upgrade to 2024.2.x #110140
Comments
Hey there @zxdavb, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) incomfort documentation |
Same issue here |
Have no issues.. I dont need username and password for it to work |
Could that be because you have an older gateway? As per integration page;
|
I'm wondering if this Python timeout change has something to do with it |
Yes perhaps, but then it probably has something to do with authentication and new python because the addon is working with older no authentication gateways |
No, it doesn't - |
I am sorry, I am the CODEOWNER, but I no longer own this hardware, and am not really able to bugfix this. |
I do appreciate that you replied. Unfortunately for us. Hopefully there is someone else around to take over the maintenance. Not for me, as I'm just a script kiddy. |
For what it is worth, I can do a GET request without any problems on
|
I will take a look at it today.. else it could take a while this will be fixed.. i guess Code is pretty minimal, and think python 3.12 broke it |
Not trying to rush you @NH-Networks, but bloody curious if you have had any luck yet on the code... |
Mhh was hoping someone from the original dev team would pick this up.. i have a older gateway.. no auth and working perfectly.. so i need some logs to see what is happening on your side |
The only relevant logging I could find were in the openings post. |
I also have an old red intergas gateway no issues controlling the device but i do have the issue since this latest HA update that the second light “WAN” goes off once or twice a day and the device is not reachable the “LAN” and “RF” light are still on but i need to reboot the gateway to be able to control it again. |
For me this was solved by pulling the power out so all 5 numbers are white. Then while the numbers are white pull out again so all except number 1 are white. |
In an attempt to do some debugging, I fired up a fresh Hass OS virtualbox image. Even when I upload a backup of my live environment, the intergas integration is still working fine. I'm totally lost. Did my OS not got updated correctly/fully at some point and am I stuck with outdated files on my OS? Tried again to gain SSH access to the OS, but without any luck, I stay stuck within the docker / hypervisor. |
I have been able to work around this until a fixture can be applied: docker exec command to achieve this is:
afterwards restart homeassistant....disco !! |
Awesome @SenTzu01 |
@USRFSledge if you have access to the host terminal you could execute If you dont have access to the host terminal, define the shell command as per my first post, adn then create an automation (see below for reference):
Once setup, just trigger the automation manually and reboot HA Core. Hope this helps! |
Boy oh boy @SenTzu01 you're a life saver! (Interesting twist though, as the HASS log nagged about the script exceeding 300 seconds. Looks like there is a small communication error between the intergration and the OS on that matter.) |
@USRFSledge Glad to help a fellow Dutchie! |
Just to validate.. this response is instant..? With curl or wget? |
Instant, with curl indeed from any random machine in my network @NH-Networks |
Havent looked into the code any further, but from the previous Home Automation I used (Pimatic) I recall that updates to the incomfort bridge are not processed immediately. As python calls the API asynchronously, the timeouts could occur. |
It just processes the json.. only values get updated... Never seen a timeout... Glad your fix is working.. but there is some other issue |
A fellow dutchie, that increases the chance of hugging massively. EDIT: Hang on ... you are using HA now, but only for week and for sure planning on using it a bit longer. Looking for adopting an intergration? |
Had the same issue with my incomfort gateway, so rule #1: Use your internet Fu.... I recently switched to HA, Used to develop for Pimatic. I still need to gain mad Python skillz, might adopt the integration once I am set. Current code owners could PM me or something. |
Hi @zxdavb, mister @SenTzu01 appears a little shy so far, but he might be a candidate to take over your integration ;)
|
If it helps, the incomfort debug log shows the integration is taking its time indeed (on my Pi 3b at least). Not sure how it was before, but for the record, it only became an issue as from HA core-2024.2.x
|
Anyone (not just the CODEOWNER) can submit a PR. Submitting several high-quality PRs and/or getting usefully involved with issues will be sufficient to qualify you for CODEOWNER status. Becoming the CODEOWNER is just another PR. |
@zxdavb I am not ready to take this responsibility yet, as per my previous post. Just wanted to share my 2 cents to help others. |
Hi @SenTzu01! Thank you for your work! I've added the shell_command, rebooted HA, ran the automation, rebooted again but unfortunately my Incomfort is still not working. I'm using an old Intergas gateway, so without authentication. Everything is looking fine when I straight go to its IP address. Before running the fix_incomfort command the timeout error as in the opening post was shown in the HA logs. Now it shows:
Do you have a clue what the issue could be? Or someone else? |
As was exactly the case for core-2024.2.x and core-2024.3.x, but as from core-2024.4.x everything works out of the box again. Did I got lucky three times in a row (v4.0, 4.1 and 4.2) or is this the general experience? |
Same here, works fine again with core-2024.4.x without applying the temporary fix. |
Hi, I am the new codeowner for the |
Glad to see @jbouwh, as I hope to use the hardware for a little longer. |
Then I suggest to close this issue for now, thank you for your feedback @USRFSledge. |
BTW, I bought a new boiler and gateway last week, so I may assume support is to be continued for now. |
Cheers @jbouwh |
The problem
Intergas intergration was working fine for an extended period of time, till I ran the upgrade of core-2024.1.x to 2024.2.0 (and later 2024.2.1).
Best guess is the Python version upgrade that came with core-2024.2 broke the intergration.
Boot log states that the intergration is not responding for over 300 seconds, which disables the intergration in order to continue the boot.
What version of Home Assistant Core has the issue?
core-2024.2.x
What was the last working version of Home Assistant Core?
core-2024.1.x
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Intergas InComfort/Intouch Lan2RF gateway
Link to integration documentation on our website
https://www.home-assistant.io/integrations/incomfort/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
Webinterfae of the gateway is available. Credentials are confirmed working. Both gateway as home assistant hot and cold booted multiple times. Native gateway android app is working as intended.
The text was updated successfully, but these errors were encountered: