steve9f Posted December 8, 2018 Posted December 8, 2018 I recently upgraded my ISY to v5.0.14 so that I could take advantage expanded support for the new Insteon motion sensor. I discovered a bug in the isy994 component that caused the component to fail. Turns out that the subnode id for the Insteon devices is hex but the component expected decimal - not a problem until you get a device with a address > 9. I've opened a bug report with home assistant. If you're looking for a fix you can edit binary_sensory/isy994.py changing line 55 to subnode_id = int(node.nid[-1], 16) You can track the issue here https://github.com/home-assistant/home-assistant/issues/18867
danbutter Posted December 8, 2018 Posted December 8, 2018 Is this the issue described in this thread? https://community.home-assistant.io/t/isy994-config-errors/52783 Sounds similar, but not necessarily the same. I tried to find the file you are talking about, but I'm running the hassio image right now and it doesn't seem to let you browse all the directories.
steve9f Posted December 8, 2018 Author Posted December 8, 2018 From the traceback at the beginning of the thread it's different (didn't read the entire thread). My setup worked fine except the motion II causes it to throw an error in the binary_sensor component..I have limited experience running Hassio. You may be able to access the file it you install ssh if you haven't already tried that. Another alternative might be to clone the isy994 component into your custom components directory and make the change there. I've reported the issue on the home assistant GitHub repository but no one had responded. As the fix is trivial I may try to go through the pull request process but will be my first time so might take a bit to navigate I recently upgraded my ISY to v5.0.14 so that I could take advantage expanded support for the new Insteon motion sensor. I discovered a bug in the isy994 component that caused the component to fail. Turns out that the subnode id for the Insteon devices is hex but the component expected decimal - not a problem until you get a device with a address > 9. I've opened a bug report with home assistant. If you're looking for a fix you can edit binary_sensory/isy994.py changing line 55 to subnode_id = int(node.nid[-1], 16) You can track the issue here https://github.com/home-assistant/home-assistant/issues/18867 Sent from my Pixel 2 XL using Tapatalk
steve9f Posted January 10, 2019 Author Posted January 10, 2019 The fix for the Insteon 2844-222 motion sensor II bug has been merged into Home Assistant version 0.85.0.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.