Closed ankaboutobruni closed 1 year ago
Hey there @zxdavb, mind taking a look at this issue as it has been labeled with an integration (incomfort
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
incomfort documentation incomfort source (message by IssueLinks)
Hello, thanks for your report.
Have a look at these lines from your log file:
2023-02-07 21:38:16.727 DEBUG (MainThread) [incomfortclient] _get(url=heaterlist.json): response = {'heaterlist': ['000W00000', '000W00000', None, None, None, None, None, None]}
2023-02-07 21:38:16.727 DEBUG (MainThread) [incomfortclient] Heater(serial_no=000W00000) instantiated.
The boiler serial number is 000W00000
, which is a sentinel value for a null boiler. It is not the serial number of your existing boiler.
The 'new' serial number is why the integration is creating a second thermostat.
The problem with the code is that it should be raising an exception with this sentinel value, rather than instantiating a boiler - I will address that issue in an update (but I do not currently have access to the hardware).
I don't know why the gateway is reporting the sentinel value, instead of your actual boiler's serial number - you need to address that - perhaps via the vendor's web site / app?
I think I figured it out. As a last attempt late last night I put the gateway back to its original IP. I then remembered that that was actually in a different network, outside of my normal LAN, and now it's working again. So I'm now wondering whether port 80 might have been blocked inside my LAN but not on default in the network it's in now (default network of my router). I'll test again when I'm home tonight if it was port 80 that was not reachable, and if so, it'd be a good addition to the documentation (it mentions the port must be reachable but not the effect if it's not).
If you want access to my gateway for some updates, I'd be happy to assist and give you some limited access. Just message me.
There is a new version of the incomfort-client library that should address the above issue.
However, I am unable to test it using the LAN2RF hardware (for some months).
If anyone has the skills to test it: modify components/incomfort/manifest.json to include this line:
"requirements": ["incomfort-client==0.5.0"]
If there are any issues, simply change it back to 0.4.4
.
(see also: #82178)
Closing as per above.
The problem
Today I changed the IP address of my Intergas Incomfort Gateway. I changed it in the configuration.yaml file, and then restarted. Suddenly all the entities weren't available anymore and they were all "restored".
I tried removing them all, and removing the integration, and then adding it again. No luck, it strangely only adds a second thermostat (one that isn't being used). But no other thermostats or entities are being created.
The only log details for Incomfort are these:
What version of Home Assistant Core has the issue?
2023.2.2
What was the last working version of Home Assistant Core?
2023.2.2
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Incomfort
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
No response