Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. [SOLVED] New iblind and zwaveJScontroller/MSR not communicating
Moving MSR from a QNAP container to RP 5 - some issues
T

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.

Multi-System Reactor about 5 hours ago
Need help reducing false positive notifications
T

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)

- name: "Washing Machine" state: > {% if states("sensor.washer_switch_0_power")|float == 0 %} Off {% elif states("sensor.washer_switch_0_power")|float <= 2.9 %} Standby {% else %} Washing {% endif %} icon: > {% if states("sensor.washer_switch_0_power") == "off" %} mdi:washing-machine-alert {% elif states("sensor.washer_switch_0_power")|float <= 2.9 %} mdi:washing-machine-off {% else %} mdi:washing-machine {% endif %} minutes: 2

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

Multi-System Reactor about 10 hours ago
Widget deletion does not work and landing page (status) is empy
M

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

Multi-System Reactor about 13 hours ago
Reactor (Multi-System/Multi-Hub) Announcements
T

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.
Multi-System Reactor a day ago
Deleting widgets
T

Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266

Multi-System Reactor a day ago
MQTT configuration question
T

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?

Multi-System Reactor 6 days ago
System Configuration Check - time is offset
F

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

Multi-System Reactor 6 days ago
Programmatically capture HTTP Request action status code or error
therealdbT

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!

Multi-System Reactor 8 days ago
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N

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: currentColor

In 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=33

Is 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.

Multi-System Reactor 9 days ago
Problem with simultaneous notifications.
T

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]

Multi-System Reactor 9 days ago
Problem after upgrading to 25067
R

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.

Multi-System Reactor 14 days ago
Global expressions not always evaluated
T

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?).

Multi-System Reactor 16 days ago
[Solved] Local expression evaluation
V

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" end
Multi-System Reactor 27 days ago
[Solved] Runtime error when exiting global reaction that contains a group
S

I 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

@http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 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.

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

Multi-System Reactor 29 days ago
Cannot delete Global Expressions
SnowmanS

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

Multi-System Reactor Mar 9, 2025, 2:32 AM
Local notification methods?
CatmanV2C

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

Multi-System Reactor Feb 14, 2025, 5:08 PM
Custom capabilities in MQTT templates
M

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: int

And 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: json

So 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 AM

This 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]

Multi-System Reactor Feb 11, 2025, 1:28 PM
[SOLVED]Hass websocket falsely reporting ready on boot??
V

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 GUI

From 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?

Multi-System Reactor Feb 10, 2025, 7:45 PM
[SOLVED]Logs permissions for Docker Install
V

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

Multi-System Reactor Feb 8, 2025, 6:05 PM
Button.Since Revisited
SnowmanS

@toggledbits In the MSR documentation, under Standard Capabilities, I noticed that the
button.since attribute was deprecated as of version 22256 and the metadata is the preferred way to access the last-modified time of an attribute.

Am I reading this right? Should I stop using it in my rules?

Thanks

Multi-System Reactor Feb 7, 2025, 2:14 AM

[SOLVED] New iblind and zwaveJScontroller/MSR not communicating

Scheduled Pinned Locked Moved Multi-System Reactor
solved
44 Posts 3 Posters 3.4k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    gwp1
    wrote on Sep 8, 2023, 5:48 AM last edited by gwp1 Sep 24, 2023, 6:00 PM
    #1

    I installed a new iblind this evening and it is appearing in ZWaveJS. It is operational thru Home Assistant just fine. It is operational thru the HA ZwaveJS plugin just fine.

    Where it is non-responsive is in MSR for some reason. The entities are there. Adding the node to a Reaction and then attempting to run said Reaction nets me this:

    [latest-23242]2023-09-08T05:33:08.454Z <ZWaveJSController:5:ZWaveJSController.js:655> ZWaveJSController#zwavejs _apply_value motion_sensor.state=false
