I have a real big delay when pushing more then one of my roller shutters up or down. the first does it instantly, but the other 2 only react with a delay of 10 seconds each.
The order in which I start doesn’t matter and with the old OZW-Beta integration these problems did not arise
I switched to the new integration and it looks promising. Have some Fibaro Shutter Controllers v2. When I go in the control panel in ZwaveJS to mqtt I can see a tilt position, I also can adjust it there. Unfortunately its not exposed to HA. Also no luck with the shutter tilt command.
It took a few days to get things fully working, but everything is way faster for me now. For example, I have a few Innovelli Illumin bulbs I got on clearance awhile back for the kid’s rooms. In the past, they always responded very slow. I just thought it was the bulbs. Now, they operate instantly. I’ve noticed better response in my garage’s devices as well after I got the door lock re-added and interviewed properly.
Sensative strips, anyone?
I have several sensative door/window strips. They worked well under the legacy zwave integration, but not so under zwavejs. In zwavejs2mqtt they look fine, and the binary sensor shows true/false as it’s supposed to. In the zwave js integration, only the battery sensors are available.
I tried to exclude/include without improvement (that didn’t surprise me, since the problem seems to be in the integration part.)
i have one strip and it working fine.
But I have to exclude first and include again to get all entities… I think it was a problem with the sleeping device.
and 2 or 3 entities where disabled in HA, I have enabled them and all was fine
I dont get it, these developers do an update change the configuration and the inputs and they do not document it. HA should enforce these folks to comply and update documents before being approved to update…DEVOPS 101
- platform: template
sensors:
#Downstairs Smoke - Z Wave
smoke_downstairs:
value_template: >-
{%- if is_state("sensor.smoke_downstairs_alarm_type", "1")
and is_state("sensor.smoke_downstairs_alarm_level", "255") -%}
true
{%- else -%}
false
{%- endif %}
device_class: smoke
friendly_name: 'Downstairs'
delay_off:
seconds: 10
#Downstairs CO - Z Wave
co_downstairs:
value_template: >-
{%- if is_state("sensor.smoke_downstairs_alarm_type", "2")
and is_state("sensor.smoke_downstairs_alarm_level", "255") -%}
true
{%- else -%}
false
{%- endif %}
device_class: gas
friendly_name: 'Downstairs'
delay_off:
seconds: 10
#Downstairs Smoke Test - Z Wave
smoke_downstairs_test:
value_template: >-
{%- if is_state("sensor.smoke_downstairs_alarm_type", "12")
and is_state("sensor.smoke_downstairs_alarm_level", "255") -%}
true
{%- else -%}
false
{%- endif %}
device_class: smoke
friendly_name: 'Downstairs'
delay_off:
seconds: 10
For reference, I usually see alarm_type = 13 and alarm_level = 255 on these units when nothing is going on.
So far I have only done a test alarm on 1 of 4 of my units and it did trigger OK based on this code. I have, in the past with on OZW, tested the smoke pickup by burning some paper near one of these. I have never seen a CO condition come in (which is a good thing).
so after having updated to the latest version of the ZwaveJS integration, several extra sensors are discovered per already registered (and renamed) devices. However, the newly created sensors dont follow the naming of the parent device, but return to the original naming scheme.
Would this be a bug of the new integration? I understand where this is coming from, being the hardware device not having a name and the name really being a Home Assistant thing. But, since this is created within the Home Assistant environment and the core ZwaveJS integration And add-on, I would have expected the new devices to get the HA naming scheme?
Yeah those sensors aren’t working just yet. There are several locktypes in the repo that are pending import so your lock type might be hanging out in there like mine is. I have a Yale lock and while my sensors are showing that they’re now alive they don’t report anything…yet
Any tricks to getting zwave-js to recognize the zcombo? I tried excluding and re-including and the device adds but nothing is pulled in. Doesn’t show the manufacture or anything.
Announcement: About supporting new device configuration files · Issue #1600 · zwave-js/node-zwave-js (github.com)