Websocket issues with ISY integration (possible climate issue?) #66003
Comments
|
isy994 documentation |
|
Hey there @bdraco, @shbatm, mind taking a look at this issue as it has been labeled with an integration ( |
|
I should also point out that the integration mostly works, sometimes haha When I really noticed there being an issue was when I recently set up a 2nd stage heat in a feed-room in a barn controlled by HA. The Insteon thermostat initially provided feedback to HA perfectly fine, then it stopped updating regularly. This lead to HA thinking the room was at one temperature when it was really at another and automation not happening as a result. Thinking my ISY was on its way out I moved some nightly automated tasks (turning on some yard lights) over to HA. These tasks don't always execute properly. Sometimes they're fine and other times not so much. Devices NOT connected to the ISY (using other integrations/protocols via HA) work just fine. |
|
Please enable debug logging for |
|
Well it looks like that MAYBE helped me solve my issues! Thanks! Having had no idea how to enable the debug logging I searched for doing so and found the following thread that pretty closely mimics what I have going on (Though there is no resolution here): Looks like maybe that was an old way to enable debugging (before it was a homeassistant.component) but I also found the following: Ultimately I just added the following to my configuration.yaml file: annnnnnnnd I can see a ton more logging entries, as one would expect. I can see it connect, get the config data from the ISY, get the programs, updates all the nodes, then it loads some devices, that's where I see the first error(s): After that the next error is right after it attempts to update a wireless thermostat (battery powered): ^ The above few errors repeat like crazy after that and then the whole works repeats for this thermostat device. I disabled this thermostat in HA and on the ISY and restarted. While the errors related to this thermostat went away next up was the same series of errors, but for another Wireless Thermostat... so again, I disabled it. It's been only about 15 minutes but given that the log isn't being flooded with entries about the above errors I'm cautiously optimistic. I can see heartbeats now, my heat-pump just came on (a hard-wired Insteon Thermostat) and I can see messages come through from the ISY about various states etc. So Ultimately I think there is still an error/issue, and it has to do with Insteon Wireless Thermostats.What can I do to help improve this? |
|
automicus/PyISY#248 should fix the websocket disconnecting. I'm not sure what to do about the 0 value for unit of measurement, but @shbatm may have a better idea how to handle that. |
|
Maybe related? automicus/PyISY#246 Edit: Seems not, still seeing the same behavior after the patch. Will enable pyisy debug. |
|
Sorry, been out of pocket for a while--
It think changing this line to the following should fix the thermostat issue. I'm curious about firmware because I haven't seen a thermostat report a if uom in (UOM_ISYV4_NONE, "", "0"):
|
|
Are you connecting to the portal URL (my.isy.io) or to the ISY directly? |
|
I can/do both. Launching the admin console is sometimes "fun" and I typically end up in the portal trying to remember how to gain access. It's also where the google home integration is. |
How do you connect Home Assistant? (BTW: I always recommend local to the ISY over HTTP--not HTTPS--for Home Assistant when possible, for best speed/response). I'm just curious if the Portal is sending empty values differently than the local connection. |
|
Oh I'm sorry, HA access is local absolutely. Until my somewhat recently acquired Starlink internet connection my rural broadband was awful at best, everything is local I can possibly get away with. I honestly don't recall if I'm using HTTP or HTTPS and I'm currently typing from elbow deep in a smart car transmission, I had a quick look at the configuration for the ISY integration via my mobile app but the configuration page seems to less than informative for how that aspect of the integration is configured. I can dig in to it this evening to try to find how I have it set up but something tells me it's HTTPS for some reason |
|
@Dewieinns It turned out that the thermostat had some bad firmware. SmartHome replaced it for me. |
|
The Thermostats are... not new by any means (looks like they were mostly
purchased 2015-2017), but they've been working without issue for at least 5
years, I'm not seeing any other odd behavior.
…On Tue, Mar 1, 2022 at 2:09 PM dobsod ***@***.***> wrote:
@Dewieinns <https://github.com/Dewieinns>
How old are your thermostats?
Several years ago I had issues with an insteon thermostat in my previous
residence. I believe it was a Venstar 7-day programmable thermostat.
It seemed to be generating a lot of insteon traffic/noise throughout my
house and not responding properly.
It turned out that the thermostat had some bad firmware. SmartHome
replaced it for me.
—
Reply to this email directly, view it on GitHub
<#66003 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGMJVAPGOF7PN7K4AFFL55LU5ZMOFANCNFSM5NXKNPGQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
- Fixes home-assistant#66003 - Changelog: automicus/PyISY@v3.0.1...v3.0.4
* Bump pyisy to 3.0.4 - Fixes #66003 - Changelog: automicus/PyISY@v3.0.1...v3.0.4 * again
* Bump pyisy to 3.0.4 - Fixes #66003 - Changelog: automicus/PyISY@v3.0.1...v3.0.4 * again
The problem
Well I’ve been beating my head against the wall for too long now and it’s time to ask for assistance. I’ve been looking through various forums and various GitHub issues and nothing seems to entirely fit what I’m experiencing (that I’ve been able to find) but I’m not perfect, if you have suggestions where I may be better to post up my issues please feel free to point me in the right direction.
Back Story:
I have been using a bunch of Insteon gear and an ISY 944 for about a decade now. I’ve been doing so without issue, but I want more! I was introduced to Home Assistant by my brother and set up an instance… months ago - and I guess that’s really when the issues started, though I wasn’t entirely sure what was up. It started with Google Home integration directly to the ISY controller not working consistently anymore, it gives errors stating it can’t reach the device - yet it sometimes still does what was asked.
The Issue:
Fast forward to presently and I’ve determined there is something weird going on with websocket connections between HA and the ISY controller, to the point it sometimes crashes the ISY Controller (or it needs to be manually restarted). When I disable the integration within HA my issues go away, but so does the integration with 55 devices and a boat-load of automations.
What version of Home Assistant Core has the issue?
core-2022.2.2
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
Universal Devices ISY994
Link to integration documentation on our website
https://www.home-assistant.io/integrations/isy994
Diagnostics information
I know this isn't entirely what you wanted here but I figured I'd fire it in anyways for information's sake.
System Health
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Universal Devices ISY994
Lovelace
Example YAML snippet
No response
Log Messages
Within my log files in HA I get the following error show up every few seconds:
as well as a few others:
The log files on the ISY controller are also full of error messages related websocket issues:
Network Information
I run a Ubiquiti USG, 24 port gigabit switch and a wireless mesh network. Everything related to this scenario is hard-wired to the same switch.
Additional Information:
I had two devices on the ISY controller which didn’t always respond. They’re remote, in my garage, and while they work via the Insteon Remote I have paired to them in the garage, they’ve never worked properly within the ISY interface. Communication issues.
I have attempted to remove them, they’re gone from the ISY interface but still remain within the integration of the ISY Controller in HA. I have attempted to remove them as devices (I have disabled them) and Entities but the delete button is grey’d out. They’re currently disabled as Entities also but my Integration in HA shows the same number of devices.
Possibly Related/additional issue:
Another error I’ve noticed is related to climate. I live in Northern Canada and I don’t heat my garage unless I’m in it. My Insteon Thermostat out there shows 0 regardless if it is 0 or below. When this happens the ISY interface shows something like 127.5 degrees. Within HA I am getting a couple related errors:
Unexpected websocket error '0' Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/pyisy/events/websocket.py", line 234, in websocket await self._route_message(msg.data) File "/usr/local/lib/python3.9/site-packages/pyisy/events/websocket.py", line 191, in _route_message self.isy.nodes.control_message_received(xmldoc) File "/usr/local/lib/python3.9/site-packages/pyisy/nodes/__init__.py", line 268, in control_message_received node.update_property(node_property) File "/usr/local/lib/python3.9/site-packages/pyisy/nodes/nodebase.py", line 228, in update_property self.status_events.notify(self.status_feedback) File "/usr/local/lib/python3.9/site-packages/pyisy/helpers.py", line 179, in notify subscriber.callback(event) File "/usr/src/homeassistant/homeassistant/components/isy994/entity.py", line 54, in async_on_update self.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 530, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 563, in _async_write_ha_state state = self._stringify_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 536, in _stringify_state if (state := self.state) is None: File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 210, in state return self.hvac_mode File "/usr/src/homeassistant/homeassistant/components/isy994/climate.py", line 136, in hvac_mode return UOM_TO_STATES[uom].get(hvac_mode.value) KeyError: '0'Logger: homeassistant.helpers.template Source: helpers/template.py:1822 First occurred: 6:15:55 PM (2 occurrences) Last logged: 6:15:55 PM Template variable warning: 'mappingproxy object' has no attribute 'current_temperature' when rendering '{{ state.attributes.current_temperature }}'I am very much willing to provide any additional logging information I can.
The text was updated successfully, but these errors were encountered: