@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[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
-
@tamorgen said in [SOLVED] New iblind and zwaveJScontroller/MSR not communicating:
I don't believe the old power switch commands work with the new command class. When I go into a specific device in ZwaveJS, the switch type devices are greyed out.
I noticed this as well. I've also noticed that tapping into the dialogue you're showing (how did you copy/paste images, I keep getting a
parsing server error...) nets a slider in HA that does nothing. It literally saysUNKNOWNat the top where a percentage would be display of openness or closure. -
@gwp1
It seems to me that something may be missing from this command class integration. I know iBlinds was working with the ZWaveJS developers. I'm curious is this is what they expected.When I look at the entities in MSR, there are a lot of entries that have null or unknown. I'm not sure if this is coming from MSR expecting entries in a specific command class or if ZWaveJs is providing it to MSR that way.
Of all the actions in that window, the cover.xxx don't seem to work for me. The only ones that seem to work are:
x_hass_cover.close_cover_tilt
x_hass_cover.open_cover_tilt
x_hass_cover.set_cover_tilt_positionOthers may work, but these are the one's I know specifically work and from an automation perspective meet my needs.
-
@toggledbits I conducted some tests tonight.
MSR's ZWaveJSController
HA ZWaveJSController Plugin via HASending you an image since I can't upload any here for some reason (parser error) via your file share.
Results of my tests:
MSR's ZWJSC: no response
HA ZWJSC plugin: no response from any command other thanx_hass_cover.set_cover_tilt_position[latest-23242]2023-09-17T23:34:45.311Z <Rule:INFO> The Internet is up (rule-l2gdh04j in Notifications) evaluation complete [latest-23242]2023-09-17T23:34:45.312Z <Rule:INFO> Check Internet Status (rule-l2f9yuad in Reactor Alerts and Checks) evaluation complete [latest-23242]2023-09-17T23:34:45.313Z <Rule:INFO> HTTP Failed Alerts (rule-l2kd6w6k in Reactor Alerts and Checks) evaluation complete [latest-23242]2023-09-17T23:34:45.313Z <Rule:INFO> MSR Update Notifier (rule-l9vf6nai in Reactor Alerts and Checks) evaluation complete [latest-23242]2023-09-17T23:34:45.316Z <Rule:INFO> The Internet is up (rule-l2gdh04j in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23242]2023-09-17T23:34:45.317Z <Rule:INFO> Check Internet Status (rule-l2f9yuad in Reactor Alerts and Checks) starting evaluation; because entity-changed System#reactor_system>system [latest-23242]2023-09-17T23:34:45.317Z <Rule:INFO> HTTP Failed Alerts (rule-l2kd6w6k in Reactor Alerts and Checks) starting evaluation; because entity-changed System#reactor_system>system [latest-23242]2023-09-17T23:34:45.317Z <Rule:INFO> MSR Update Notifier (rule-l9vf6nai in Reactor Alerts and Checks) starting evaluation; because entity-changed System#reactor_system>system [latest-23242]2023-09-17T23:34:45.318Z <Rule:INFO> The Internet is up (rule-l2gdh04j in Notifications) trigger evaluation result is false (previously false) [latest-23242]2023-09-17T23:34:45.318Z <Rule:INFO> The Internet is up (rule-l2gdh04j in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23242]2023-09-17T23:34:45.320Z <Rule:INFO> Check Internet Status (rule-l2f9yuad in Reactor Alerts and Checks) trigger evaluation result is false (previously false) [latest-23242]2023-09-17T23:34:45.320Z <Rule:INFO> Check Internet Status (rule-l2f9yuad in Reactor Alerts and Checks) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23242]2023-09-17T23:34:45.321Z <Rule:INFO> HTTP Failed Alerts (rule-l2kd6w6k in Reactor Alerts and Checks) trigger evaluation result is false (previously false) [latest-23242]2023-09-17T23:34:45.321Z <Rule:INFO> HTTP Failed Alerts (rule-l2kd6w6k in Reactor Alerts and Checks) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23242]2023-09-17T23:34:45.322Z <Rule:INFO> MSR Update Notifier (rule-l9vf6nai in Reactor Alerts and Checks) trigger evaluation result is false (previously false) [latest-23242]2023-09-17T23:34:45.323Z <Rule:INFO> MSR Update Notifier (rule-l9vf6nai in Reactor Alerts and Checks) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23242]2023-09-17T23:34:45.323Z <Rule:INFO> The Internet is up (rule-l2gdh04j in Notifications) evaluation complete [latest-23242]2023-09-17T23:34:45.323Z <Rule:INFO> Check Internet Status (rule-l2f9yuad in Reactor Alerts and Checks) evaluation complete [latest-23242]2023-09-17T23:34:45.324Z <Rule:INFO> HTTP Failed Alerts (rule-l2kd6w6k in Reactor Alerts and Checks) evaluation complete [latest-23242]2023-09-17T23:34:45.324Z <Rule:INFO> MSR Update Notifier (rule-l9vf6nai in Reactor Alerts and Checks) evaluation complete [latest-23242]2023-09-17T23:34:45.346Z <Rule:INFO> Change to Night (via ESPresense) (rule-kwc6rmci in Mode Triggers) starting evaluation; because entity-changed ValueSensor#hass>sensor_john_iphone_battery_status [latest-23242]2023-09-17T23:34:45.349Z <Rule:INFO> Change to Night (via ESPresense) (rule-kwc6rmci in Mode Triggers) trigger evaluation result is false (previously false) [latest-23242]2023-09-17T23:34:45.349Z <Rule:INFO> Change to Night (via ESPresense) (rule-kwc6rmci in Mode Triggers) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23242]2023-09-17T23:34:45.350Z <Rule:INFO> Change to Night (via ESPresense) (rule-kwc6rmci in Mode Triggers) evaluation complete [latest-23242]2023-09-17T23:34:50.341Z <Rule:INFO> Change to Night (via ESPresense) (rule-kwc6rmci in Mode Triggers) starting evaluation; because entity-changed ValueSensor#hass>sensor_john_iphone_battery_status [latest-23242]2023-09-17T23:34:50.347Z <Rule:INFO> Change to Night (via ESPresense) (rule-kwc6rmci in Mode Triggers) trigger evaluation result is false (previously false) [latest-23242]2023-09-17T23:34:50.348Z <Rule:INFO> Change to Night (via ESPresense) (rule-kwc6rmci in Mode Triggers) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23242]2023-09-17T23:34:50.349Z <Rule:INFO> Change to Night (via ESPresense) (rule-kwc6rmci in Mode Triggers) evaluation complete [latest-23242]2023-09-17T23:34:51.559Z <HubitatController:INFO> HubitatController#hubitat ignoring DEVICE event for device 1405 (Sun Position); device not enumerated by Maker API [latest-23242]2023-09-17T23:34:51.600Z <HubitatController:INFO> HubitatController#hubitat ignoring DEVICE event for device 1405 (Sun Position); device not enumerated by Maker API [latest-23242]2023-09-17T23:34:51.662Z <HubitatController:INFO> HubitatController#hubitat ignoring DEVICE event for device 1405 (Sun Position); device not enumerated by Maker API [latest-23242]2023-09-17T23:34:55.352Z <Rule:INFO> Change to Night (via ESPresense) (rule-kwc6rmci in Mode Triggers) starting evaluation; because entity-changed ValueSensor#hass>sensor_john_iphone_battery_status [latest-23242]2023-09-17T23:34:55.357Z <Rule:INFO> Change to Night (via ESPresense) (rule-kwc6rmci in Mode Triggers) trigger evaluation result is false (previously false) [latest-23242]2023-09-17T23:34:55.357Z <Rule:INFO> Change to Night (via ESPresense) (rule-kwc6rmci in Mode Triggers) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23242]2023-09-17T23:34:55.359Z <Rule:INFO> Change to Night (via ESPresense) (rule-kwc6rmci in Mode Triggers) evaluation complete [latest-23242]2023-09-17T23:34:55.426Z <Engine:INFO> Enqueueing "Blinds DR Open" (re-kx6a2k13) **[latest-23242]2023-09-17T23:34:55.429Z <Engine:NOTICE> Starting reaction Blinds DR Open (re-kx6a2k13)** [latest-23242]2023-09-17T23:34:56.685Z <ZWaveJSController:5:ZWaveJSController.js:798> ZWaveJSController#zwavejs handling node event statistics updated entity Cover#zwavejs>22-0 [latest-23242]2023-09-17T23:34:56.767Z <ZWaveJSController:5:ZWaveJSController.js:798> ZWaveJSController#zwavejs handling node event value updated entity Cover#zwavejs>22-0 [latest-23242]2023-09-17T23:34:56.769Z <ZWaveJSController:5:ZWaveJSController.js:994> ZWaveJSController#zwavejs update node 22 value "0:106:targetValue:23" data [Object]{ "source": "node", "event": "value updated", "nodeId": 22, "args": { "commandClassName": "Window Covering", "commandClass": 106, "endpoint": 0, "property": "targetValue", "propertyKey": 23, "newValue": 50, "prevValue": 0, "propertyName": "targetValue", "propertyKeyName": "Horizontal Slats Angle" } } [latest-23242]2023-09-17T23:34:56.770Z <ZWaveJSController:5:ZWaveJSController.js:1006> ZWaveJSController#zwavejs updating attributes for node 22 value "0:106:targetValue:23"=50: [Array][ ] [latest-23242]2023-09-17T23:34:56.771Z <ZWaveJSController:5:ZWaveJSController.js:1025> ZWaveJSController#zwavejs setting Cover#zwavejs>22-0.x_zwave_values.Window_Covering_targetValue_23 to 50 [latest-23242]2023-09-17T23:34:56.782Z <ZWaveJSController:5:ZWaveJSController.js:798> ZWaveJSController#zwavejs handling node event value updated entity Cover#zwavejs>22-0 [latest-23242]2023-09-17T23:34:56.783Z <ZWaveJSController:5:ZWaveJSController.js:994> ZWaveJSController#zwavejs update node 22 value "0:106:currentValue:23" data [Object]{ "source": "node", "event": "value updated", "nodeId": 22, "args": { "commandClassName": "Window Covering", "commandClass": 106, "property": "currentValue", "propertyKey": 23, "endpoint": 0, "newValue": 50, "prevValue": 0, "propertyName": "currentValue", "propertyKeyName": "Horizontal Slats Angle" } } [latest-23242]2023-09-17T23:34:56.785Z <ZWaveJSController:5:ZWaveJSController.js:1006> ZWaveJSController#zwavejs updating attributes for node 22 value "0:106:currentValue:23"=50: [Array][ "cover.state", "position.value" ] [latest-23242]2023-09-17T23:34:56.787Z <ZWaveJSController:5:ZWaveJSController.js:1013> ZWaveJSController#zwavejs updating attribute cover.state with [Object]{ "entity": "22-0", "impl": { "expr": "!(value == 0 || value >= 99)", "valueId": "106:currentValue:23" } } [latest-23242]2023-09-17T23:34:56.787Z <ZWaveJSController:5:ZWaveJSController.js:947> ZWaveJSController#zwavejs _apply_value entity Cover#zwavejs>22-0 cover.state [latest-23242]2023-09-17T23:34:56.788Z <ZWaveJSController:5:ZWaveJSController.js:987> ZWaveJSController#zwavejs _apply_value cover.state=true [latest-23242]2023-09-17T23:34:56.789Z <ZWaveJSController:5:ZWaveJSController.js:1013> ZWaveJSController#zwavejs updating attribute position.value with [Object]{ "entity": "22-0", "impl": { "expr": "round( value / 99, 2 )", "valueId": "106:currentValue:23" } } [latest-23242]2023-09-17T23:34:56.790Z <ZWaveJSController:5:ZWaveJSController.js:947> ZWaveJSController#zwavejs _apply_value entity Cover#zwavejs>22-0 position.value [latest-23242]2023-09-17T23:34:56.791Z <ZWaveJSController:5:ZWaveJSController.js:987> ZWaveJSController#zwavejs _apply_value position.value=0.51 [latest-23242]2023-09-17T23:34:56.792Z <ZWaveJSController:5:ZWaveJSController.js:1025> ZWaveJSController#zwavejs setting Cover#zwavejs>22-0.x_zwave_values.Window_Covering_currentValue_23 to 50 [latest-23242]2023-09-17T23:34:56.807Z <HassController:INFO> HassController#hass action x_hass_cover.set_cover_tilt_position([Object]{ "tilt_position": 50 }) on Cover#hass>cover_dining_room2_horizontal_slats_angle succeeded [latest-23242]2023-09-17T23:34:56.809Z <Engine:INFO> Resuming reaction Blinds DR Open (re-kx6a2k13) from step 1 [latest-23242]2023-09-17T23:34:56.810Z <Engine:NOTICE> Blinds DR Open delaying until 1694993697809<9/17/2023, 7:34:57 PM> [latest-23242]2023-09-17T23:34:56.930Z <ZWaveJSController:5:ZWaveJSController.js:798> ZWaveJSController#zwavejs handling node event statistics updated entity Cover#zwavejs>22-0 [latest-23242]2023-09-17T23:34:57.811Z <Engine:INFO> Resuming reaction Blinds DR Open (re-kx6a2k13) from step 2 [latest-23242]2023-09-17T23:34:57.812Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.refresh on Cover#zwavejs>7-0 with [Object]{ } [latest-23242]2023-09-17T23:34:57.814Z <ZWaveJSController:5:ZWaveJSController.js:1750> ZWaveJSController#zwavejs no implementation mapped; attempting default [latest-23242]2023-09-17T23:34:57.815Z <ZWaveJSController:5:ZWaveJSController.js:751> ZWaveJSController#zwavejs sending #1694993697815<9/17/2023, 7:34:57 PM>: [Object]{ "command": "node.refresh_values", "nodeId": 7, "messageId": 1694993697815 } [latest-23242]2023-09-17T23:34:57.830Z <ZWaveJSController:5:ZWaveJSController.js:778> ZWaveJSController#zwavejs command result error: [Object]{ "type": "result", "success": false, "messageId": 1694993697815, "errorCode": "node_not_found", "args": { "nodeId": 7 } } [latest-23242]2023-09-17T23:34:57.832Z <ZWaveJSController:ERR> ZWaveJSController#zwavejs request 1694993697815<9/17/2023, 7:34:57 PM> (node.refresh_values) failed: [Error] node_not_found [-] [latest-23242]2023-09-17T23:34:57.834Z <Engine:INFO> Resuming reaction Blinds DR Open (re-kx6a2k13) from step 3 [latest-23242]2023-09-17T23:34:57.835Z <Engine:INFO> Blinds DR Open all actions completed.If you'd like the whole log I can upload that as well or anything else you need for review.
-
Yeah, a clean log would be good to review. In your
logging.yaml, please add the following (if there's already a section for ZWaveJSController, just modify it to make it look like this):ZWaveJSController: level: 5 streams: - type: file name: zwavejs.log keep: 2 level: 999 recycle: trueRestart Reactor and run a test (or a few) of
cover.openandcover.closeandposition.set. Then copy just thezwavejs.logfile up together with your latestzwavejs_devices_initial.jsonto link I sent you earlier. Thank you! -
@toggledbits I actually had that logging enabled already and didn't realize/remember it.
Scenarios tested:
Test #1: 22-0 ~10:20 ET
ZWJSC,cover.close
Result: blind closed, "inside down"
ZWJSC,cover.open
Result: blind opened, position=50%
Repeated, same resultsTest #2: 22-0
ZWJSC,position.set = 0
Result: blind closed, "inside up"
ZWJSC,position.set = .5
Result: blind opened, position=50%
Repeated, same resultsTest #3: 22-0
ZWJSC,cover.close
Result: blind closed, "inside down"
ZWJSC,cover.open
Result: blind opened, position=50%
Repeated, same resultsUnfortunately, everything WAI. Kinda frustrated at the moment. Same blind as last night's testing when nothing responded. Log being uploaded momentarily.
-
@gwp1 ,
Not to steal your thread, but out of curiosity, have you noticed any issues with battery life lately? I've noticed that a few of my iBlinds are draining very rapidly, ending in a unresponsive state. I've charged them, then less than a week later, they are dead and unresponsive.They all appear to be the older v2 iBlinds, so it could just be that the batteries are ending their useful life, however, it's also possible that the new configuration and command class is affecting them in some way. I'm gradually replacing them, as I've found the v3.1 iBlinds to be much more reliable. I haven't noticed this behavior in the v3.1 iBlinds.
I'm just curious if you've seen this as well. If you are seeing it, it could be an issue with how ZWaveJS is communicating with the iBlinds due to this new roleout.
-
@tamorgen Not entirely stealing or off-topic as that has played a role before in iblind responsiveness. I have solar panels on mine - 50/50 on how well they work. My blinds are all v3.1, btw, @toggledbits, just as a point of reference.
I have found if ZWaveJS HA Plugin shows anything under 60% battery the blinds become unresponsive. A quick plug of the power cable and a tap of the
pingbutton and the physical button on the blind itself and they come back.For this specific topic, all tested blinds are either plugged in or showing 100% battery.
-
@gwp1,
I'm working on trying to make something useful in the dashboards using this new device class, and it's not going well. I've reached out to iBlinds/Eric B for help. What we are both seeing as unknown/null states could be a problem.There are three values that are null or unknown: cover.state, position.value, and then a repeat using the x_hass.state.
When I go into Developer Tools in HA, the state is unknown as well. That makes sense since MSR has to grab it from somewhere.
I'm trying to work on my dashboard and display some useful information, and I'm unable to get the value of the attributes. I'm guessing that's because the State is unknown.
Hopefully iBlinds can work with HA and ZWaveJS and get these values to show properly.
-
Yeah, logs confirm everything going out as expected, ZWJS acknowledging the request, and also sending a notification for a value change asynchronously. ZWaveJSController appears to be doing the right things. ZWaveJS appears to be doing its part as well.
-
@toggledbits I'm conducting an experiment.
DR2 blind (22-0) is configured as
[Default]direction and using MSRs ZWJSController. I have set the threeReactionsto:DR OPEN:
cover.open
DR CLOSE:cover.close
DR @25:position.set=.75(resulting in the blind being tilted open 25%, "top inside").All other iblinds are using HA's ZWJSC plugin and all ran flawlessly for the past 24 hours. I'm wondering if this issue is somehow load-induced. If this single blind remains solid I will add a second and so on.
UPDATE: as my patience level on any given day runs the gamut between saint and toddler I've added KITCHEN (18-0) to this test with the same settings as above excepting
.80instead of.75. Both of these iblinds were the most impacted in being unresponsive. -
@toggledbits we have fail!
Added two more iblinds to the test. They failed to respond so I isolated one of them and did the following tests on
node8-0:LR Left OPEN:
cover.open
LR Left CLOSE:cover.close
LR Left @20:position.set=.80(resulting in the blind being tilted open 20%, "top inside").Results:
cover.open= iblind opens, position of50
cover.close= iblind moves to position of50<---expected result, position0
position.set= iblind moves to position of80As this
Reactionwas to run BOTH left and right blinds I removed the right blind and ran the left solo as the kitchen and DR are (both still working fine, btw). For reference, Kitchen was existing unit and was re-interviewed to be current, DR is a brand new unit. LR's are existing units re-interviewed.Log forthcoming.
-
@gwp1, I just replaced 6 of my ib2 motors with ib3.1, and they are working just fine (12 of 14 are v3.1). I can control them from MSR with ZWJSController without issue.
My only issue is actually Home Assistant itself. I've had to go to great lengths to get a somewhat working card for each of the blinds in my home, and I'm still not completely there yet. I'm hoping either the ZWaveJS devlopers or the HA developers figure out whats going on with the 'state' value for each of these, as they all return 'unknown', so none of the cards work out of the box.
-
@tamorgen said in [SOLVED-ish] New iblind and zwaveJScontroller/MSR not communicating:
they are working just fine (12 of 14 are v3.1). I can control them from MSR with ZWJSController without issue.
It's more helpful if, instead of generalized statements, you provide settings/configurations you're using whilst having this success for comparison sake.
I ran into an issue this morning wherein, after completing the weekly
zwave_device.set_config, the iblinds finish in a closed position but reporting back in all systems (HA, both ZWJSC's, and MSR) as50oropen. I've created a workaround wherein, after completing the config, they wait a few seconds then tilt 20% and then set back to open. -
@gwp1 said in [SOLVED-ish] New iblind and zwaveJScontroller/MSR not communicating:
It's more helpful if, instead of generalized statements, you provide settings/configurations you're using whilst having this success for comparison sake.
All of mine are like this, cover.close, cover.open.
Perform cover.close on Office Blind Left (zwavejs>30-0) Delay for 5 seconds Perform cover.close on Office Blind Right (zwavejs>31-0) Delay for 5 seconds Perform zwave_device.refresh on Office Blind Left (zwavejs>30-0) Perform zwave_device.refresh on Office Blind Right (zwavejs>31-0)I'm not even sure the zwave.device.refresh is needed anymore. This was more of an issue when trying to force the old device class to refresh on both the binary switch and the multi-level switch, as they weren't directly connected and didn't update each other. It was one of the reasons that the folks at iBlinds were pushing to get the window device class implemented.
-
@tamorgen I see you doing the delay as I do. How do you do a weekly config? (The blinds will "drift" if not config'd weekly or bi-weekly.
I have removed the
zwave_device.refreshto see how that goes.Question: you have a great number of blinds in your fleet as do I - how many blinds do you group together? I see you grouped two for your office blinds, do you have more than two at a time grouped in a single reaction? Or are you skipping
reactionsand adding eachentityin eachruleset? -
@gwp1 ,
I really don't have any sort of weekly config on mine. I haven't noticed mine drifting at all, but a weekly recalibrate wouldn't be a bad idea.
I have rules for hourly refreshing the the cover, position, and switch positions that are now pretty much legacy of the old device class. I only have two of the IB2 devices left, and they're in non critical rooms ( guest bedroom and mudroom). I'll replace those later this year. Once those are gone, I'll be able to remove those three hourly rules.
I have reactions set up for each set of windows in a room. Most rooms only have two windows, so I group those. The lone exception is my family room, where I have four windows, but on different walls. I have those set up on two separate reactions, which allows me to separately set the blinds to a partial open position when the sun is shining directly in. The largest events with the blinds are at sunrise, sunset, and when the house is vacant or someone arrives, when I'll set the reactions from the rule, and I have "Wait for completion" enabled after each call for a reaction. It takes a couple of minutes for all my blinds to open/close when it's called. I initially didn't do this, but iBlinds recommended not calling them all at once (thus the pause in between each call for a blind to open/close). For the most part, this has helped tremendously with the IB2 motors, although they still had their fair share of problems, which is why I've been replacing them all this year.
I call the reactions from rulesets, so I don't have to reinvent the wheel each time I want to perform an action on a window. It also allows me to make an adjustment once and not 10 different times in different rules.