Awesome thank you! I’m looking forward for my own switch over to Z-Wave JS – All these exciting things happening, and of course I’m busy with other things this week.
Thanks to everyone who has worked on this so far! I am trying to port this code over to use the older Minimotes with zwave_js, but haven’t been able to get it working yet.
The Minimotes send out an event_type: zwave_js_event, but of the data type: “value_notification” and scene_id values of 1, 3, 5, or 7 corresponding to the four buttons. (Odd 1, 3, 5, 7 for short press, even 2, 4, 6, 8 for long press.)
I can get everything working if I explicitly list the node_id, type: value_notification, and value, but not in the blueprints format.
Hello,
I hope you could help me. i have just included this nanomote quad and i only get these entities…
Maybe you could assist me? i am using z-wave js using z-wave js to mqtt as bridge.~
Has anyone been able to create a zwavejs blueprint for the nanomote quad? If so would they be willing to share it on the forum. I wish I had the ability to create one but its just a bit outside my ability. Thanks!
If i add the url for this blueprint to my setup will it automatically pull the js version from post 12 or will it pull the original from the top that works with ozw? If it doesnt pull from post 12 how is that accomplished to import it to my ha?
I tried switching the “ozw.scence_activated” against “zwave_js_value_notification” however this didn’t solve it, my automations would not get triggered.
So I got the blueprint from post #12 and I can add automations that work. However the blueprint only sets up single quick press for each button. I was using automations for holding down and releasing as well (thus 8 automations in total).
If I run listen on this press I get two entries:
"value": "KeyHeldDown",
"value_raw": 2
“value”: “KeyReleased”,
“value_raw”: 1
Is there anyway to tweak the blueprint to allow for programing using holding down button?
If not, how should the manual code be for zwave-js if I do it like I had previously?
I will answer my own question as I got it to work. Don’t know how I add my blueprint here but the following works for allowing to create automations for both the quick press and the long hold for 2 seconds for each button. So all in all 8 automations from the NanoMote Quad.
Note the Input needs to be matched to your NanoMote Quad.
And it’s changed to have zwave_js_value_notification instead of js_event.
blueprint:
name: Aeotec ZWA003 NanoMote Quad
description: Create automations for the Aeotec ZWA003 NanoMote Quad using the
Zwave-JS integration.
domain: automation
input:
NanoMote:
name: Aeotec NanoMote Quad
description: The NanoMote Quad to interact with.
selector:
device:
integration: zwave_js
manufacturer: Aeotec Ltd.
model: Aeotec NanoMote Quad
button_1_single:
name: Press Button One Single
description: Action to run on single button press.
default: []
selector:
action: {}
button_1_hold:
name: Press Button One Hold
description: Action to run on long button press.
default: []
selector:
action: {}
button_2_single:
name: Press Button Two Single
description: Action to run on single button press.
default: []
selector:
action: {}
button_2_hold:
name: Press Button Two Hold
description: Action to run on long button press.
default: []
selector:
action: {}
button_3_single:
name: Press Button Three Single
description: Action to run on single button press.
default: []
selector:
action: {}
button_3_hold:
name: Press Button Three Hold
description: Action to run on long button press.
default: []
selector:
action: {}
button_4_single:
name: Press Button Four Single
description: Action to run on single button press.
default: []
selector:
action: {}
button_4_hold:
name: Press Button Four Hold
description: Action to run on long button press.
default: []
selector:
action: {}
mode: single
max_exceeded: silent
trigger:
platform: event
event_type: zwave_js_value_notification
event_data:
command_class_name: Central Scene
device_id: !input NanoMote
action:
- variables:
scene_id: "{{ trigger.event.data.property_key_name }}"
scene_value_id: "{{ trigger.event.data.value }}"
- choose:
- conditions: "{{ scene_id == '001' and scene_value_id == 'KeyPressed' }}"
sequence: !input button_1_single
- conditions: "{{ scene_id == '001' and scene_value_id == 'KeyReleased' }}"
sequence: !input button_1_hold
- conditions: "{{ scene_id == '002' and scene_value_id == 'KeyPressed' }}"
sequence: !input button_2_single
- conditions: "{{ scene_id == '002' and scene_value_id == 'KeyReleased' }}"
sequence: !input button_2_hold
- conditions: "{{ scene_id == '003' and scene_value_id == 'KeyPressed' }}"
sequence: !input button_3_single
- conditions: "{{ scene_id == '003' and scene_value_id == 'KeyReleased' }}"
sequence: !input button_3_hold
- conditions: "{{ scene_id == '004' and scene_value_id == 'KeyPressed' }}"
sequence: !input button_4_single
- conditions: "{{ scene_id == '004' and scene_value_id == 'KeyReleased' }}"
sequence: !input button_4_hold
I was being rather obtuse, it works fine when I tested it physically. I presume that error is just because I was running internal tests and it had no real data to act upon.
