Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down.
I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor).
My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long
I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
https://github.com/dbochicchio/reactor-mqtt-contrib
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me.
While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users.
I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do.
Just an idea
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically.
That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button.
Example: Light 1 ON → OFF, then Light 2 ON → OFF.
The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule.
Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Use case:
When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled.
To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work.
Then another situation: the water pump system and garden irrigation, another switch.
In short, I had to create several virtual switches in Hubitat to disable rules in MSR.
Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR.
If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR.
Would it be possible to do something like this? Any recommendations from the experts?
Probably a really dumb question.
Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great.
Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly.
Any thoughts?
Apologies if the ask is not clear/
TIA
C
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well.
As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API.
Updates: (the latest versions first in the list)
OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions;
Fix an error in OWMWeatherController that could cause it to stop updating;
Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later;
Improve error detail in messages for EzloController during auth phase;
Add isRuleSet() and isRuleEnabled() functions to expressions extensions;
Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases);
Fix a place in the UI where 24-hour time was not being displayed.
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page.
Once logged back in I can no longer remove errant panes nor is the + available to add new ones.
Brave Browser v1.80.122 (Jul 16, 2025)
What have I done?!
Will check other browsers on my M1.
UPDATE: Safari exhibits same behaviour.
I've tried both sans last-four public key entry and with - no change.
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of.
Thanks.
[ZwaveJS] Position and cover not working for Roller Shutter 1/2/3
-
"It's not working" isn't actionable. You know what I need.
-
Ok, here we go.
In details:- OK: cover.close/open
- KO: cover.stop, position.*
Taken from zwawejs.log
[latest-24212]2024-08-20T14:54:29.867Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.open on Cover#zwavejs>4-0 with [Object]{ } [latest-24212]2024-08-20T14:54:29.869Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs action cover.open set node 4 endpoint 0 value 38:targetValue:(undefined) = 99 [latest-24212]2024-08-20T14:54:29.871Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs setting value [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 99 } [latest-24212]2024-08-20T14:54:33.806Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.close on Cover#zwavejs>4-0 with [Object]{ } [latest-24212]2024-08-20T14:54:33.808Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs action cover.close set node 4 endpoint 0 value 38:targetValue:(undefined) = 0 [latest-24212]2024-08-20T14:54:33.809Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs setting value [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 0 } [latest-24212]2024-08-20T14:54:36.322Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.open on Cover#zwavejs>4-0 with [Object]{ } [latest-24212]2024-08-20T14:54:36.323Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs action cover.open set node 4 endpoint 0 value 38:targetValue:(undefined) = 99 [latest-24212]2024-08-20T14:54:36.323Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs setting value [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 99 } [latest-24212]2024-08-20T14:55:02.507Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing position.increase on Cover#zwavejs>4-0 with [Object]{ "amount": 0.1 } [latest-24212]2024-08-20T14:55:04.523Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing position.increase on Cover#zwavejs>4-0 with [Object]{ "amount": 0.1 } [latest-24212]2024-08-20T14:55:10.073Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing position.relative on Cover#zwavejs>4-0 with [Object]{ "amount": 0.5 } [latest-24212]2024-08-20T14:55:13.023Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing position.set on Cover#zwavejs>4-0 with [Object]{ "value": 0.3 } -
Class B doesn't have position, per Z-Wave specs. So that's the manufacturer providing the wrong device class data. Fibaro does a lot of this. Their firmware is trash. Also, this is a different device than previously reported (node 4 vs node 148), so you are moving the goal posts on me. So go back to 148 and tell me what's going on there, then we'll worry about 4 (different version of similar device).
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Class B doesn't have position, per Z-Wave specs. So that's the manufacturer providing the wrong device class data. Fibaro does a lot of this. Their firmware is trash. Also, this is a different device than previously reported (node 4 vs node 148), so you are moving the goal posts on me. So go back to 148 and tell me what's going on there, then we'll worry about 4 (different version of similar device).
@toggledbits sorry. node 148 is working as expected. this is a RS3. node 4 is a RS2.
here's node 4:
cover.state=true energy_sensor.units="kWh" energy_sensor.value=6.58 position.value=null power_sensor.units="W" power_sensor.value=0 power_switch.state=true x_debug.dt={"0":769,"1":4097,"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=6","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state","manufacturerId":271,"productType":770,"productId":4096} x_zwave_values.Binary_Switch_currentValue=true x_zwave_values.Binary_Switch_targetValue=null x_zwave_values.Configuration_Delay_Time_After_S2=10 x_zwave_values.Configuration_Energy_Reports=10 x_zwave_values.Configuration_Forced_Roller_Shutter_Calibration=0 x_zwave_values.Configuration_Lamellas_Positioning_Mode=1 x_zwave_values.Configuration_Managing_Lamellas_in_Response_to_Alarm=0 x_zwave_values.Configuration_Motor_Operation_Detection=0 x_zwave_values.Configuration_Motor_Operation_Time=240 x_zwave_values.Configuration_Periodic_Power_or_Energy_Reports=3600 x_zwave_values.Configuration_Power_Reports=10 x_zwave_values.Configuration_Reports_Type=0 x_zwave_values.Configuration_Response_to_General_Alarm=0 x_zwave_values.Configuration_Response_to_Smoke_CO_CO2_Alarm=0 x_zwave_values.Configuration_Response_to_Temperature_Alarm=0 x_zwave_values.Configuration_Response_to_Water_Flood_Alarm=0 x_zwave_values.Configuration_Roller_Shutter_Operating_Modes=1 x_zwave_values.Configuration_Scenes_Associations_Activation=1 x_zwave_values.Configuration_Self_Measurement=0 x_zwave_values.Configuration_Switch_Type=0 x_zwave_values.Configuration_Turning_Time_Delay_Time=150 x_zwave_values.Manufacturer_Proprietary_fibaro_venetianBlindsPosition=99 x_zwave_values.Manufacturer_Specific_manufacturerId=271 x_zwave_values.Manufacturer_Specific_productId=4096 x_zwave_values.Manufacturer_Specific_productType=770 x_zwave_values.Meter_reset=null x_zwave_values.Meter_value_65537=6.58 x_zwave_values.Meter_value_66049=0 x_zwave_values.Multilevel_Sensor_Power=0 x_zwave_values.Multilevel_Switch_Close=null x_zwave_values.Multilevel_Switch_Open=null x_zwave_values.Multilevel_Switch_currentValue=99 x_zwave_values.Multilevel_Switch_duration=null x_zwave_values.Multilevel_Switch_restorePrevious=null x_zwave_values.Multilevel_Switch_targetValue=99 x_zwave_values.Protection_exclusiveControlNodeId=null x_zwave_values.Protection_local=0 x_zwave_values.Protection_rf=0 x_zwave_values.Protection_timeout=null x_zwave_values.Version_firmwareVersions=["25.25"] x_zwave_values.Version_libraryType=3 x_zwave_values.Version_protocolVersion="3.52" zwave_device.capabilities=[37,38,49,50,112,114,117,134,145] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Multilevel Switch" zwave_device.impl_sig="24233:1:24233:1" zwave_device.is_beaming=false zwave_device.is_listening=true zwave_device.is_routing=true zwave_device.is_secure=false zwave_device.manufacturer_info=[271,770,4096] zwave_device.max_data_rate=null zwave_device.node_id=4 zwave_device.specific_class="Motor Control Class B" zwave_device.status=4 zwave_device.status_text="alive" zwave_device.version_info=[null,"25.25"] -
Here's node 148 for reference:
cover.state=true energy_sensor.units="kWh" energy_sensor.value=0.41 position.value=0.92 power_sensor.units="W" power_sensor.value=0 x_debug.dt={"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=6","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state","description":"Roller Shutter 3","model":"FGR223","default_name":"Roller Shutter 3","values":[{"match":{"endpoint":[1,2],"commandClass":38,"property":"currentValue"},"entity_class":"Cover","primary_attribute":"cover.state","capabilities":{"cover":{"attributes":{"state":{"expr":"value !== 0"}},"actions":{"open":{"valueId":"+targetValue:#","value":99},"close":{"valueId":"+targetValue:#","value":0},"stop":{"valueId":"+Up:","value":false}}},"position":{"attributes":{"value":{"expr":"round( value / 99, 2 )"}},"actions":{"set":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( parameters.value ?# 0 ), 0 ) ) )"}},"increase":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) + ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}},"decrease":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) - ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}},"relative":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) + ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}}}},"toggle":{"actions":{"toggle":{"valueId":"+targetValue:#","value":{"expr":"entity.attributes.cover.state ? 0 : 99"}}}}}}],"manufacturerId":271,"productType":771,"productId":4096} x_zwave_values.Meter_reset=null x_zwave_values.Meter_value_65537=0.41 x_zwave_values.Meter_value_66049=0 x_zwave_values.Multilevel_Switch_Down=null x_zwave_values.Multilevel_Switch_Up=null x_zwave_values.Multilevel_Switch_currentValue=91 x_zwave_values.Multilevel_Switch_duration="unknown" x_zwave_values.Multilevel_Switch_restorePrevious=null x_zwave_values.Multilevel_Switch_targetValue=91 x_zwave_values.Notification_Power_Management_Over_current_status=0 x_zwave_values.Notification_System_Hardware_status=0 x_zwave_values.Notification_alarmLevel=null x_zwave_values.Notification_alarmType=null zwave_device.capabilities=[38,50,113] zwave_device.endpoint=1 zwave_device.failed=null zwave_device.impl_sig="24233:1:24233:1" zwave_device.manufacturer_info=null zwave_device.node_id=148 zwave_device.version_info=null -
OK. That's easy to fix, I think. Pull the updated
zwavejs_data.zipfile from the server and put in yourconfigdirectory, restart Reactor, and let's see if 4 behaves better (I just applied the exceptions for the 223 to the 222, adjusted for a single endpoint). -
Still not working. position.value is still null.
Logs:
[latest-24212]2024-08-20T15:19:14.892Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing position.relative on Cover#zwavejs>4-0 with [Object]{ "amount": 0.5 } [latest-24212]2024-08-20T15:19:20.349Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing position.relative on Cover#zwavejs>4-0 with [Object]{ "amount": 0.5 } [latest-24212]2024-08-20T15:19:29.900Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.close on Cover#zwavejs>4-0 with [Object]{ } [latest-24212]2024-08-20T15:19:29.901Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs action cover.close set node 4 endpoint 0 value 38:targetValue:(undefined) = 0 [latest-24212]2024-08-20T15:19:29.903Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs setting value [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 0 } [latest-24212]2024-08-20T15:19:32.172Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.close on Cover#zwavejs>4-0 with [Object]{ } [latest-24212]2024-08-20T15:19:32.173Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs action cover.close set node 4 endpoint 0 value 38:targetValue:(undefined) = 0 [latest-24212]2024-08-20T15:19:32.174Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs setting value [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 0 } [latest-24212]2024-08-20T15:19:34.602Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.stop on Cover#zwavejs>4-0 with [Object]{ } [latest-24212]2024-08-20T15:19:36.567Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.open on Cover#zwavejs>4-0 with [Object]{ } [latest-24212]2024-08-20T15:19:36.568Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs action cover.open set node 4 endpoint 0 value 38:targetValue:(undefined) = 99 [latest-24212]2024-08-20T15:19:36.570Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs setting value [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 99 } [latest-24212]2024-08-20T15:19:45.548Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing position.relative on Cover#zwavejs>4-0 with [Object]{ "amount": 0.5 } -
OK. You're talking about an attribute, but showing me actions in a log. On my system, the FGR222 is now showing position.value correctly for any value in range.
Here's what my log looks like (position.set to 0.45 on device 4, using your configuration):
[###BUILDVERSION###]2024-08-20T15:25:04.586Z <ZWaveJSController#zwstatic:INFO> ZWaveJSController#zwstatic performing position.set on Cover#zwstatic>4-0 with [Object]{ "value": 0.45 } [###BUILDVERSION###]2024-08-20T15:25:04.587Z <ZWaveJSController#zwstatic:5:ZWaveJSController.js:2135> ZWaveJSController#zwstatic def [Object]{ "endpoint": 0, "commandClass": 38, "property": "currentValue", "propertyKey": --undef--, "impl": { "valueId": "+targetValue:#", "value": { "expr": "max( 0, min( 99, round( 100 * ( parameters.value ?# 0 ), 0 ) ) )" } } } [###BUILDVERSION###]2024-08-20T15:25:04.591Z <ZWaveJSController#zwstatic:INFO> ZWaveJSController#zwstatic action position.set set node 4 endpoint 0 value 38:targetValue:(null) = 45 [###BUILDVERSION###]2024-08-20T15:25:04.593Z <ZWaveJSController#zwstatic:5:ZWaveJSController.js:1760> ZWaveJSController#zwstatic _set_value(4,0,38,targetValue,(null),45) [###BUILDVERSION###]2024-08-20T15:25:04.594Z <ZWaveJSController#zwstatic:INFO> ZWaveJSController#zwstatic setting value [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 45 } [###BUILDVERSION###]2024-08-20T15:25:04.596Z <ZWaveJSController#zwstatic:5:ZWaveJSController.js:335> ZWaveJSController#zwstatic sending #1724167504595<8/20/2024, 11:25:04 AM>: [Object]{ "command": "node.set_value", "nodeId": 4, "valueId": { "endpoint": 0, "commandClass": 38, "property": "targetValue" }, "value": 45, "messageId": 1724167504595 }So both are working for me. I would try deleting the entity in MSR and restarting to recreate it. Then test again.
-
What is the
impl_sigattribute on device 4? -
Are you using position.set directly, or using the relative actions?
-
That's wonderful. I have a FGR222 (previous fw) that's working. Here's node 3:
cover.state=false energy_sensor.units="kWh" energy_sensor.value=0 position.value=0 power_sensor.units="W" power_sensor.value=0 power_switch.state=true x_debug.dt={"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=6","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state","description":"Roller Shutter","model":"FGRM222","default_name":"Roller Shutter","values":[{"match":{"commandClass":38,"property":"currentValue"},"capabilities":{"cover":{"attributes":{"state":{"expr":"value !== 0"}},"actions":{"open":{"valueId":"+targetValue:#","value":99},"close":{"valueId":"+targetValue:#","value":0},"stop":{"valueId":"+Up:","value":false}}},"position":{"attributes":{"value":{"expr":"round( value / 99, 2 )"}},"actions":{"set":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( parameters.value ?# 0 ), 0 ) ) )"}},"increase":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) + ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}},"decrease":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) - ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}},"relative":{"valueId":"+targetValue:#","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) + ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}}}},"toggle":{"actions":{"toggle":{"valueId":"+targetValue:#","value":{"expr":"entity.attributes.cover.state ? 0 : 99"}}}}}}],"manufacturerId":271,"productType":769,"productId":4097} x_zwave_values.Binary_Switch_currentValue=true x_zwave_values.Binary_Switch_targetValue=null x_zwave_values.Configuration_Delay_Time_After_S2=10 x_zwave_values.Configuration_Energy_Reports=10 x_zwave_values.Configuration_Forced_Roller_Shutter_Calibration=0 x_zwave_values.Configuration_Lamellas_Positioning_Mode=1 x_zwave_values.Configuration_Managing_Lamellas_in_Response_to_Alarm=0 x_zwave_values.Configuration_Motor_Operation_Detection=1 x_zwave_values.Configuration_Motor_Operation_Time=240 x_zwave_values.Configuration_Periodic_Power_or_Energy_Reports=3600 x_zwave_values.Configuration_Power_Reports=10 x_zwave_values.Configuration_Reports_Type=0 x_zwave_values.Configuration_Response_to_General_Alarm=0 x_zwave_values.Configuration_Response_to_Smoke_CO_CO2_Alarm=0 x_zwave_values.Configuration_Response_to_Temperature_Alarm=0 x_zwave_values.Configuration_Response_to_Water_Flood_Alarm=0 x_zwave_values.Configuration_Roller_Shutter_Operating_Modes=0 x_zwave_values.Configuration_Scenes_Associations_Activation=1 x_zwave_values.Configuration_Self_Measurement=0 x_zwave_values.Configuration_Switch_Type=0 x_zwave_values.Configuration_Turning_Time_Delay_Time=150 x_zwave_values.Manufacturer_Proprietary_fibaro_venetianBlindsPosition=99 x_zwave_values.Manufacturer_Specific_manufacturerId=271 x_zwave_values.Manufacturer_Specific_productId=4097 x_zwave_values.Manufacturer_Specific_productType=769 x_zwave_values.Meter_reset=null x_zwave_values.Meter_value_65537=0 x_zwave_values.Meter_value_66049=0 x_zwave_values.Multilevel_Sensor_Power=0 x_zwave_values.Multilevel_Switch_Close=null x_zwave_values.Multilevel_Switch_Open=null x_zwave_values.Multilevel_Switch_currentValue=0 x_zwave_values.Multilevel_Switch_duration=null x_zwave_values.Multilevel_Switch_restorePrevious=null x_zwave_values.Multilevel_Switch_targetValue=0 x_zwave_values.Protection_exclusiveControlNodeId=null x_zwave_values.Protection_local=0 x_zwave_values.Protection_rf=0 x_zwave_values.Protection_timeout=null x_zwave_values.Version_firmwareVersions=["24.24"] x_zwave_values.Version_libraryType=3 x_zwave_values.Version_protocolVersion="3.52" zwave_device.capabilities=[37,38,49,50,112,114,117,134,145] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Multilevel Switch" zwave_device.impl_sig="24233:1:24233:2" zwave_device.is_beaming=false zwave_device.is_listening=true zwave_device.is_routing=true zwave_device.is_secure=false zwave_device.manufacturer_info=[271,769,4097] zwave_device.max_data_rate=null zwave_device.node_id=3 zwave_device.specific_class="Motor Control Class B" zwave_device.status=4 zwave_device.status_text="alive" zwave_device.version_info=[null,"24.24"] -
OK. I think I see it. #4 has a different type and ID, and the alias has an error. Pull the new data ZIP and try again.
-
That did the trick. Two things.
position.valueis now incosistent, whereas dimming.level was ok before. I tried to set node 4 to .9, and it's now reporting .31. A refresh is updating the position (to .91), but nowpower_switch.state=null.power_sensor.valueis still 0. -
What are you comparing it to? For node 4, the last data you show have the Meter class value (meterType 1, property
value, propertyKey 66049) at 0, and the Multilevel Sensor withsensorType=4 (Power) also 0. What are you expecting the value to be? Again, can you show more context, too? Post all the attributes? These things are moving targets, so more data is better than less. -
I'm getting the values from ZWaveJS UI and checking on the reported values from MSR:
Position
Watts reading seems to be more related to the device not refreshing itself (or refreshing randomly), as it was doing on Vera. I'll keep debugging the ZWaveJS part, since it seems that if I refresh the device, the values is passed onto Reactor.
Thanks for the help!