[latest-23242]2023-09-08T05:33:08.455Z <ZWaveJSController:5:ZWaveJSController.js:722> ZWaveJSController#zwavejs setting Binary Sensor#zwavejs>11-0.x_zwave_values.Binary_Sensor_Motion to false
[latest-23242]2023-09-08T05:33:08.692Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event statistics updated entity Binary Sensor#zwavejs>11-0
[latest-23242]2023-09-08T05:40:23.960Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing cover.open on Cover#zwavejs>20-0 with [Object]{  }
[latest-23242]2023-09-08T05:40:23.962Z <ZWaveJSController:5:ZWaveJSController.js:1843> ZWaveJSController#zwavejs no implementation mapped; attempting default
[latest-23242]2023-09-08T05:40:25.062Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.refresh on Cover#zwavejs>20-0 with [Object]{  }
**[latest-23242]2023-09-08T05:40:25.063Z <ZWaveJSController:5:ZWaveJSController.js:1843> ZWaveJSController#zwavejs no implementation mapped; attempting default**
[latest-23242]2023-09-08T05:40:25.065Z <ZWaveJSController:5:ZWaveJSController.js:294> ZWaveJSController#zwavejs sending #1694151625064<9/8/2023, 1:40:25 AM>: [Object]{ "command": "node.refresh_values", "nodeId": 20, "messageId": 1694151625064 }
[latest-23242]2023-09-08T05:40:26.307Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event statistics updated entity Cover#zwavejs>20-0
[latest-23242]2023-09-08T05:40:26.317Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event value updated entity Cover#zwavejs>20-0
[latest-23242]2023-09-08T05:40:26.318Z <ZWaveJSController:5:ZWaveJSController.js:667> ZWaveJSController#zwavejs update node 20 value "0:128:level:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 20, "args": { "commandClassName": "Battery", "commandClass": 128, "property": "level", "endpoint": 0, "newValue": 100, "prevValue": 100, "propertyName": "level" } }
[latest-23242]2023-09-08T05:40:26.319Z <ZWaveJSController:5:ZWaveJSController.js:684> ZWaveJSController#zwavejs updating attributes for node 20 value "0:128:level:"=100: [Array][ "battery_power.level", "battery_power.since" ]
[latest-23242]2023-09-08T05:40:26.320Z <ZWaveJSController:5:ZWaveJSController.js:698> ZWaveJSController#zwavejs updating attribute battery_power.level with [Object]{ "entity": "20-0", "impl": { "expr": "float( value ) / 100", "valueId": "128:level:" } }
[latest-23242]2023-09-08T05:40:26.321Z <ZWaveJSController:5:ZWaveJSController.js:591> ZWaveJSController#zwavejs _apply_value entity Cover#zwavejs>20-0 battery_power.level
[latest-23242]2023-09-08T05:40:26.322Z <ZWaveJSController:5:ZWaveJSController.js:655> ZWaveJSController#zwavejs _apply_value battery_power.level=1
[latest-23242]2023-09-08T05:40:26.323Z <ZWaveJSController:5:ZWaveJSController.js:698> ZWaveJSController#zwavejs updating attribute battery_power.since with [Object]{ "entity": "20-0", "impl": { "expr": "time()", "valueId": "128:level:" } }
[latest-23242]2023-09-08T05:40:26.323Z <ZWaveJSController:5:ZWaveJSController.js:591> ZWaveJSController#zwavejs _apply_value entity Cover#zwavejs>20-0 battery_power.since
[latest-23242]2023-09-08T05:40:26.324Z <ZWaveJSController:5:ZWaveJSController.js:655> ZWaveJSController#zwavejs _apply_value battery_power.since=1694151626324<9/8/2023, 1:40:26 AM>
[latest-23242]2023-09-08T05:40:26.325Z <ZWaveJSController:5:ZWaveJSController.js:722> ZWaveJSController#zwavejs setting Cover#zwavejs>20-0.x_zwave_values.Battery_level to 100
[latest-23242]2023-09-08T05:40:26.333Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event value updated entity Cover#zwavejs>20-0
[latest-23242]2023-09-08T05:40:26.334Z <ZWaveJSController:5:ZWaveJSController.js:667> ZWaveJSController#zwavejs update node 20 value "0:128:isLow:" data [Object]{ "source": "node", "event": "value updated", "nodeId": 20, "args": { "commandClassName": "Battery", "commandClass": 128, "property": "isLow", "endpoint": 0, "newValue": false, "prevValue": false, "propertyName": "isLow" } }
[latest-23242]2023-09-08T05:40:26.336Z <ZWaveJSController:5:ZWaveJSController.js:324> ZWaveJSController#zwavejs request 1694151625064<9/8/2023, 1:40:25 AM> (node.refresh_values) success notification
[latest-23242]2023-09-08T05:40:26.337Z <ZWaveJSController:5:ZWaveJSController.js:684> ZWaveJSController#zwavejs updating attributes for node 20 value "0:128:isLow:"=false: [Array][  ]
[latest-23242]2023-09-08T05:40:26.338Z <ZWaveJSController:5:ZWaveJSController.js:722> ZWaveJSController#zwavejs setting Cover#zwavejs>20-0.x_zwave_values.Battery_isLow to false
[latest-23242]2023-09-08T05:40:26.558Z <ZWaveJSController:5:ZWaveJSController.js:360> ZWaveJSController#zwavejs handling node event statistics updated entity Cover#zwavejs>20-0

    Please note the highlighted logpart - no other iblind has this. In addition, in MSR>Entities several show as null rather than having a value as the others do.

    69631fbc-db4e-4e8d-aa98-10565811cd93-image.png

    I tried deleting all Entities associated with this device from MSR and then refreshing ZWaveJS in Home Assistant and restarting MSR - the Entities return but in the same state/s.

    Admittedly, it's been a very long three weeks at work - I could have missed something obvious during setup but I sure can't figure what it is.

    *Hubitat C-7 2.4.1.151
    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

    *HASS 2025.3.4
    w/ ZST10-700 fw 7.18.3

    *Prod MSR in docker/portainer
    MSR: latest-25082-3c348de6
    MQTTController: 24257
    ZWave Controller: 25082

    1 Reply Last reply
    0
    • T Offline
      T Offline
      toggledbits
      wrote on Sep 8, 2023, 12:04 PM last edited by
      #2

      Can you paste all of the attributes for zwavejs>20-0? There's a "Copy Attributes" button when you expand the entity in the Entities list. Remember to format it as code when pasting here.

      I'm heading to a field training exercise, so I may not get a chance to look at this in depth until late Sunday.

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      G 1 Reply Last reply Sep 8, 2023, 1:54 PM
      0
      • G Offline
        G Offline
        gwp1
        replied to toggledbits on Sep 8, 2023, 1:54 PM last edited by
        #3

        @toggledbits As requested:

        battery_power.since=1694178019327
