That’s been there since the original implementation, but I might have broken something causing it to pull updates more frequently. I’ll look tomorrow.
Do you use any of those virtual sensor programs?
No, I don’t use any virtual sensor programs. With variables now working, it is always easier for me to just create a variable for any states I need.
Is that 11 B7 F0 1? You might try removing the “- Ignore” from the name of 11 B7 F0 2 in your ISY – the component uses the “negative” node to get updates too–it should only show up as 1 device in HA.
Post/send the debug log when you can for the others, including the Loaded/Updated Programs issue–I can’t replicate that.
Found the program issue–it only shows up when you’re not watching any programs for some reason.
1 Like
Re the 11.b7.f0 Triggerlinc, yes, that is one of them. These devices show 2 sensors: #1 is unlocked true/false, #2 is locked true/false. Only #1 works with ISY. #2 does not update. That is why I had -Ignore on #2. But I removed that tag, restarted, and still I am not getting updates on that device.
Can you double check that the code is looking for #1 for data, and not #2? BTW, I am running 5.0.14 in my ISY.
Watch the debug logs and make sure you’re getting the event come through. If it does please post that excerpt here. You can filter it with egrep "11 B7 F0" home-assistant.log to just catch the lines that have to do with that node.
If I understand the original code correctly: it just listens to both nodes for sensors like that, sometimes (depending on device config) it will turn the OFF node ON but not update the ON node or vice versa–the Hass code just lumps these together and looks at both nodes–if either one changes it updates the status correctly. I haven’t done anything with this section of code, so that’s why I need the debug logs to see what’s actually being sent from the ISY.
Another thing you could try:
Line 248 of binary_sensor.py change from:
if self._status_was_unknown and self._computed_state is None:
to this:
if self._status_was_unknown:
Thanks again, shbatm. I will do some snooping to figure it out. Reading up on the ISY forums, this particular sensor is rather finicky and this model is no longer sold I think. So perhaps not worth too much effort if we cannot quickly resolve. Right now, I have these devices setting variables via programs on the ISY, and variables are working great!!!
@shbatm, it does look like the data on the 2421 TriggerLinc is coming across for the door sensor. See log extract below:
core-ssh:/config# egrep "11 B7 F0" home-assistant.log
<?xml version="1.0"?><Event seqnum="131" sid="uuid:75"><control>ST</control><action uom="100" prec="0">255</action><node>11 B7 F0 1</node><eventInfo></eventInfo><fmtAct>On</fmtAct></Event>
2019-07-19 14:43:06 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: 11 B7 F0 1
2019-07-19 14:43:06 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: 11 B7 F0 1 ST 255
<?xml version="1.0"?><Event seqnum="501" sid="uuid:75"><control>DOF</control><action>1</action><node>11 B7 F0 1</node><eventInfo></eventInfo></Event>
2019-07-19 14:43:50 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: 11 B7 F0 1 DOF 1
<?xml version="1.0"?><Event seqnum="502" sid="uuid:75"><control>ST</control><action uom="100" prec="0">0</action><node>11 B7 F0 1</node><eventInfo></eventInfo><fmtAct>Off</fmtAct></Event>
2019-07-19 14:43:50 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: 11 B7 F0 1
2019-07-19 14:43:50 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: 11 B7 F0 1 ST 0
<?xml version="1.0"?><Event seqnum="503" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ 11 B7 F0 1] DOF 1</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="504" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ 11 B7 F0 1] ST 0 (uom=100 prec=0)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="537" sid="uuid:75"><control>DON</control><action>1</action><node>11 B7 F0 1</node><eventInfo></eventInfo></Event>
2019-07-19 14:43:57 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: 11 B7 F0 1 DON 1
<?xml version="1.0"?><Event seqnum="538" sid="uuid:75"><control>ST</control><action uom="100" prec="0">255</action><node>11 B7 F0 1</node><eventInfo></eventInfo><fmtAct>On</fmtAct></Event>
2019-07-19 14:43:57 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: 11 B7 F0 1
2019-07-19 14:43:57 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: 11 B7 F0 1 ST 255
<?xml version="1.0"?><Event seqnum="539" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ 11 B7 F0 1] DON 1</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="540" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ 11 B7 F0 1] ST 255 (uom=100 prec=0)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="583" sid="uuid:75"><control>DOF</control><action>1</action><node>11 B7 F0 1</node><eventInfo></eventInfo></Event>
2019-07-19 14:44:08 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: 11 B7 F0 1 DOF 1
<?xml version="1.0"?><Event seqnum="584" sid="uuid:75"><control>ST</control><action uom="100" prec="0">0</action><node>11 B7 F0 1</node><eventInfo></eventInfo><fmtAct>Off</fmtAct></Event>
2019-07-19 14:44:08 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: 11 B7 F0 1
2019-07-19 14:44:08 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: 11 B7 F0 1 ST 0
<?xml version="1.0"?><Event seqnum="587" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ 11 B7 F0 1] DOF 1</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="588" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ 11 B7 F0 1] ST 0 (uom=100 prec=0)</eventInfo></Event>
core-ssh:/config#
BTW, it is going from 0 for off, to 255 for on, then 0 for off. I was not sure if the 255 value was normal for binary switch.
No joy using
if self._status_was_unknown:
And here is the egrep’d log looking at my Home Energy Monitor (ZW 030)
core-ssh:/config# egrep "ZW030" home-assistant.log
<?xml version="1.0"?><Event seqnum="266" sid="uuid:75"><control>TPW</control><action uom="33" prec="3">15805013</action><node>ZW030_001_143</node><eventInfo></eventInfo><fmtAct>15805.013 kWh</fmtAct></Event>
2019-07-19 14:43:07 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_001_143 TPW 15805013
<?xml version="1.0"?><Event seqnum="267" sid="uuid:75"><control>ST</control><action uom="73" prec="3">581652</action><node>ZW030_001_143</node><eventInfo></eventInfo><fmtAct>581.652 Watts</fmtAct></Event>
2019-07-19 14:43:07 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: ZW030_001_143
2019-07-19 14:43:07 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_001_143 ST 581652
<?xml version="1.0"?><Event seqnum="268" sid="uuid:75"><control>TPW</control><action uom="33" prec="3">11116754</action><node>ZW030_002_143</node><eventInfo></eventInfo><fmtAct>11116.754 kWh</fmtAct></Event>
2019-07-19 14:43:07 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_002_143 TPW 11116754
<?xml version="1.0"?><Event seqnum="269" sid="uuid:75"><control>ST</control><action uom="73" prec="3">381669</action><node>ZW030_002_143</node><eventInfo></eventInfo><fmtAct>381.669 Watts</fmtAct></Event>
2019-07-19 14:43:07 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: ZW030_002_143
2019-07-19 14:43:07 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_002_143 ST 381669
<?xml version="1.0"?><Event seqnum="344" sid="uuid:75"><control>ERR</control><action>0</action><node>ZW030_1</node><eventInfo></eventInfo></Event>
2019-07-19 14:43:08 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_1 ERR 0
<?xml version="1.0"?><Event seqnum="345" sid="uuid:75"><control>BATLVL</control><action uom="51" prec="0">0</action><node>ZW030_1</node><eventInfo></eventInfo><fmtAct>0%</fmtAct></Event>
2019-07-19 14:43:08 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_1 BATLVL 0
<?xml version="1.0"?><Event seqnum="346" sid="uuid:75"><control>TPW</control><action uom="33" prec="3">27009442</action><node>ZW030_143</node><eventInfo></eventInfo><fmtAct>27009.442 kWh</fmtAct></Event>
2019-07-19 14:43:08 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_143 TPW 27009442
<?xml version="1.0"?><Event seqnum="347" sid="uuid:75"><control>ST</control><action uom="73" prec="3">1448994</action><node>ZW030_143</node><eventInfo></eventInfo><fmtAct>1448.994 Watts</fmtAct></Event>
2019-07-19 14:43:08 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: ZW030_143
2019-07-19 14:43:08 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_143 ST 1448994
<?xml version="1.0"?><Event seqnum="739" sid="uuid:75"><control>ST</control><action uom="73" prec="3">1965483</action><node>ZW030_143</node><eventInfo></eventInfo><fmtAct>1965.483 Watts</fmtAct></Event>
2019-07-19 14:46:20 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: ZW030_143
2019-07-19 14:46:20 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_143 ST 1965483
<?xml version="1.0"?><Event seqnum="740" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW030_143] ST 1965483 (uom=73 prec=3)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="749" sid="uuid:75"><control>TPW</control><action uom="33" prec="3">27009584</action><node>ZW030_143</node><eventInfo></eventInfo><fmtAct>27009.584 kWh</fmtAct></Event>
2019-07-19 14:46:21 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_143 TPW 27009584
<?xml version="1.0"?><Event seqnum="750" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW030_143] TPW 27009584 (uom=33 prec=3)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="1029" sid="uuid:75"><control>ST</control><action uom="73" prec="3">1879883</action><node>ZW030_143</node><eventInfo></eventInfo><fmtAct>1879.883 Watts</fmtAct></Event>
2019-07-19 14:51:20 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: ZW030_143
2019-07-19 14:51:20 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_143 ST 1879883
<?xml version="1.0"?><Event seqnum="1030" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW030_143] ST 1879883 (uom=73 prec=3)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="1039" sid="uuid:75"><control>TPW</control><action uom="33" prec="3">27009732</action><node>ZW030_143</node><eventInfo></eventInfo><fmtAct>27009.732 kWh</fmtAct></Event>
2019-07-19 14:51:21 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_143 TPW 27009732
<?xml version="1.0"?><Event seqnum="1040" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW030_143] TPW 27009732 (uom=33 prec=3)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="1290" sid="uuid:75"><control>ST</control><action uom="73" prec="3">1815255</action><node>ZW030_143</node><eventInfo></eventInfo><fmtAct>1815.255 Watts</fmtAct></Event>
2019-07-19 14:56:20 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: ZW030_143
2019-07-19 14:56:20 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_143 ST 1815255
<?xml version="1.0"?><Event seqnum="1291" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW030_143] ST 1815255 (uom=73 prec=3)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="1297" sid="uuid:75"><control>TPW</control><action uom="33" prec="3">27009890</action><node>ZW030_143</node><eventInfo></eventInfo><fmtAct>27009.890 kWh</fmtAct></Event>
2019-07-19 14:56:21 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_143 TPW 27009890
<?xml version="1.0"?><Event seqnum="1298" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW030_143] TPW 27009890 (uom=33 prec=3)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="1554" sid="uuid:75"><control>ST</control><action uom="73" prec="3">2128872</action><node>ZW030_143</node><eventInfo></eventInfo><fmtAct>2128.872 Watts</fmtAct></Event>
2019-07-19 15:01:21 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: ZW030_143
2019-07-19 15:01:21 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_143 ST 2128872
<?xml version="1.0"?><Event seqnum="1555" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW030_143] ST 2128872 (uom=73 prec=3)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="1561" sid="uuid:75"><control>TPW</control><action uom="33" prec="3">27010042</action><node>ZW030_143</node><eventInfo></eventInfo><fmtAct>27010.042 kWh</fmtAct></Event>
2019-07-19 15:01:21 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW030_143 TPW 27010042
<?xml version="1.0"?><Event seqnum="1562" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW030_143] TPW 27010042 (uom=33 prec=3)</eventInfo></Event>
core-ssh:/config#
And log from my ZW034 Motion Sensor with temperature probe. I would like to have access to ST (motion) and CLITEMP (temperature sensor)
core-ssh:/config# egrep "ZW034" home-assistant.log
<?xml version="1.0"?><Event seqnum="240" sid="uuid:75"><control>ST</control><action uom="78" prec="0">100</action><node>ZW034_1</node><eventInfo></eventInfo><fmtAct>On</fmtAct></Event>
2019-07-19 14:43:07 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: ZW034_1
2019-07-19 14:43:07 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW034_1 ST 100
<?xml version="1.0"?><Event seqnum="241" sid="uuid:75"><control>CLITEMP</control><action uom="4" prec="0">22</action><node>ZW034_118</node><eventInfo></eventInfo><fmtAct>22°C</fmtAct></Event>
2019-07-19 14:43:07 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW034_118 CLITEMP 22
<?xml version="1.0"?><Event seqnum="321" sid="uuid:75"><control>ST</control><action uom="78" prec="0">100</action><node>ZW034_172</node><eventInfo></eventInfo><fmtAct>On</fmtAct></Event>
2019-07-19 14:43:08 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: ZW034_172
2019-07-19 14:43:08 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW034_172 ST 100
<?xml version="1.0"?><Event seqnum="2442" sid="uuid:75"><control>CLITEMP</control><action uom="4" prec="0">24</action><node>ZW034_118</node><eventInfo></eventInfo><fmtAct>24°C</fmtAct></Event>
2019-07-19 15:12:38 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW034_118 CLITEMP 24
<?xml version="1.0"?><Event seqnum="2443" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW034_118] CLITEMP 24 (uom=4 prec=0)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="2467" sid="uuid:75"><control>ST</control><action uom="78" prec="0">0</action><node>ZW034_1</node><eventInfo></eventInfo><fmtAct>Off</fmtAct></Event>
2019-07-19 15:13:19 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: ZW034_1
2019-07-19 15:13:19 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW034_1 ST 0
<?xml version="1.0"?><Event seqnum="2468" sid="uuid:75"><control>DOF</control><action uom="78" prec="0">0</action><node>ZW034_1</node><eventInfo></eventInfo><fmtAct>Off</fmtAct></Event>
2019-07-19 15:13:19 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW034_1 DOF 0
<?xml version="1.0"?><Event seqnum="2469" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW034_1] ST 0 (uom=78 prec=0)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="2470" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW034_1] DOF 0 (uom=78 prec=0)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="2471" sid="uuid:75"><control>DON</control><action uom="78" prec="0">100</action><node>ZW034_172</node><eventInfo></eventInfo><fmtAct>On</fmtAct></Event>
2019-07-19 15:13:20 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW034_172 DON 100
<?xml version="1.0"?><Event seqnum="2472" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW034_172] DON 100 (uom=78 prec=0)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="2795" sid="uuid:75"><control>ST</control><action uom="78" prec="0">100</action><node>ZW034_1</node><eventInfo></eventInfo><fmtAct>On</fmtAct></Event>
2019-07-19 15:18:01 DEBUG (Thread-2) [custom_components.isy994] ISY Updated Node: ZW034_1
2019-07-19 15:18:01 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW034_1 ST 100
<?xml version="1.0"?><Event seqnum="2796" sid="uuid:75"><control>DON</control><action uom="78" prec="0">100</action><node>ZW034_1</node><eventInfo></eventInfo><fmtAct>On</fmtAct></Event>
2019-07-19 15:18:01 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW034_1 DON 100
<?xml version="1.0"?><Event seqnum="2797" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW034_1] ST 100 (uom=78 prec=0)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="2798" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW034_1] DON 100 (uom=78 prec=0)</eventInfo></Event>
<?xml version="1.0"?><Event seqnum="2799" sid="uuid:75"><control>DON</control><action uom="78" prec="0">100</action><node>ZW034_172</node><eventInfo></eventInfo><fmtAct>On</fmtAct></Event>
2019-07-19 15:18:01 DEBUG (Thread-2) [custom_components.isy994] ISY Node Control Event: ZW034_172 DON 100
<?xml version="1.0"?><Event seqnum="2800" sid="uuid:75"><control>_1</control><action>3</action><node></node><eventInfo>[ ZW034_172] DON 100 (uom=78 prec=0)</eventInfo></Event>
core-ssh:/config#
Found a major oversight on binary_sensors. Please try the new version.
The status should be fixed with the latest update too. Please check the device state attributes for the temperature – let me know if this is being updated; you’ll have to pull this out with a template sensor.
I think I found the issue with the sensors too. Let me know if you have some luck with this version.
1 Like
Good progress!
Working:
2421 TriggerLinc
ZW034 Motion
No longer getting the constant program pinging (performance on ISY and HA much better now)
Not working:
ZW034 CLITEMP: no temperature value
ZW030 HEM: still get battery data, but no power data (Watts or KWhr)
Great progress! The Triggerlinc is really nice to have. Those are the only areas where I had to create a variable that I otherwise did not need. THANKS!!
I wanted to ask about two things. First zwave plugs with energy monitoring.
I have a couple different types that simply say Unknown in HA when there is no current usage.
This is a plug I use for a Christmas tree and it just stays there to help the zwave network the rest of the year.
The only other thing I see coming from ISY that is strange is scenes.
I have some ceiling fans with fanlincs and keypadlincs controlling them.
So in order for the buttons on the keypadlinc to be in sync with the status of the fan speeds and light I have scenes assigned to the buttons of the keypadlinc. I then turn the scenes on and off with the buttons and all is well. So while I can have the fan motor in lovelace and tap on it and then choose the speed of the fan that I would like…the keypadlinc gets out of sync if I do this. So I added the scenes to the room in lovelace.
They come over from ISY as a switch. Problem is that when I use one scene by hitting the button it turns on all three (low, med, high) in lovelace. They can never be turned off either…they just turn themselves back on.
Any clue on a way around this?
@danbutter, can you please send the ISY /rest/nodes/ZWADDR response for the plugs? I’ll look at it when I look at @Blueman2’s stuff.
For the scenes - this is what I have settled on using:
This part specifically I think has to do with how the groups are set up on the Keypadlinc itself. I remember a similar issue when I tried to set up an exclusive group of the 4 fan buttons. I ended up ungrouping them, making them all toggle on/off except the fan off button (off only) and using the special variables/scenes above to keep everything in sync.
Just following up on these – haven’t had much time to look in detail but please confirm:
- Are these showing up as separate sensor entities in HA (They should be, ISY reports them as different nodes than their parents)?
- If they’re showing up as separate sensors, is it showing any initial power state for the ZW030 or unknown? For ZW034, I think I see an issue–the ISY never reports a “
ST” state value, just a “CLITEMP” command. Is this showing up in this separate sensor as a attribute at all (e.g. is the status unknown but the temp is in the attributes)?
Follow up to this – do you have these “grouped” / nested in the ISY? If so, can you try ungrouping them and restarting HA? – In my testing the devices are seen and managed by PyISY, but HA isn’t adding them because there is something wrong with the iterator–it doesn’t look like it’s working for grouped nodes.
EDIT: For reference, this is the issue in PyISY that causes this problem.
BINGO. It appears that was it. I have ungrouped my nodes and I am now getting data on all the elements I expected. I am seeing a bit of an anomaly on a few nodes, but give me time to look into that. However, it does appear that is the source bug. Grouped nodes were not being seen. Great detective work!
EDIT: Following up, I ungrouped everything and that solved all the issues I was seeing with z-wave device sub-nodes I am getting all the nodes within my Smoke/CO alarm, my PIR/Temp sensor, and my HEM (Home Energy Monitor)!
Well done!!!
I’ve added this to HACS for easier installation.
Custom Repo (should be available in default store soon): https://github.com/shbatm/hacs-isy994
1 Like
Hi,
I tried to to install this it seems like it did successfully, but I’m not able to load the component when starting HA. I see this error in the log.
2019-08-14 14:40:34 ERROR (MainThread) [homeassistant.setup] Error during setup of component isy994
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 153, in _async_setup_component
hass, processed_config)
File "/config/custom_components/isy994/__init__.py", line 464, in async_setup
log=_LOGGER,
File "/usr/local/lib/python3.7/site-packages/PyISY/isy.py", line 79, in __init__
self.nodes = Nodes(self, xml=self.conn.get_nodes())
File "/usr/local/lib/python3.7/site-packages/PyISY/Nodes/__init__.py", line 61, in __init__
self.parse(xml)
File "/usr/local/lib/python3.7/site-packages/PyISY/Nodes/__init__.py", line 216, in parse
self.get_by_id(nid).update(feature)
File "/usr/local/lib/python3.7/site-packages/PyISY/Nodes/node.py", line 111, in update
sleep(wait_time)
TypeError: an integer is required (got type Element)
The regular ISY994 component works fine. I would like to test out your changes so let me know if there’s anything farther I can provide.
Strange that this hasn’t been caught before, I just pushed an update, please give it a try.
What worries me is that if this is failing on your initial setup, then somehow you are getting nodes with duplicate IDs, which shouldn’t happen… Let me know if you get any further with the new update.