@toggledbits I understand that you do not perform testing on Mac computers but thought I'd share the following with you in case something can be done.
I started seeing these errors with version 24302. I thought that upgrading to 24343 would have fixed the issue but unfortunately not. I either have to close the browser or clear the cache for the errors to stop popping-up but they slowly come back.
I see these errors on the following browsers:
Safari 16.6.1 on macOS Big Sur Safari 18.1.1 on MacOS Sonoma DuckDuckGo 1.118.0 on macOS Big Sur and Sonoma Firefox 133.0.3 on macOS Big Sur Chrome 131.0.6778 on macOS Big SurHere are the errors
Safari while creating/updating an expression
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:21 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:29 reindexExpressions@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:32 @http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:608:40 dispatch@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:40040DuckDuckGo while clicking on status
http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:789:44 asyncFunctionResume@[native code] saveGridLayout@[native code] dispatchEvent@[native code] _triggerEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1401:30 _triggerAddEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1383:31 makeWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:968:30 addWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:388:24 placeWidgetAdder@http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:183:44Firefox while updating a rule
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:82:21 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:47:26 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1460:39 forEach@[native code] @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1459:58Chrome while creating/updating an expression
TypeError: Cannot read properties of undefined (reading 'getEditor') at RuleEditor.makeExprMenu (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:1788:86) at Object.handler (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:2174:54) at http://192.168.0.13:8111/client/MessageBus.js:98:44 at Array.forEach (<anonymous>) at MessageBus._sendToBus (http://192.168.0.13:8111/client/MessageBus.js:95:54) at MessageBus.send (http://192.168.0.13:8111/client/MessageBus.js:106:44) at ExpressionEditor.publish (http://192.168.0.13:8111/client/Observable.js:78:28) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:14) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:15) at ExpressionEditor.reindexExpressions (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:18) ``
Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.
Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce
A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.
Hi
Having to rebuild my Linux Debian box as the SSD failed. And I have forgotten exactly what I did the first time to get it all setup.
I have Debian 12 up and running on the new SSD, I only have console no Desktop GUI.
I am trying to do the bare metal install for MSR. However I am not sure if I am meant to install nodejs whlist logged in as the root user or as the none root user with my name ?
I used putty and connected via SSH and logged in as root and I installed nodejs but I think this was wrong as when logged in as my user name and I do a node -v command it says node is not installed or doesn't show any version number anyway.
But when logged in as root and I do a node -v command it does show me its installed and displays the version number. maybe its a path issue for my username and he can't see node is installed?
So now I am thinking I should of installed node whilst logged in as my user name and not as the root user.
This is how I installed nodejs as whilst logged in as root
ac7bf6c3-23ad-46fc-8ada-44af6704e63e-image.png
Thanks in advance.
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.As the title says, here's my OpenAI Controller for Reactor:
OpenAI Controller per Reactor. Contribute to dbochicchio/reactor-openai development by creating an account on GitHub.
It supports both OpenAI and Azure OpenAI endpoints. You'll need keys/endpoints, according to each service.
The controller supports multiple models, and each one could be mapped as an entity.
It's quite easy to use, and responses can be stored in variables, for easy access. Or sent to another action (Text To Speech, another endpoint, etc).
9013ae50-fd68-42a2-87c3-97479132e465-image.png
80a88eec-7c89-464a-8196-690b4b72d044-image.png
Have fun with LLM into your scenes!
In Home Assistant I have an integration that if I add entities to it, I will get the following error in MSR as certain entity values I'm using in expressions are null for a moment. This is more or less cosmetic issue and happens very rarely as I rarely modify that integration on the hass side.
Screenshot 2024-11-28 at 22.20.41.png
And the expression is
Screenshot 2024-11-28 at 22.38.19.png
Could I "wrap" hass-entity shown above somewhat differently to prevent this error from happening? Using build 24302.
Hello
I am trying to set up Multi System Reactor to automate routines across multiple smart home devices & platforms (e.g., Home Assistant, SmartThings, and Hubitat). While I have successfully linked the systems; I am facing issues with:
-Delays in triggering actions on secondary devices.
-Inconsistent execution of complex logic conditions.
-Synchronization of states between devices when one system updates.
Is there a recommended way to optimize performance & confirm seamless state sharing across systems?
I have checked https://smarthome.community/category/22/multi-system-reactor-msbi guide for reference but still need advice.
Any tips on debugging or log analysis to pinpoint where the issue arises would also be appreciated.
Thank you !
I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.
Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.
( *Drag & drop of rule conditions have never worked on a mobile)
@toggledbits Since I have upgraded ZWaveJSController to 24293 from 24257 I am seeing entries related to registering action set_volume, but action is not defined by the capability 143 every time I restart Reactor.
The Siren seems to be doing what it is supposed to do. The volume levels are fine. Should I worry about it?
Reactor version 24302
ZWaveJSController version 24293
Z-Wave JS UI version 9.27.4
zwave-js version 14.3.4
I have the following ACL defined:
groups: admin: users: - admin applications: true api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: trueAnd I have authenticated to MSR as "admin" user. However, I'm getting "access denied" when trying to access http://*******:8111/api/v1/log
So what I'm missing, is my ACL incorrectly defined?
Using build 24302 on Docker.
Hi
I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.
They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.
This is how that device looks in the Ezlo API.
Devices Info:
_id: "10696001" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "level_sensor" subcategory: "" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Digital" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696001" deviceId: "10696001" hasGetter: true hasSetter: false name: "smoke_density" show: true valueType: "substance_amount" scale: "parts_per_million" value: 2.7472610473632812 valueFormatted: "2.75" status: "idle"There is also an Analog Gas sensor that one did import in to MSR OK.
68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png
Devices Info:
_id: "10696000" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "security_sensor" subcategory: "gas" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Analog" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696000" deviceId: "10696000" hasGetter: true hasSetter: false name: "gas_alarm" show: true valueType: "token" enum: 0: "no_gas" 1: "combustible_gas_detected" 2: "toxic_gas_detected" 3: "unknown" valueFormatted: "no_gas" value: "no_gas" status: "idle"And this is how this MQ2 Gas Sensor looks like on their dashboard:
Digital
cb77dfa3-4af5-4d06-9635-89207a716a89-image.png
Analog
4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png
They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!
And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.
THANKS.
A couple of things for you @toggledbits, since you mentioned that this release has new features and some tweaks are expected.
Local expressions cannot be deleted. Pushing the X button has no effect for me.
When cloning an entity action, the result is strange (first is cloned one, second is the original action):
a92ea094-9e2c-4aaa-bf47-2d07a6ffdbd0-image.png
When changing the action on the cloned element, the params are added to the original one. See screenshot:
92ac3011-83c8-466b-bd23-47d483ad7a52-image.png
Dark theme has a couple of strange contrasts. One is visible in the previous screenshots (white text on yellow background). Another one is in groups (blue text on blue background):
9b3c4988-53ef-44e6-9672-30e744cacb75-image.png
Overall, I found blue, yellow, red and green (in buttons and forms) to be too bright.
On the bright side:
I love the new script action: thank you! The dark theme is a great start to avoid getting blinded at night I promise I'll try very soon the new features around actions. Thanks!@toggledbits
I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:
I followed the new directions about npm
npm i --no-save --no-package-lock --omit dev
Any idea what the issue is?
Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)
Things I have tried:
Hard refresh
Different browser
Different computer
Restarting Reactor
Failed troubleshooting attempts:
No errors in Chrome console
No relevant errors in Reactor log (can still PM the full log file)
Reactor version: latest-24293-ea42a81d
Hardware: Odroid N2+
Linux version: Ubuntu 24.04.1 LTS
3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled
ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled
Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.
What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?
Running:
Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]HAAS:
RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0[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.
-
@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!
-
Sorry, but the image looks like you're showing position, not watts. I would like to understand which of the two power values provided by the device you are trying to reconcile.
That said, a position of 0.91 would be correct, as the scale of the
position.valueattribute in Reactor is 0.0 to 1.0, computed from the device range of 0 to 99 (90/99 = 0.91 rounded to two digits).Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.