cover.state=null
position.value=null
x_debug.dt={"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=7","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state","description":"Window Blind Controller","model":"iblinds V3","default_name":"Window Blind Controller","values":[{"valueId":"38:currentValue:","capabilities":{"cover":{"attributes":{"state":{"expr":"!(value == 0 || value >= 99)"}},"actions":{"open":{"valueId":"38:targetValue:","value":50},"close":{"valueId":"38:targetValue:","value":99},"stop":false}},"position":{"attributes":{"value":{"expr":"round( value / 99, 2 )"}},"actions":{"set":{"valueId":"38:targetValue","value":{"expr":"max( 0, min( 99, round( 100 * ( parameters.value ?# 0 ), 0 ) ) )"}},"increase":{"valueId":"38:targetValue","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) + ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}},"decrease":{"valueId":"38:targetValue","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) - ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}},"relative":{"valueId":"38:targetValue","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) + ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}}}},"toggle":{"actions":{"toggle":{"valueId":"38:targetValue:","value":{"expr":"entity.attributes.cover.state ? 99 : 50"}}}}}}],"manufacturerId":647,"productType":4,"productId":113}
x_zwave_values.Battery_isLow=false
x_zwave_values.Battery_level=100
x_zwave_values.Configuration_Close_Interval=15
x_zwave_values.Configuration_Default_ON_Value=50
x_zwave_values.Configuration_MC=1
x_zwave_values.Configuration_Maximum_Tilt_Level=99
x_zwave_values.Configuration_Minimum_Tilt_Level=0
x_zwave_values.Configuration_Movement_Duration=0
x_zwave_values.Configuration_Override_Response_to_ON_Command=null
x_zwave_values.Configuration_Remote_Calibration=1
x_zwave_values.Configuration_Reset_Button=0
x_zwave_values.Configuration_Reverse_Direction=1
x_zwave_values.Configuration_Send_Reports=0
x_zwave_values.Indicator_Node_Identify_3=0
x_zwave_values.Indicator_Node_Identify_4=0
x_zwave_values.Indicator_Node_Identify_5=0
x_zwave_values.Indicator_identify=true
x_zwave_values.Indicator_timeout=null
x_zwave_values.Indicator_value=null
x_zwave_values.Manufacturer_Specific_manufacturerId=647
x_zwave_values.Manufacturer_Specific_productId=114
x_zwave_values.Manufacturer_Specific_productType=4
x_zwave_values.Version_applicationBuildNumber=43707
x_zwave_values.Version_applicationFrameworkAPIVersion="3.12.1"
x_zwave_values.Version_applicationFrameworkBuildNumber=35
x_zwave_values.Version_applicationVersion="3.12.1"
x_zwave_values.Version_firmwareVersions=["3.12"]
x_zwave_values.Version_hardwareVersion=2
x_zwave_values.Version_hostInterfaceBuildNumber=0
x_zwave_values.Version_hostInterfaceVersion="unused"
x_zwave_values.Version_libraryType=3
x_zwave_values.Version_protocolVersion="7.12"
x_zwave_values.Version_sdkVersion="7.12.2"
x_zwave_values.Version_zWaveProtocolBuildNumber=35
x_zwave_values.Version_zWaveProtocolVersion="7.12.2"
x_zwave_values.Window_Covering_currentValue_23=0
x_zwave_values.Window_Covering_duration_23={"value":0,"unit":"seconds"}
x_zwave_values.Window_Covering_levelChangeDown_23=false
x_zwave_values.Window_Covering_levelChangeUp_23=true
x_zwave_values.Window_Covering_targetValue_23=0
zwave_device.capabilities=[106,112,114,128,134,135]
zwave_device.endpoint=0
zwave_device.failed=false
zwave_device.generic_class="Multilevel Switch"
zwave_device.impl_sig="23052:1:23093:1"
zwave_device.is_beaming=false
zwave_device.is_listening=false
zwave_device.is_routing=true
zwave_device.is_secure=false
zwave_device.manufacturer_info=[647,4,114]
zwave_device.max_data_rate=null
zwave_device.node_id=20
zwave_device.specific_class="Motor Control Class C"
zwave_device.status=4
zwave_device.status_text="alive"
zwave_device.version_info=[null,"3.12.1"]

        I may try removing the device completely and repairing if you think that might have benefit.

        *Hubitat C-7 2.4.1.151
        *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

        *HASS 2025.3.4
        w/ ZST10-700 fw 7.18.3

        *Prod MSR in docker/portainer
        MSR: latest-25082-3c348de6
        MQTTController: 24257
        ZWave Controller: 25082

        1 Reply Last reply
        0
        • T Offline
          T Offline
          toggledbits
          wrote on Sep 8, 2023, 2:51 PM last edited by
          #4

          Look at the file called 647.yaml in ext/ZWaveJSController/manufacturer and check the version. It should be 23093. And your ext/ZWaveJSController/zwave_devices.yaml file should be version 23194.

          If these numbers don't match up, update your ZWaveJSController.

          Download: https://reactor.toggledbits.com/download/extras/ZWaveJSController/

          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

          1 Reply Last reply
          0
          • T Offline
            T Offline
            toggledbits
            wrote on Sep 8, 2023, 3:28 PM last edited by
            #5

            Also, did you restart Reactor after adding the node?

            Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

            G 1 Reply Last reply Sep 8, 2023, 4:43 PM
            0
            • G Offline
              G Offline
              gwp1
              replied to toggledbits on Sep 8, 2023, 4:43 PM last edited by
              #6

              @toggledbits Answering in reverse order: yes on restart of MSR (multiple times). Also reloaded the HA ZWaveJS plugin as well as restarted HA as a whole.

              The the first ask:
              647.yaml

              manufacturer_id: 647
manufacturer_name: "HAB Home Intelligence, LLC"
version: 23093
revision: 1
format: 1

              and I do not have a ext/ZWaveJSController/zwave_devices.yaml but do have a ext/ZWaveJSController/zwavejs_devices.yaml and it shows

              version: 23052
revision: 1
format: 1

              Looking in my files I see the latest version was 23093 so I'm grabbing 23094 from your repo and installing now.

              *Hubitat C-7 2.4.1.151
              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

              *HASS 2025.3.4
              w/ ZST10-700 fw 7.18.3

              *Prod MSR in docker/portainer
              MSR: latest-25082-3c348de6
              MQTTController: 24257
              ZWave Controller: 25082

              G 1 Reply Last reply Sep 8, 2023, 4:55 PM
              0
              • T Offline
                T Offline
                toggledbits
                wrote on Sep 8, 2023, 4:53 PM last edited by
                #7

                Looks like your Hass devices aren't actually faring much better... nulls there too for some values, and that's a straight pass from Hass itself, not likely something MSR is doing (or not doing).

                Something off about this device. I'm going to PM you instructions to upload a data file from your system.

                Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                1 Reply Last reply
                0
                • G Offline
                  G Offline
                  gwp1
                  replied to gwp1 on Sep 8, 2023, 4:55 PM last edited by
                  #8

                  @toggledbits Ok, release deployed.

                  ext/ZWaveJSController/zwavejs_devices.yaml now shows

                  version: 23194
revision: 1
format: 1

                  647.yaml still shows

                  manufacturer_id: 647
manufacturer_name: "HAB Home Intelligence, LLC"
version: 23093
revision: 1
format: 1

                  Node attributes:

                  battery_power.since=1694192043559
cover.state=null
position.value=null
x_debug.dt={"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=7","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state","description":"Window Blind Controller","model":"iblinds V3","default_name":"Window Blind Controller","values":[{"valueId":"38:currentValue:","capabilities":{"cover":{"attributes":{"state":{"expr":"!(value == 0 || value >= 99)"}},"actions":{"open":{"valueId":"38:targetValue:","value":50},"close":{"valueId":"38:targetValue:","value":99},"stop":false}},"position":{"attributes":{"value":{"expr":"round( value / 99, 2 )"}},"actions":{"set":{"valueId":"38:targetValue","value":{"expr":"max( 0, min( 99, round( 100 * ( parameters.value ?# 0 ), 0 ) ) )"}},"increase":{"valueId":"38:targetValue","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) + ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}},"decrease":{"valueId":"38:targetValue","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) - ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}},"relative":{"valueId":"38:targetValue","value":{"expr":"max( 0, min( 99, round( 100 * ( ( entity.attributes.position?.value ?# 0 ) + ( parameters.amount ?# 0.10 ) ), 0 ) ) )"}}}},"toggle":{"actions":{"toggle":{"valueId":"38:targetValue:","value":{"expr":"entity.attributes.cover.state ? 99 : 50"}}}}}}],"manufacturerId":647,"productType":4,"productId":113}
x_zwave_values.Battery_isLow=false
x_zwave_values.Battery_level=100
x_zwave_values.Configuration_Close_Interval=15
x_zwave_values.Configuration_Default_ON_Value=50
x_zwave_values.Configuration_MC=1
x_zwave_values.Configuration_Maximum_Tilt_Level=99
x_zwave_values.Configuration_Minimum_Tilt_Level=0
x_zwave_values.Configuration_Movement_Duration=0
x_zwave_values.Configuration_Override_Response_to_ON_Command=null
x_zwave_values.Configuration_Remote_Calibration=1
x_zwave_values.Configuration_Reset_Button=0
x_zwave_values.Configuration_Reverse_Direction=1
x_zwave_values.Configuration_Send_Reports=0
x_zwave_values.Indicator_Node_Identify_3=0
x_zwave_values.Indicator_Node_Identify_4=0
x_zwave_values.Indicator_Node_Identify_5=0
x_zwave_values.Indicator_identify=true
x_zwave_values.Indicator_timeout=null
x_zwave_values.Indicator_value=null
x_zwave_values.Manufacturer_Specific_manufacturerId=647
x_zwave_values.Manufacturer_Specific_productId=114
x_zwave_values.Manufacturer_Specific_productType=4
x_zwave_values.Version_applicationBuildNumber=43707
x_zwave_values.Version_applicationFrameworkAPIVersion="3.12.1"
x_zwave_values.Version_applicationFrameworkBuildNumber=35
x_zwave_values.Version_applicationVersion="3.12.1"
x_zwave_values.Version_firmwareVersions=["3.12"]
x_zwave_values.Version_hardwareVersion=2
x_zwave_values.Version_hostInterfaceBuildNumber=0
x_zwave_values.Version_hostInterfaceVersion="unused"
x_zwave_values.Version_libraryType=3
x_zwave_values.Version_protocolVersion="7.12"
x_zwave_values.Version_sdkVersion="7.12.2"
x_zwave_values.Version_zWaveProtocolBuildNumber=35
x_zwave_values.Version_zWaveProtocolVersion="7.12.2"
x_zwave_values.Window_Covering_currentValue_23=0
x_zwave_values.Window_Covering_duration_23={"value":0,"unit":"seconds"}
x_zwave_values.Window_Covering_levelChangeDown_23=false
x_zwave_values.Window_Covering_levelChangeUp_23=true
x_zwave_values.Window_Covering_targetValue_23=0
zwave_device.capabilities=[106,112,114,128,134,135]
zwave_device.endpoint=0
zwave_device.failed=false
zwave_device.generic_class="Multilevel Switch"
zwave_device.impl_sig="23194:1:23093:1"
zwave_device.is_beaming=false
zwave_device.is_listening=false
zwave_device.is_routing=true
zwave_device.is_secure=false
zwave_device.manufacturer_info=[647,4,114]
zwave_device.max_data_rate=null
zwave_device.node_id=20
zwave_device.specific_class="Motor Control Class C"
zwave_device.status=4
zwave_device.status_text="alive"
zwave_device.version_info=[null,"3.12.1"]

                  (Did a manual restart via Tools>Restart after the deploy as well.

                  *Hubitat C-7 2.4.1.151
                  *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                  *HASS 2025.3.4
                  w/ ZST10-700 fw 7.18.3

                  *Prod MSR in docker/portainer
                  MSR: latest-25082-3c348de6
                  MQTTController: 24257
                  ZWave Controller: 25082

                  1 Reply Last reply
                  0
                  • T Offline
                    T Offline
                    toggledbits
                    wrote on Sep 8, 2023, 5:00 PM last edited by toggledbits Sep 8, 2023, 1:02 PM
                    #9

                    Yeah, this device is off. It's reporting Multilevel Switch for its generic class, and Motor Control Class C as the more specific, and usually this device class reports command class 38, Multilevel Switch. That's how your other iBlinds units that identify the same way (same 647 manufacturer ID, product type 4, product ID 114) work. But this particular unit does not appear to be advertising command class 38 Multilevel Switch, and is instead reporting command class 106 Window Covering, which is relatively new.

                    Once you upload the data I PM'd you about, I'll be curious to see how the reporting firmware compares. But this new unit is definitely working differently from everything else you have, and it doesn't look like HA actually likes it any better -- I think that's why it's reporting the slats angle in HA as null; I bet it shows the same in their dashboard.

                    I'll know more/confirm once I see you data. Probably won't get to that until Sunday or Monday at this point, though.

                    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                    G 1 Reply Last reply Sep 8, 2023, 5:46 PM
                    0
                    • G Offline
                      G Offline
                      gwp1
                      replied to toggledbits on Sep 8, 2023, 5:46 PM last edited by
                      #10

                      @toggledbits file has been uploaded. This blind is in a guest room that's not in use currently - no rush.

                      Do you think excluding/including with HA/ZWjs would have any effect? Could something have gone sideways during pairing that a complete redo might clear?

                      *Hubitat C-7 2.4.1.151
                      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                      *HASS 2025.3.4
                      w/ ZST10-700 fw 7.18.3

                      *Prod MSR in docker/portainer
                      MSR: latest-25082-3c348de6
                      MQTTController: 24257
                      ZWave Controller: 25082

                      1 Reply Last reply
                      0
                      • T Offline
                        T Offline
                        toggledbits
                        wrote on Sep 11, 2023, 5:36 PM last edited by
                        #11

                        ZWaveJSController version 23254 has been released. It should handle your oddball iBlinds unit. I'd love to know (not from you, from the manufacturer) what triggers the difference between reporting status in command class 38 versus command class 106 -- only this most recent unit of yours reports/controls via 106; all of the others use 38. And there's no difference in reported model or firmware version. No obvious configuration parameter that might trigger such a difference (e.g. some others, like some Aeotec devices, can change the reporting CC based on a config parameter). Just goes to show you that despite a fairly strict standard and specification, manufacturers can continue to make subtle choices that create headaches.

                        Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                        G 2 Replies Last reply Sep 11, 2023, 5:48 PM
                        0
                        • G Offline
                          G Offline
                          gwp1
                          replied to toggledbits on Sep 11, 2023, 5:48 PM last edited by
                          #12

                          @toggledbits this was deployed and tests as working. Really appreciate it - I bought two new units and have held off installing the second until it was determined not to be a firmware problem (broken vs them just randomly changing something).

                          Thank you!

                          *Hubitat C-7 2.4.1.151
                          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                          *HASS 2025.3.4
                          w/ ZST10-700 fw 7.18.3

                          *Prod MSR in docker/portainer
                          MSR: latest-25082-3c348de6
                          MQTTController: 24257
                          ZWave Controller: 25082

                          1 Reply Last reply
                          0
                          • G Offline
                            G Offline
                            gwp1
                            replied to toggledbits on Sep 14, 2023, 2:17 AM last edited by gwp1 Sep 13, 2023, 10:29 PM
                            #13

                            @toggledbits I contacted iblinds Support. This was their response:

                            *We've had similar reports. I believe it is related to a recent update with Home Assistant supporting the Z-Wave Window Covering Command Class now. So when you add your new devices they are seen with the new command class. I would imagine if you excluded and included one of the older motors they would now be Window Covering devices as opposed to multi-level switches.

                            We initially worked with the ZWaveJS developer when they added the Window Covering CC Support. But unfortunately, our HA in our lab is no longer working so we have been unable to test locally.

                            We have been waiting to get a replacement RPi so hopefully we can do some testing on our end soon.

                            I hope this helps.

                            Best Regards,
                            Eric B.
                            The iblinds Team*

                            Further, I just discovered if I do a reinterview on an existing blind via ZWaveJS in HA it switches to this new Window Covering mode.

                            *Hubitat C-7 2.4.1.151
                            *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                            *HASS 2025.3.4
                            w/ ZST10-700 fw 7.18.3

                            *Prod MSR in docker/portainer
                            MSR: latest-25082-3c348de6
                            MQTTController: 24257
                            ZWave Controller: 25082

                            T 1 Reply Last reply Sep 14, 2023, 2:35 AM
                            0
                            • T Offline
                              T Offline
                              tamorgen
                              replied to gwp1 on Sep 14, 2023, 2:35 AM last edited by
                              #14

                              @gwp1 said in [SOLVED] New iblind and zwaveJScontroller/MSR not communicating:

                              Further, I just discovered if I do a reinterview on an existing blind via ZWaveJS in HA it switches to this new Window Covering mode.

                              For what it's worth, I have both v2 and v3.1 iBlinds in my home. Reinterviewing only changes the type from multilevel switches to window covering on v3.1 blinds. Version 2 blinds remain multilevel switches after reinterviewing.

                              The Window Covering class is supposedly better. The MLS class is designed for rolling blinds, so on/off will have the bllinds all the way open, or all the way off. With horizonal blinds, the 0/100 values are just 180 degree opposites of a closed blind. With Window Covering class, I believe there are values to tell the Z-Wave system what type of blind it is, and specify what is open versus closed. I dealt with iBlinds support maybe 4 or 5 months ago, and at the time, no Z-Wave system supported Window Covering. Zwave JS implemented the change shortly thereafter.

                              G 2 Replies Last reply Sep 14, 2023, 2:41 AM
                              1
                              • G Offline
                                G Offline
                                gwp1
                                replied to tamorgen on Sep 14, 2023, 2:41 AM last edited by
                                #15

                                @tamorgen I'm poking at it now. It seems for the iblinds I can now use cover.close and the [0] NO (default) setting for direction vs having it set to [1] YES to make it tilt the way I want it to when closed.

                                I was using power_switch.off previously to close my v3.1's.

                                *Hubitat C-7 2.4.1.151
                                *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                *HASS 2025.3.4
                                w/ ZST10-700 fw 7.18.3

                                *Prod MSR in docker/portainer
                                MSR: latest-25082-3c348de6
                                MQTTController: 24257
                                ZWave Controller: 25082

                                1 Reply Last reply
                                0
                                • G Offline
                                  G Offline
                                  gwp1
                                  replied to tamorgen on Sep 14, 2023, 11:45 AM last edited by
                                  #16

                                  UPDATE: after many lost hours last night/this morning (hello, 0230 ET, looking at you) I found cover.x and power_switch.x to be woefully unreliable after reinterviewing the blinds.

                                  What has proven reliable is position.set for which I use 0 for closed, 50 for open and have the blinds (as they were previously) set to [1] YES for Reverse Direction.

                                  *Hubitat C-7 2.4.1.151
                                  *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                  *HASS 2025.3.4
                                  w/ ZST10-700 fw 7.18.3

                                  *Prod MSR in docker/portainer
                                  MSR: latest-25082-3c348de6
                                  MQTTController: 24257
                                  ZWave Controller: 25082

                                  T 1 Reply Last reply Sep 14, 2023, 6:59 PM
                                  0
                                  • T Offline
                                    T Offline
                                    tamorgen
                                    wrote on Sep 14, 2023, 1:36 PM last edited by
                                    #17

                                    I've been using the ID hass>cover_blind_horizontal_slats_angle and x_hass_cover.open_cover_tilt or x_haas_cover.close_cover_tilt and it works flawlessly for open and close. If I want to set the position for partial close when the sun is glarring into the room, I use x_hass_cover.set_cover_tilt_position with the same ID, and set the tilt_position to whatever I want to reduce the glare.

                                    My only problem now is that I use mushroom for my dashboard in Home Assistant, and the templates for covers hasn't caught up with the new Window Covering class. It makes adjusting the blinds more problematic from HA.

                                    1 Reply Last reply
                                    0
                                    • T Offline
                                      T Offline
                                      toggledbits
                                      replied to gwp1 on Sep 14, 2023, 6:59 PM last edited by
                                      #18

                                      @gwp1 said in [SOLVED] New iblind and zwaveJScontroller/MSR not communicating:

                                      UPDATE: after many lost hours last night/this morning (hello, 0230 ET, looking at you) I found cover.x and power_switch.x to be woefully unreliable after reinterviewing the blinds.

                                      Can you please be more descriptive here? I don't have these devices, so I can't test them, but that doesn't mean I'm not interested in getting them working reliably. But the description given isn't enough for me to do any troubleshooting at all.

                                      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                                      G 1 Reply Last reply Sep 14, 2023, 9:39 PM
                                      0
                                      • G Offline
                                        G Offline
                                        gwp1
                                        replied to toggledbits on Sep 14, 2023, 9:39 PM last edited by gwp1 Sep 14, 2023, 5:44 PM
                                        #19

                                        @toggledbits of course, no problem! I cannot seem to upload images into this response. I've uploaded to your Dropbox shared folder a pair of images.

                                        Using the iblind I sent you logs and such for previously as the example, I have a blind called Beach Blind (two guest rooms, one is named Ocean, the other Beach). I use the commands from the ID Beach Blind from zwavejs. As @tamorgen notes, there is also a new one (with the changes HA made) from my HASS controller called Beach Blind Horizontal Slates Angle which has a few less commands including those mentioned starting with x_hass_*.

                                        I use the ZwaveJSController commands.

                                        cover.open
                                        cover.close
                                        power_switch.on
                                        power_switch.off
                                        position.set
                                        zwave_device.refresh
                                        zwave_device.set_config

                                        These are the ones I most commonly use to open, close, and tilt the blinds. refresh is used to force HA to update dasheboards with any changes and set_config I use less often, weekly, to recalibrate the blinds as they do wander sometimes and "open" becomes "open-ish".

                                        I'd been using power_switch.on to open and cover.close to close. The blinds have been happiest that way. With these new changes from HA, these commands have become hit/miss. In the HA ZWaveJS plugin the status would reflect 0/closed but the blind was clearly wide open.

                                        Last night/this morning I opted to use position.set and it's been pretty solid from what I've seen throughout the day.
                                        position.set = 0 nets me a closed blind, position.set = .5 nets me a wide open/"slates level with the ground" blind. I used position.set = .2 or .3 to tilt the sun away during specific dayparts based on sun azimuth.

                                        I did not grab MSR logs during those tests - apologies, it was 0200 ET and I just wanted the blinds closed for the night. I have amassed 13 of these iblinds over the past couple years.

                                        If you wish, I'll set some time tonight or tomorrow night and generate some MSR logs.

                                        *Hubitat C-7 2.4.1.151
                                        *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                        *HASS 2025.3.4
                                        w/ ZST10-700 fw 7.18.3

                                        *Prod MSR in docker/portainer
                                        MSR: latest-25082-3c348de6
                                        MQTTController: 24257
                                        ZWave Controller: 25082

                                        T 1 Reply Last reply Sep 14, 2023, 10:06 PM
                                        0
                                        • T Offline
                                          T Offline
                                          tamorgen
                                          replied to gwp1 on Sep 14, 2023, 10:06 PM last edited by
                                          #20

                                          @gwp1 said in [SOLVED] New iblind and zwaveJScontroller/MSR not communicating:

                                          With these new changes from HA, these commands have become hit/miss.

                                          To be precise, it's not so much a change from HA, but from ZWaveJS. They're recognizing a new command class that the developers at iBlinds actually recommend.

                                          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.

                                          46ce7b67-822d-4800-ad9e-84e420f830a6-image.png

                                          if you go into the switch, it shows it as unavailable.

                                          b487cb9f-a396-460f-8190-1753e356ff73-image.png

                                          I would guess the power on/off cover.close / cover.open are remnants and probably need to be removed.

                                          G 1 Reply Last reply Sep 14, 2023, 11:55 PM
                                          0

                                          1/44

                                          Sep 8, 2023, 5:48 AM

                                          Recent Topics

                                          • Moving MSR from a QNAP container to RP 5 - some issues
                                            T
                                            Tom_D
                                            about 5 hours ago
                                            0
                                            4
                                            80
                                          • Need help reducing false positive notifications
                                            T
                                            tamorgen
                                            about 10 hours ago
                                            0
                                            7
                                            164
                                          • Widget deletion does not work and landing page (status) is empy
                                            M
                                            mgvra
                                            about 13 hours ago
                                            0
                                            3
                                            61
                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            T
                                            toggledbits
                                            a day ago
                                            5
                                            120
                                            17.2k
                                          • Deleting widgets
                                            T
                                            toggledbits
                                            a day ago
                                            0
                                            4
                                            256
                                          • MQTT configuration question
                                            T
                                            tunnus
                                            6 days ago
                                            0
                                            11
                                            249
                                          • System Configuration Check - time is offset
                                            G
                                            gwp1
                                            6 days ago
                                            0
                                            8
                                            224
                                          • Programmatically capture HTTP Request action status code or error
                                            therealdbT
                                            therealdb
                                            8 days ago
                                            0
                                            3
                                            175
                                          • ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
                                            T
                                            toggledbits
                                            9 days ago
                                            0
                                            9
                                            292
                                          • Problem with simultaneous notifications.
                                            T
                                            tamorgen
                                            9 days ago
                                            0
                                            1
                                            73
                                          • Problem after upgrading to 25067
                                            R
                                            retireditguy
                                            14 days ago
                                            0
                                            4
                                            178
                                          Powered by NodeBB | Contributors
                                          Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                                          • Login
                                          • Don't have an account? Register
                                          • Login or register to search.
                                          1 out of 44
                                          • First post
                                            1/44
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Unsolved