Good morning,
I'm trying to figure out if there is a way to evaluate if a command was completed and retry if it did not complete.
I have 14 iBlinds 3.1 z-wave controllers in my home. 95% of the time, they work just fine. Occasionally, I'll get a blind that does not open on the first attempt. When I go into Home Assistant, and manually open or close the blind, it works.
I have 3 reactions set up for each room. One to open, one to close, and one partial open for sun glare. Each of them is set up as below.
5afc9924-4300-4718-9e23-8855c4a3a9fd-image.png
The reactions are set up to wait for 5 seconds before going onto the next blind, so the z-wave network doesn't get overwhelmed.
In addition, the set command to run the reactions has "Wait for completion" checked.
3919fc06-c1f1-4c49-bf95-716028d18a27-image.png
I also have a routine set up whenever a z-wave device reports as non-functional (dead), it'll get pinged to wake it up. This usually works to wake them up.
16df4bff-c733-4ec2-a55c-c964238ada3b-image.png
Appreciate any ideas to make this more reliable.
I'm running:
Reactor latest-24190-bd310acc, Bare-metal on Fedora WaveJSController [0.1.23326] Home Assistant: 2024.7.0I think this feature request could be accomplished with the use of two or more rules, but it would be great if there was a way to wait for an event or trigger to occur before continuing on in the reactions.
For example, I have a rule that will turn on some exterior lights if you arrive home after the porch lights have been turned off. Right now this rule randomly will turn off between 5-10 minutes after the person has entered the geofence. On some occasions this 5-10 minutes isn't long enough, say if you are unloading the car or something. I would like to kick off the reaction, but pause it part way through and wait for the door to close and lock, then continue it on. Hubitat Rule Machine has a "Wait for event" option, but I really want to keep all my logic within MSR.
Good morning,
I'm going through my ruleset this morning, trying to get away from haas>blahblablah entries and completely migrate them all to zwavejs>xx-0 entries where possible.
I have 3 Aeon MultiSensor 6 devices in my home, all USB powered.
When using Haas entries, I see an entry for hass>binary_sensor_guest_bedroom_multisensor_home_security_motion_detection, and motion_sensor.state (primary)
Screenshot 2024-07-25 at 8.25.53 AM.png
Under ZwaveJS, this entry appears to be missing.
Screenshot 2024-07-25 at 8.26.51 AM.png
From the Entities page:
battery_power.level=1
battery_power.since=1721910337433
binary_sensor.state=false
humidity_sensor.units="%"
humidity_sensor.value=46
light_sensor.units="Lux"
light_sensor.value=5
tamper.state=false
temperature_sensor.units="°F"
temperature_sensor.value=73.8
x_debug.dt={}
x_zwave_values.Basic_currentValue=0
x_zwave_values.Battery_isLow=false
x_zwave_values.Battery_level=100
x_zwave_values.Binary_Sensor_Any=false
x_zwave_values.Configuration_Automatic_Report_Group_1_Battery_1=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Humidity_64=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Luminance_128=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Temperature_32=1
x_zwave_values.Configuration_Automatic_Report_Group_1_Ultraviolet_16=1
x_zwave_values.Configuration_Automatic_Report_Group_2_Battery_1=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Humidity_64=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Luminance_128=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Temperature_32=0
x_zwave_values.Configuration_Automatic_Report_Group_2_Ultraviolet_16=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Battery_1=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Humidity_64=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Luminance_128=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Temperature_32=0
x_zwave_values.Configuration_Automatic_Report_Group_3_Ultraviolet_16=0
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_1=3600
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_2=3600
x_zwave_values.Configuration_Automatic_Reporting_Interval_Group_3=3600
x_zwave_values.Configuration_Automatic_Temperature_Reporting_Unit=2
x_zwave_values.Configuration_Battery_Level_Threshold=10
x_zwave_values.Configuration_Current_Power_Mode_65280=0
x_zwave_values.Configuration_Humidity_Above_Lower_Limit_32=0
x_zwave_values.Configuration_Humidity_Below_Lower_Limit_2=0
x_zwave_values.Configuration_Humidity_Change_Threshold=10
x_zwave_values.Configuration_Humidity_Recover_Limit=5
x_zwave_values.Configuration_Humidity_Sensor_Calibration=0
x_zwave_values.Configuration_LED_Blinking=0
x_zwave_values.Configuration_Lighting_Recover_Limit=10
x_zwave_values.Configuration_Lock_Configuration=0
x_zwave_values.Configuration_Low_Battery_Threshold=20
x_zwave_values.Configuration_Low_Temperature_Alarm_15_C=0
x_zwave_values.Configuration_Lower_Humidity_Limit=50
x_zwave_values.Configuration_Lower_Lighting_Limit=100
x_zwave_values.Configuration_Lower_Temperature_Limit_4294901760=320
x_zwave_values.Configuration_Lower_Temperature_Limit_Unit_3840=2
x_zwave_values.Configuration_Lower_Ultraviolet_Limit=4
x_zwave_values.Configuration_Luminance_Above_Lower_Limit_64=0
x_zwave_values.Configuration_Luminance_Below_Lower_Limit_4=0
x_zwave_values.Configuration_Luminance_Change_Threshold=100
x_zwave_values.Configuration_Luminance_Sensor_Calibration=0
x_zwave_values.Configuration_Motion_Sensor_Report_Type_to_Send=2
x_zwave_values.Configuration_PIR_Sensitivity=3
x_zwave_values.Configuration_PIR_Sensor_Timeout=20
x_zwave_values.Configuration_Recover_Limit_Temperature_Unit_255=2
x_zwave_values.Configuration_Report_Above_Humidity_Threshold_32=0
x_zwave_values.Configuration_Report_Above_Luminance_Threshold_64=0
x_zwave_values.Configuration_Report_Above_Temperature_Threshold_16=0
x_zwave_values.Configuration_Report_Above_Ultraviolet_Threshold_128=0
x_zwave_values.Configuration_Report_Below_Humidity_Threshold_2=0
x_zwave_values.Configuration_Report_Below_Luminance_Threshold_4=0
x_zwave_values.Configuration_Report_Below_Temperature_Threshold_1=0
x_zwave_values.Configuration_Report_Below_Ultraviolet_Threshold_8=0
x_zwave_values.Configuration_Reset_Parameters_101_103_to_Default_Values=null
x_zwave_values.Configuration_Reset_Parameters_111_113_to_Default_Values=null
x_zwave_values.Configuration_Reset_to_Factory_Default_Setting=null
x_zwave_values.Configuration_Selective_Reporting=0
x_zwave_values.Configuration_Sleep_State_255=2
x_zwave_values.Configuration_Temperature_Above_Lower_Limit_16=0
x_zwave_values.Configuration_Temperature_Below_Lower_Limit_1=0
x_zwave_values.Configuration_Temperature_Calibration_Offset_65280=0
x_zwave_values.Configuration_Temperature_Calibration_Unit_255=2
x_zwave_values.Configuration_Temperature_Change_Threshold_4294901760=20
x_zwave_values.Configuration_Temperature_Recover_Limit_65280=20
x_zwave_values.Configuration_Temperature_Threshold_Unit_3840=2
x_zwave_values.Configuration_Ultraviolet_Above_Lower_Limit_128=0
x_zwave_values.Configuration_Ultraviolet_Below_Lower_Limit_8=0
x_zwave_values.Configuration_Ultraviolet_Change_Threshold=2
x_zwave_values.Configuration_Ultraviolet_Recover_Limit=2
x_zwave_values.Configuration_Ultraviolet_Sensor_Calibration=0
x_zwave_values.Configuration_Upper_Humidity_Limit=60
x_zwave_values.Configuration_Upper_Lighting_Limit=1000
x_zwave_values.Configuration_Upper_Temperature_Limit_4294901760=824
x_zwave_values.Configuration_Upper_Temperature_Limit_Unit_3840=2
x_zwave_values.Configuration_Upper_Ultraviolet_Limit=8
x_zwave_values.Configuration_Wake_Device_for_10_minutes_After_Power_On=1
x_zwave_values.Configuration_Wake_Up_Timeout=15
x_zwave_values.Manufacturer_Specific_manufacturerId=134
x_zwave_values.Manufacturer_Specific_productId=100
x_zwave_values.Manufacturer_Specific_productType=258
x_zwave_values.Multilevel_Sensor_Air_temperature=73.8
x_zwave_values.Multilevel_Sensor_Humidity=46
x_zwave_values.Multilevel_Sensor_Illuminance=5
x_zwave_values.Multilevel_Sensor_Ultraviolet=0
x_zwave_values.Notification_Home_Security_Cover_status=0
x_zwave_values.Notification_Home_Security_Motion_sensor_status=0
x_zwave_values.Notification_alarmLevel=0
x_zwave_values.Notification_alarmType=0
x_zwave_values.Version_firmwareVersions=["1.17"]
x_zwave_values.Version_hardwareVersion=100
x_zwave_values.Version_libraryType=3
x_zwave_values.Version_protocolVersion="4.54"
x_zwave_values.Wake_Up_controllerNodeId=1
x_zwave_values.Wake_Up_wakeUpInterval=3600
zwave_device.capabilities=[32,48,49,112,113,114,128,132,134]
zwave_device.endpoint=0
zwave_device.failed=false
zwave_device.generic_class="Multilevel Sensor"
zwave_device.impl_sig="23326:1:22315:1"
zwave_device.is_beaming=false
zwave_device.is_listening=true
zwave_device.is_routing=true
zwave_device.is_secure=false
zwave_device.manufacturer_info=[134,258,100]
zwave_device.max_data_rate=null
zwave_device.node_id=53
zwave_device.specific_class="Routing Multilevel Sensor"
zwave_device.status=4
zwave_device.status_text="alive"
zwave_device.version_info=[null,"1.17"]
zwave_device.wakeup_interval=3600
I'm running:
Reactor latest-24190-bd310acc, Bare-metal on Fedora
WaveJSController [0.1.23326]
Home Assistant: 2024.7.0
I'm fetching certain data five past every hour, but I would like to do it closer to the hour, e.g. 1 or 2 past (but not at the hour).
I experimented with the following rule that almost works (triggers also at the hour which is not the intention). Any advice for a solution?
It would be nice to have an ability to bookmark a direct link to a dashboard item. In my case I would use this feature to access a virtual switch directly.
Hi @toggledbits
Would you please consider adding an extra sublevel in the rulesets?
I have grouped my rules in rooms/ areas. This works great for me, but I would also like to group rules for the same functionality (in a room). This would make the rules easier to find and name.
Please let me know if this is an option. Thanks!
@togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.
Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.
Thanks in advance.
Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3
@toggledbits,
I have this device attached to my system, but use a DSC panel. If you need testers to move forward, I'm happy to help.
I'm curious what your thinking the use case is for this. I currently have it integrated into HomeAssistant, and it works fine for the most part. The one thing I can't do is bypass zones, which I would like to have the ability to do.
Are you looking at more direct control for the panel, as opposed to having to jump through HA (or another system) first?
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 ruleset which I though had been working well until this morning when I noticed it's not.
I've put four weather conditions in an in array and one of them is the current weather condition - but the rule is not true. Now the cloud cover percentage is not yet met but this is an or rule so as long as the "Current Conditions" are met then it should go true.
What's the obvious thing I'm missing here? (I've tried spaces/no spaces in the in and no difference.)
Hi,
Running the latest MSR latest-24152-3455578a with the latest HA 2024.6.1. When trying to call a service I get the following in the MSR logs. Is this a version mismatch? I am not seeing anything in the HA logs.
[latest-24152]2024-06-11T10:29:56.162Z <Rule:INFO> rule-Monitor-DHW (rule-lsvq5k3x in Central Heating) started [latest-24152]2024-06-11T10:29:58.625Z <HassController:WARN> HassController#hass unknown service opentherm_gw.set_hot_water_setpoint in x_hass.call_service action on Thermostat#hass>climate_living_room_otgw [latest-24152]2024-06-11T10:29:58.626Z <HassController:INFO> HassController#hass: sending payload for x_hass.call_service on Thermostat#hass>climate_living_room_otgw action: [Object]{ "type": "call_service", "service_data": { "gateway_id": "living_room_otgw", "temperature": 65 }, "domain": "opentherm_gw", "service": "set_hot_water_setpoint", "target": { "entity_id": "climate.living_room_otgw" } } [latest-24152]2024-06-11T10:29:58.627Z <HassController:ERR> HassController#hass request 1718101798626<6/11/2024, 12:29:58 PM> (call_service) failed: [Object]{ "id": 1718101798626, "type": "result", "success": false, "error": { "code": "invalid_format", "message": "extra keys not allowed @ data['entity_id']" } } [latest-24152]2024-06-11T10:29:58.627Z <HassController:WARN> HassController#hass action x_hass.call_service([Object]{ "service": "opentherm_gw.set_hot_water_setpoint", "data": "{ \"gateway_id\": \"living_room_otgw\", \"temperature\": 65 }" }) on Thermostat#hass>climate_living_room_otgw failed!Cheers Rene
Some background
I'm trying to integrate a Zigbee device into the MSR using zigbee2mqtt bridge and MQTTController. The device in question is a cheap mood light that has following properties that I'd like to control:
I'v already managed to get the switch part working and can toggle the light on/off. Also the brightness value is mapped back to MSR. In zigbee2mqtt it has a value range from 0 to 254, so this the reason for the expression:
expr: 'payload.brightness / 254'Here's the entity definition (don't know whether the type should be something else than the Switch)
zigbee-lidl-mood-light: name: 'Lidl Mood Light' friendly_name: 'Mood Light' type: Switch uses_template: lidl-moodlightAnd the corresponding template (NOTE: rgb_color has not been defined in this example):
lidl-moodlight: init: "zigbee2mqtt/%friendly_name%/get/state" query: "zigbee2mqtt/%friendly_name%/get/state" capabilities: - power_switch - toggle - dimming primary_attribute: power_switch.state events: "zigbee2mqtt/%friendly_name%": "power_switch.state": json_payload: true expr: 'upper(payload.state) == "ON"' "dimming.level": json_payload: true expr: 'payload.brightness / 254' actions: power_switch: "on": topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'ON' "off": topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'OFF' set: topic: "zigbee2mqtt/%friendly_name%/set/state" payload: expr: "parameters.state ? 'ON' : 'OFF'" type: raw toggle: topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'TOGGLE'The problem
In order to control the brightness or the RGB color values, I would have send a JSON payload in corresponding actions. But I have no idea how to define it in the template. The reason why the switch part is working is that the zigbee2mqtt accepts also plain ON / OFF / TOGGLE string payloads in that case.
But the brightness should be controlled with the following payload:
{"brightness": 196}And the RGB color like:
{"color":{"rgb":"46,102,150"}}Here's the link for the documentation (the Exposes part defines the messages).
So how should I define the JSON payload for example for the dimming action? It definitely should be some sort of expressions since I have to map the MSR real value (0...1) to (0...254) for the zigbee2mqtt.
actions: dimming: set: topic: "zigbee2mqtt/%friendly_name%/set" payload: expr: ????? type: jsonAnother problem is the RGB value. I could use the rgb_color capability for the setting but the problem is that the zigbee2mqtt only reports the current color in hue/saturation or xy coordinates.
Here's an example of published message after setting the color:
Topic: zigbee2mqtt/Mood Light QoS: 0 { "brightness":254, "color":{ "hue":240, "saturation":100, "x":0.1355, "y":0.0399 }, "color_mode":"xy", "color_temp":574, "linkquality":96, "state":"ON" }I would have to map those values back to RGB, but is it even possible with existing constructs in MQTTController's templates?
Help would be appreciated @toggledbits
br,
mgvra
That's probably more appropriate to post on Mantis for @toggledbits, but since I know there's at least @Crille publishing templates, my intent with this post is to open a broader discussion.
Long story short: I'm starting to slowly add new template for Shelly Plus and I noticed I'll end up with a dozen more templates, all similar but simply different in trivial details, all sharing a large amount of code and all needing special cares when fixing bugs/adding features (as the latest wifi_status addition).
So, I'm wondering if it's time to start thinking of some sort of inheritance in templates, where I could just create a generic shelly_gen1 and use it as a base for shelly_relay, and this be used as the base for shelly_relay_power and so on.
I could probably achieve this with some sort of scripting on my side to generate templates via code, but maybe there's a better way of doing this, or it's already on the radar.
I need a handful of victims volunteers to help test previews of the next build of Reactor. A long-standing request was for "a simple login mechanism," but in practice, adding user authentication and competent access control turned out to be a pretty big project with a lot of big changes on both server and client sides. It's a bit more than I'm comfortable testing myself and springing out to everyone at once, so I'd like to work with a small group to put it through "sea trials."
Major changes/features include:
User authentication with hashed password storage; User group configuration with application restriction (admin, dashboard, API); Detailed control over API access, with user- and token-based authentication/authorization; Improvements to the HTTPS service; Improvements to UI coordination with the core for Rules and Reactions.If this sounds like something you'd like to help with, drop me a reply here in this thread or privately.
[Solution: Reactor 24115 is not compatible with MQTTController > 24120]
Reactor latest-24115 bare metal.
All MQTT entities stop working after updating MQTTController to 24142, downgrade to 24120 and they are back. Templates and configured entities has not been changed between versions.
I'm not sure if uses_template should be replaced by ìnclude in entity configuration in reactor.yaml but I guess not, I've tried it and it did not do any difference.
I have not tried to update Reactor to userauth version.
Example entity in reactor.yaml that uses MQTTController included template:
entities: "takflakt_kallare": name: "Takfläkt källare" topic: "Källartemp" unit: "" uses_template: tasmota_generic_relay init: "cmnd/%topic%/POWER%unit%"Any hints? Do you need more info, please let me know.
Log from startup:
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests 🙂
Is the following config correct?
- id: time_series name: "Out temp" capabilities: temperature_sensor: attributes: value: model: time series entity: "hass>sensor_outdoor_temperature" attribute: "temperature_sensor.value" interval: 5 # minutes retention: 20 # minutes aggregate: wma primary_attribute: temperature_sensor.value type: ValueSensorSpecifically, is "depth" directive needed/mandatory here? Reason I'm asking is that I'm not getting a "final" value in MSR, only debug values are shown:
temperature_sensor.units=null temperature_sensor.value=null x_virtualentity.last_request_time=null x_virtualentity.request_failures=null x_virtualentity.template=null x_virtualentity.timeseries_debug=[{"time":1716537360000,"value":22.1},{"time":1716537660000,"value":22},{"time":1716537960000,"value":22},{"time":1716538260000,"value":21.9},{"time":1716538560000,"value":22}]Good morning,
I apologize if this subject has been covered. I did try the search, but I'm not coming up with any topics on my issue.
I'm running userauth-24137-57b41335, bare metal installation on Fedora 39 Server.
I have a rule set up to turn the Eco mode off on my Nest Thermostat when the thermostat is set to Away (Rule State: Away Mode), the user (Driver) presence in my car changes to true, and the destination is set to home.
93804f7c-62d6-42c0-ae04-ff602011a6fd-image.png
This works fine for most days, where I'm headed home from work (commute is about 45 minutes). What I don't want it to do is set change it to Eco mode if my ETA is more than an hour.
There is a sensor/entity for Time to Arrival when the Destination is set. What it appears to provide is the Time OF arrival/ETA, not time until arrival. If it was Time until Arrival, and it was a numeric value, I could simply test if the value is less than 60 and be done with it.
I pulled up the history through Home Assistant for my morning commute and this appears to be what it is providing.
c2a32739-c84f-4a05-95d9-73793ed818f5-image.png
So what I need to do is to do a calculation of the the ETA from the sensor value and subtract the current time, and get a value in minutes that I can determine if it's less than 60.
I believe I can do this with the local expression, but I don't see anything for the system time, or local time. Also, do the local expressions update themselves if the sensors do?
Good morning,
I'm running userauth-24137-57b41335 on Fedora 39, bare metal installation.
ZWaveJSController 0.1.23254
Home Assistant:
Core, 2024.5.3 Supervisor, 2024.05.1 Operating System, 12.3 Frontend, 20240501.1I'm trying to troubleshoot a Dynamic Group Controller and notification alert that I've set up for low battery level.
In my Reactor.config, I have the following lines:
name: "Dynamic Group Controller" implementation: DynamicGroupController config: groups: "zwavejs_dead": select: - include_group: "zwavejs" filter_expression: "entity?.attributes?.zwave_device?.status == 3" group_actions: true "low_battery": select: - include_capability: battery_power filter_expression: > entity.attributes.battery_power.level < 0.35The idea here is that I should only have members of this group that have a battery level below 35%. When I go into Entities, I show a whole slew of devices, none of which have a battery level below the threshold.
a77e445b-ab78-4752-a624-3c4117f34f90-image.png
I also tried setting up a rule to generate a push notification once a day, but with all of the group members, I've had to disable the rule. I believe I have it set up correctly, but I'm not 100% sure. I want the notification to tell me the battery level for that device as well.
289b4f68-03ba-49c0-8275-f0f197d13a3a-image.png
ce24a76e-6865-40bd-bd85-632e54d315a8-image.png dc837424-deb5-4ef7-8f0d-3676f1769535-image.png
Can anyone point to me what I may have misconfigured to get these results?
I should also note I'm only interested in ZWaveJS devices. It's showing me battery status for my iPad and car as well, which I don't need it to send me.
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
-
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.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.
-
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.
-
@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.
-
Look at the file called
647.yaml
inext/ZWaveJSController/manufacturer
and check the version. It should be 23093. And yourext/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/
-
Also, did you restart Reactor after adding the node?
-
@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 aext/ZWaveJSController/zwavejs_devices.yaml
and it showsversion: 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.
-
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.
-
@toggledbits Ok, release deployed.
ext/ZWaveJSController/zwavejs_devices.yaml
now showsversion: 23194 revision: 1 format: 1
647.yaml
still showsmanufacturer_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. -
Yeah, this device is off. It's reporting
Multilevel Switch
for its generic class, andMotor 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.
-
@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?
-
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.
-
@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!
-
@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. -
@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.
-
@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. -
UPDATE: after many lost hours last night/this morning (hello, 0230 ET, looking at you) I found
cover.x
andpower_switch.x
to be woefully unreliable after reinterviewing the blinds.What has proven reliable is
position.set
for which I use0
forclosed
,50
foropen
and have the blinds (as they were previously) set to[1] YES
forReverse Direction
. -
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.
-
@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.
-
@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 IDBeach Blind
fromzwavejs
. As @tamorgen notes, there is also a new one (with the changes HA made) from my HASS controller calledBeach Blind Horizontal Slates Angle
which has a few less commands including those mentioned starting withx_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 andset_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 andcover.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 reflect0/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 usedposition.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.
-
@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.
if you go into the switch, it shows it as unavailable.
I would guess the power on/off cover.close / cover.open are remnants and probably need to be removed.