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.
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)!
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.
yo thanks for your hard work on this @shbatm! I’m just testing it out through HACS now and test sensors are working as expected. Do you have any thoughts on the status of the aeotec multi 6 sensor? Sensor is working well for me so far, just curious if the status should just read something other than unknown?
Great work, @shbatm! I have HACS on my system already, so love the idea of moving this into HACS. Is there anything I need to be careful about when installing this in HACS?
Should be straightforward, ‘drop in’ replacement and overwrite your existing custom_component.
I don’t think this will change. Looking at the node outputs I’ve received, the ISY doesn’t give a ST property for the Multisensor, so no ‘status’ can be determined. Probably best to split out all the properties as Template sensors and then hide the main device in Hass.
I was able to check out the update over the weekend and it resolved whatever my issue was. Thanks for your work on this. These changes are looking great!
I have been running the custom component for several weeks and it has been working great. I restarted today and received the following error. After several restarts including rebooting the host server, the problem persists. The ‘normal’ ISY component works fine, though. Any ideas?
2019-08-30 23:05:39 ERROR (MainThread) [homeassistant.setup] Error during setup of component isy994
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/PyISY/climate.py", line 268, in _parse_val
(val, unit) = self._parse_val_num(val)
File "/usr/local/lib/python3.7/site-packages/PyISY/climate.py", line 281, in _parse_val_num
return (float(split_val[0]), "feet")
ValueError: could not convert string to float: 'N/A'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 168, 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 89, in __init__
self.climate = Climate(self, xml=self.conn.get_climate())
File "/usr/local/lib/python3.7/site-packages/PyISY/climate.py", line 222, in __init__
self.parse(xml)
File "/usr/local/lib/python3.7/site-packages/PyISY/climate.py", line 253, in parse
(val, unit) = self._parse_val(node.firstChild.toxml())
File "/usr/local/lib/python3.7/site-packages/PyISY/climate.py", line 271, in _parse_val
(val, unit) = self._parse_val_dir(val)
TypeError: cannot unpack non-iterable NoneType object
