Hi guys,
Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular.
Maybe there are better ways to organize my rule sets.
I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
I have installed MSR on a RP5 bare metal and then copied the config and store files. Everything seems to be on the RP5 but I am missing all global expression and I don't see the controller time.
Screenshot 2025-04-06 201446.png
My browser is Microsoft Edge Version 135.0.3179.54 (Official build) (64-bit)
I have probably done something stupid or missed a step but I am stuck.
Thanks for any help.
Hi,
It seems that the widget deletion does not work. I tried to drag the widget to the left (as explained in here https://smarthome.community/topic/1071/deleting-widgets?_=1744037333660)
but it does not delete it. Anyone else experiencing the same problem?
Also the landing page after login is empty and seems be have some JS issues on the dev console:
Screenshot from 2025-04-07 18-06-19.png
fd7f0424-debb-49d3-86d8-9a3b09ad3868-image.png
Using dockerized version of Reactor (Multi-hub) latest-25082-3c348de6 on Chromium 135.0.7049.52 (Official Build) snap (64-bit)
br,
mgvra
Good day all,
I have an notification set up for my washing machine to let me know when it's complete. I have a templete sensor set up in HAAS to let me know if it's Washing, in Standby, or off, based upon the power consumption (Shelly 1PM on outlets)
The MSR code is relatively simple. I have a built in false positive attribute for if MSR gets rebooted, because I would suddenly get tons of notifications when I upgraded MSR.
6774565a-06cc-443f-99c1-e71301b33d83-image.png
What I'm trying to introduce, is a way to verify that I just didn't bump the knob on the washing machine when transferring loads from the washer to the dryer, which turns on the display and brings the power above the Standby threshold.
The power goes up to 3.7W for about 4 minutes if the selector knob is bumped/turned.
What would the best way to do this be? I have most of my MSR code set up for a couple of years now, and my coding logic is struggling a bit.
I think I need a power threshold to be substained for a minimum time period (say 2 or 3 minutes, above 10W), before the other triggers can act. What would the best way to do that be?
Running: latest-25082-3c348de6
Fedora 41 Server
HAAS:
Core
2025.3.4
Supervisor
2025.03.4
Operating System
15.1
Frontend
20250306.0
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 have the following yaml configuration in local_mqtt_devices file
x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }'While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Hi!
I get this message when I'm on the status tab:
System Configuration Check
The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds.
I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6.
HA versions are:
Core 2025.3.4
Supervisor 2025.03.4
Operating System 15.1
I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version.
Do anyone know what I can try?
Thanks in advance!
Let's Be Careful Out There (Hill Street reference...) 🙂
/Fanan
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB.
While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed.
So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response.
While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits
Thanks!
Hi ,
I'm on
-Reactor (Multi-hub) latest-25067-62e21a2d
-Docker on Synology NAS
-ZWaveJSUI 9.31.0.6c80945
Problem with ZwaveJSUI:
When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white.
I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui.
I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb".
After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color.
This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite.
x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33}The "cold white" and "warm white" settings interfer with the rgb color settings.
Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white
are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white.
So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have
x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColorIn zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set.
x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this?
x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33}Thanks in advance.
Good day all,
I have a reaction set up, that I use for both troubleshooting and changing home modes when one of my family members either arrive or are leaving. I use the companion app for HAAS on our iPhones, and HAAS reports if the person associated with the iPhone enters or leaves the geofenced area around my home. I'm sure most MSR and HAAS users are familiar with this.
I use this rule set mainly as a condition for other rules, however, as part of troubleshooting, a notification is sent through HAAS to the companion app when the rule becomes true. The problem is that I'm getting notifications now for both arriving and departing simultaneously.
96b3f7db-ba09-499e-a78c-86903b603857-image.png
36903cdd-a87f-473b-82ef-af9ef96d3c44-image.png It used to work fine as intended. I'm not sure exactly when it changed, but now I'm getting two notifications when either of these conditions change.
Any idea what could be happening?
Edit:
Running: latest-25082-3c348de6, bare-metal Linux
ZWaveJSControllerr [0.1.25082]
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem?
I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Similarly as for local expressions, global expressions evaluate and update fine when getEntity(...) structure is used. However, at least when certain functions are in use, expressions do not update.
Consider the following test case:
Screenshot 2025-03-13 at 16.29.42.png
Even though auto-evaluation is active, value does not change (it changes only if that expression is manually run). MSR restarts do not help.
Screenshot 2025-03-13 at 16.31.43.png
Note: Tested using build 25067 on Docker. I have also a PR open (but couldn't now get details or PR number as my Mantis account was somehow expired?).
Trying to understand what cause a local expresssion to be evaluated. I have read the manual but I am still not clear about it. Using the test rule below, I can see in the log that the rule is being automatically evaluated every time the temperature entity is changing. That is great...
What I am trying to understand is why the expression is not evaluated based on time as well since the "case" statement has time dependencies.
Any help would be appreciated
I have the following test rule:
eba6a3ea-ff61-4610-88c9-9b9864f11ff8-Screenshot 2025-01-21 095244.png
2d9c1ff5-7b73-4005-b324-9029c2709db9-Screenshot 2025-01-21 095302.png
Here is the expressioncode:
vFrom1 = "09:25:00", vFrom2 = "09:30:00", vFrom3 = "09:41:00", vTo = "10:55:00", # Get current time (format HH:MM:SS) vToDay = strftime("%H:%M:%S"), #Get current house temperature CurrentHouseTemp = getEntity( "hass>Thermostat2 " ).attributes.temperature_sensor.value, case when CurrentHouseTemp <= 19 and vToDay >= vFrom1 && vToDay <= vTo: "true1" # From1 when CurrentHouseTemp <= 20 and vToDay >= vFrom2 && vToDay <= vTo: "true2" # From2 when CurrentHouseTemp < 26 and vToDay >= vFrom3 && vToDay <= vTo: "true3" # From3 else "false" endI am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved.
The Runtime Error is different in the two browsers
Safari v18.3
Google Chrome 133.0.6943.142
TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.Steps to reproduce:
Click the pencil to edit a global reaction with a group.
Click the Exit button.
Runtime error appears.
or
Click Create Reaction
Click Add Action
Select Group
Add Condition such as Entity Attribute.
Add an Action.
Click Save
Click Exit
Runtime error appears.
I don’t know how long the error has been there as I haven’t edited the global reaction in a long time.
Reactor (Multi-hub) latest-25060-f32eaa46
Docker
Mac OS: 15.3.1
Thanks
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons.
I have not created a global expression for some times and just noticed this while doing some clean-up.
I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success.
Here's what the log shows.
[latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" }Reactor latest-25067-62e21a2d
Docker on Synology NAS
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method.
This was prompted by yesterday's fun and games with my ISP.
I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone)
I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions?
TIA
C
Hi,
I'm trying to integrate the sonos-mqtt (https://sonos2mqtt.svrooij.io/) with the MSR and it's coming along nicely so far.
But cannot wrap my head around how to define custom capabilities in MQTT templates. I need this for the TTS announcements and similarly for the notification sounds where I would pass the sound file as parameter.
So this is what I have in the local_mqtt_devices.yaml
capabilities: x_sonos_announcement: attributes: actions: speak: arguments: text: type: string volume: type: int delay: type: intAnd this is the template:
templates: sonos-announcement: capabilities: - x_sonos_announcement actions: x_sonos_announcement: speak: topic: "sonos/cmd/speak" payload: expr: > { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" } type: jsonSo the speak action should send something like this to topic sonos/cmd/speak
{ "text": "message goes here", "volume": 50, "delayMs": 100, "onlyWhenPlaying": false, "engine": "neural" }At startup the MSR seems to be quite unhappy with my configuration:
reactor | [latest-25016]2025-02-09T08:19:59.029Z <MQTTController:WARN> MQTTController#mqtt entity Entity#mqtt>sonos-announcement unable to configure capabilities [Array][ "x_sonos_announcement" ] reactor | i18n: missing fi-FI language string: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | i18n: missing fi-FI language string: Configuration for {0:q} has unrecognized capability {1:q} in actions reactor | Trace: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | at _T (/opt/reactor/server/lib/i18n.js:611:28) reactor | at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:125:25) reactor | at MQTTController.sendWarning (/opt/reactor/server/lib/Controller.js:627:30) reactor | at MQTTController.start (/var/reactor/ext/MQTTController/MQTTController.js:268:26) reactor | at async Promise.allSettled (index 0) Configuration for "sonos-announcement" has unrecognized capability "x_sonos_announcement" in actions Controller: MQTTController#mqtt Last 10:21:37 AM Configuration for "sonos-announcement" is incomplete because the following requested capabilities are undefined: x_sonos_announcement Controller: MQTTController#mqtt Last 10:21:37 AMThis is probably a pretty stupid question and the approach may not even work at all, but maybe someone or @toggledbits for sure, could point me to the right direction.
Basically the idea is to be able to send TTS messages from reactions using entity actions. I've previously used HTTP requests to Sonos HTTP API (https://hub.docker.com/r/chrisns/docker-node-sonos-http-api/) for the same functionality, but since moving to sonos-mqtt, I need a way to send the TTS notifications using MQTTController. Along with the actual message, volume and delay must also be parameterizable.
br,
mgvra
MSR latest-25016-d47fea38 / MQTTController [0.2.24293]
Hi, @toggledbits
I just noticed that following a reboot of my raspberry pi, some of the rules, that I was expecting to recover, are not catching up following a reboot. I have made a simple test rule (rule-m6rz6ol1) with only "after Date/time" as trigger and "turn on a lamp" as a set reaction. All my infrastructure is on the same board so Reactor, Hass, Zwavejs, ... are all rebooting.
Here is the sequence of the test case (All time converted to Zulu to match logs):
Rule "after Date/Time" set to 14:05:00z Shutdown on Raspberry Pi at 14:04:00z Power back up at 14:08:00z Rule overview shows true as of 14:08:14z waiting for 00:00:00 in GUIFrom the log I can see that MSR is picking up the rule and knows that the state of the rule has changed from false to true and tries to send the update to HASS but failed with websocket error.
Here is what I see from the log:
14:04:04z shutdown complete 14:08:08z Power up 14:08:13.111z websocket connection 14:08:15:323z Reaction to the light failed, Websocket not opened After there is a series of websocket connection attempt until 14:08:51z where it seemed to be really ready.Back in 2021 we had a discussion (https://smarthome.community/topic/700/solved-start-up?_=1738766986566) and you proposed to add a startup_delay:xxxx and startup_wait:xxxx parameter in the engine section of "reactor.yaml". When I try the startup_delay (this used to be a hard delay), the engine failed to start (I think). I then try the startup_wait:xxxx without any success. Since it wait for the connection status to be up to cancel the delay, it does not do anyting since Hass is reporting the socket up without really being up ( I think...).
Questions:
Did I figured it all wrong? should the startup_delay:xxxxx have worked? Any ideas?Here is the log:
OK now I am stuck. I did add the log but when I submit the editor complained saying that I am limited to 32767 characters. The log from the shutdown to the time the websocket is stable is about 300000 character long. What are my options?
Not a big issue simply a request if easily doable.
The MSR logs files inside the container are owned by root witch is fine however, the permissions are very restrictive. I do not know if there is something wrong with my installation but the logs permission are set to 222 (write only). Even if the docker volume is set for Read/Write the log files are retaining these values.
I go around the problem by doing a chmod 777 on all reactor logs but every time there is an MSR log rotation the permissions are set back to 222. So unless the permission are implemented in the container there is no permanent solution to this (that I know of).
I do not know much about Docker container so I do not know what is involved here.
Can the logfiles permission be simply chaged in the container to at least allow "other" read permission?
Could the MSR log rotation routine implement a chmod to set the permission?
Just a small anoyance
Thanks
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
-
@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.
-
@tamorgen we are very much aligned in our approach.
- My office has four windows, one front-facing and three smaller side-facing. I group the three together.
- My main room covers the single kitchen, single dining room, and two paired living room blinds.
- My master bedroom has two paired together, the master bath a single that I do not group with the bedroom.
- Guest rooms are single independents.
I, too, do reactions for:
- open (Day)
- close (Evening/Night)
- tilt (this is used for Away for all, also for "sun defer" as the sun moves around the house)
I do
reactionsas well for the very same reason: single place to edit. I know @toggledbits will cringe but my "Open ALL" , "Tilt ALL", and "Close ALL" arereactionsthat contain the other room-specificreactionsand are called byrulesets.I've increased my
delaysagain back to 00:00:05 (was down to 00:00:02) just to see if that may help the initial issue that spawned this topic. I don't need to have all blinds close at once (sure, it would be cool) - it's still fun for guests when the actions start in the office at the front of the house and just file their way around until all are completed. -
@gwp1 said in [SOLVED-ish] New iblind and zwaveJScontroller/MSR not communicating:
Log forthcoming.
Looked at the log. ZWaveJSController is consistently, correctly issuing the right commands and values for all actions in every case. ZWaveJS is responding with a successful acknowledgement of the command, and later passing an update notification with the node's position having a value consistent with the command previously given in every case. It appears that ZWaveJS understands what MSR is asking it to do, sending that to the device, and the device is sending back updates indicating it has done what has been asked. If that's not what the device actually does, then I assert it's firmware or hardware issue with the device.
The log contains errors for an attempt to refresh (using the
zwave_device.refreshaction) non-existent node 7 (that is, ZWaveJS reports that the node doesn't exist; the entity may still exist as a zombie). That has no effect operationally, just bringing to your attention that after excluding/including devices, you may have missed a now-dead entity. -
@toggledbits Node 7-0 has cleaned itself up in MSR (it was cleared out in HA's ZWJSC). I got the same from the logs, was hoping you would see something I missed.
The firmware is on the latest. I'll doublecheck the firmware on the ZWave Stick that runs these from HA. Thanks @toggledbits, as usual.
Updating this thread to
[SOLVED]as whatever the issue may be it's not MSR's. -
T toggledbits locked this topic on