Hmmm… then maybe I’m not on the latest?
these are the versions I have now:
App Version 2.0.0
Zwavejs Version 6.5.0
Zwavejs-server Version 1.1.0
That’s the latest
1 Like
as a FYI, I noticed the Sensitive strips not being able to be included any longer since any of the latest update in the HA (Beta 2021.3.0b3, Integration or Add-on (version 0.1.10) … No way of saying which off the updates caused this.
Filed the issue here, for anyone with the Sensitive Strips Guard, also called Strips-MaZw
Previously included Strips work fine.
update
as reported in the issue, the Strips are back up and running, took 2 days of hacking and fiddling about, but hey, I can see my doors opening again…
thx for your answer with re-interview it is working now.
first i start the re-interview and then the wake up process on the Device
1 Like
couldn’t find any info about this. My Motion / Multisensor get only a Binary Sensor Value that is not a Motion Device Class, any way around this?
now
before:
@lordfiSh, Configuration, Customizations, select your entity, use the dropdown box to change the device class (click the edit pencil if it is greyed out), and save.
Alternatively… File Editor, customize.yaml, and add lines for each entity you want to change like this:
binary_sensor.front_door:
device_class: door
1 Like
This is an improvement over zwave/ozw, which refreshed the level value immediately after the Set command. In some cases this would result in the wrong brightness, in other cases the switch might be completely off because it hadn’t even started the transition. At least this 5 second delay is functional for most uses, it only results in a minor annoyance in the UI.
For me this is indeed better than before. Would be even better when the UI could be capable of showing a wait icon in between
I have experienced the same, but also with Fibaro Smoke sensor and Aeotek recessd door sensor. After fiddling a day or too, all devices where found and have alle entities. I just tried to activate the device just at the same time that I requested a Re-Interview Node. At one time I gave up, but next morning the result was there!
new error after updating to 2021.3.0:
2021-03-04 13:10:39 ERROR (MainThread) [homeassistant.components.zwave_js] Unexpected exception: 'success'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/zwave_js/__init__.py", line 374, in client_listen
await client.listen(driver_ready)
File "/usr/local/lib/python3.8/site-packages/zwave_js_server/client.py", line 168, in listen
if not state_msg["success"]:
KeyError: 'success'
anyone with a hint?
I am no longer getting scene event names from my Inovelli switches:
{"type":"value_notification","domain":"zwave_js","node_id":38,"home_id":#########,"endpoint":null,"device_id":"ef121446fea38ca4790779a0b2cd6ba6","command_class":91,"command_class_name":"Central Scene","label":null,"property":"scene","property_name":"scene","property_key":"002","property_key_name":"002","value":0,"value_raw":0}
My Node Red scene manager is expecting
“KeyPressed”
“KeyPressed2x”
etc.
Thoughts? tagging @petro as he has been a massive help before.
Yea its changed but my belief was it was supposed to be changed back before release happened. That didn’t appear to have happened so I don’t know what the final result will be going forward…
I ended up updated my automations to use the current property_key_name and value but this may very well change back again.
Unfortunate. What are you getting/using for value though? Mine are ALL 0 no matter what scene/button is commanded (I think?).
Looks like they are on it:
Anyone else with First Alert ZCOMBO Smoke/CO detectors notice that their alarm_level and alarm_type sensors no longer work when upgrading to 2021.03? Worked on the betas up to b6, then b7 broke them. Final release didn’t fix it.
Somewhat related issue on Github, but was added to in the last few days:
EDIT: Everything working as of 2021.3.2
1 Like
I have the same issue however it doesn’t seem to be tied directly to 2021.3. I have mine working but my zwavejs2mqtt add on is at 0.5.0. If I upgrade it to 0.5.1 or 0.6.0 I no longer get the values.
Yale B1L still not reporting local lock changes. zwavejs2mqtt 2.1.0 and hass core 2021.3.0.
I don’t want to change my automations since they worked reliably in the deprecated built in version.
Check to see if you’re getting a zwave_js_event instead.
It would have a “type” as “notification”, like the door locks.
well this is unexpected. Yesterday I learned I could have Instance A with Z-waveJS integration subscribe to Instance B with the Z-Wave add-on. Working perfectly! However, before that I had also installed the Z-Wave JS integration on Instance B (and serve those entities to the other instances over MQTT, which also works just fine)
Because I have a big lag in my current Production system (Instance A) I thought it wise to check these Z-Wave JS communications, and took out the Integration from Instance B (since I don’t need the entities anymore there, only on Instance A) , leaving only the Add-on, to serve the Integration on Instance A.
To my surprise, this also took out all devices and entities on Instance A, that is, they became all unavailable. Why is this?
No events come through. Restart Home Assistant and ZWaveJS2MQTT earlier this morning (on latest version of each). Did a test and nothing.