• Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
Run rule on dimmer change?
I

Reactor latest-23302-b7def56a; docker on Ubuntu 20.04; With Vera Plus and Ezlo Plus controllers

I'm trying to tie the dimmer level of a dimmer switch to the dimmer level of a dimmable device (fan canopy light controller). In the triggers section of the rule I can select "dimming.level changes" as the condition, and I can get said dimming level in an expression that I then use to set the dimming.set attribute of the dimming device in the Set Reaction section, but this only works when going from 0--><some value>. When going from <some value> --> <some other value> or <some value>-->0, this does not work, because the rule is already set (it went true with the first change, and hasn't gone false yet - this is expected behavior as per the documentation)

I can fix the <some value>-->0 issue by setting the Reset Reaction, but how can I get the rule to run - and set the entity dimming level - every time the switch value changes?

(I tired to upload a screen shot of what I have, but I just kept getting errors)

Multi-System Reactor
CallMeBot new interface?
wmarcolinW

Hi @toggledbits

Apparently, there have been some changes to the CallMeBot interface, as the service recently stopped working for me. I've tried several configurations, and none of the ones below are working.

# CallMeBot CallMeBot: profiles: default: # description - A friendly description of this profile (for menus) description: Default Profile New # # api_url - Access URL for CallMeBot API being used api_url: http://api.callmebot.com/start.php # # api_key - (if needed) API key (use for Facebook API, WhatsApp API, etc.). # If the API you are using does not require it, leave it # commented out or blank. api_key: "177xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxTGk" # # source - (if needed) Source field for some APIs. If yours does not require # it, leave it commented out or blank. #source: "source-value" # # phone - (if needed) Phone field for some APIs. If yours does not require # it, leave it commented out or blank. phone: "+5xxxxxxxx33" # # user - (if needed) User field for some APIs. If yours does not require # it, leave it commented out or blank. #user: "@xxxxxxxxxxxxx" # # lang - (optional) Language/voice; default "en-US-Standard-C". # See CallMeBot docs for possible values. lang: "en-US-Standard-C" # # rpt - (optional) Number of times to repeat message; default: 1. rpt: 2

I have already tested using the phone or the user.

Looking at the action log, I see that it starts, runs and finishes without any problems.

[latest-23302]2023-11-05T14:35:54.106Z <Engine:INFO> Enqueueing "teste<SET>" (rule-lolk0nlj:S) [latest-23302]2023-11-05T14:35:54.108Z <Engine:NOTICE> Starting reaction teste<SET> (rule-lolk0nlj:S) [latest-23302]2023-11-05T14:35:54.111Z <Engine:INFO> teste<SET> all actions completed.

When testing directly on the site, I see that it no longer uses API, and I haven't even found where to generate the API KEY.

http://api.callmebot.com/start.php?source=web&user=+5xxxxxxxx33&text=Teste callmebot pelo numero novo&lang=en-US-Standard-C

Please, can you advise me on what I should do to solve the problem?

Thanks.

Multi-System Reactor
Motion activated light now showing activation delay
V

Hi,

For years I have been using a rule that uses motion detection to maintain or turn on a light. For a while now, I noticed a significant delay (20 to 30 sec.) between the motion detection and the light coming on.

Here is my setup:

I am running the docker Home assistant 2023.11.3 and MSR 23302 on a Raspberry Pi 4 with raspian 64 bit. Motion sensor are coming from my DSC alarm panel via the HA Envisalink integration. The lights switch are zwave and are handled by HA via zwave-JS-UI.

I am not a software developper nor a specialist but here is, based on the log files of HA, MSR and zwavejs, the sequence of event as I understand it, on Nov 28 :

03:41:48 Home assistant sensor detect the motion. (from HA sensor log)
03:41:48 Reactor log report the "Living Rule Light On Set"
03:42:18 Both the zwavejsui and zwavejs logs show the light activation requests/commands

This is a delay of a little more than 30 ses between time that MSR activate the rule and zwavejs receive the request to turn on the light.

When I look at the detailed MSR logs, I can see that there is some time between the initial rule activation and its completion that correspond to the time line above. Again, without understanding everyting, the delay seemed to be coming from MSR (Or my rules/configuration). Here's the MSR Log:

Access via Synology

Here are the 2 Rules that control the light:

Living Room Light On

Screenshot 2023-11-29 114149.jpg

Living Room Light Off

Screenshot 2023-11-29 114451.jpg

This is not a major issue but it is a change from the initial behaviur I was having.

Thanks in advance

Multi-System Reactor
Using Zooz ZEN32 Scene Controller as Trigger
PablaP

Hello all, I recently installed a Zooz ZEN 32 scene controller and was looking for some guidance on how I could use a button press as a trigger in MSR. The scene controller has a total of 5 buttons that can activate scenes based on single press, double press, triple till 5 presses and also a press and hold. Currently in MSR I see an entity for the scene controller itself and separate entities for each button.

Using the MSR native Z wave controller I can see the button.state (shows if it was pressed single double...) and button.since which shows the last time the button was pressed. The issue with the button.state is that say I press the scene controller button once its state is single but it never "resets" it's state will remain single. So if I press the button again the trigger won't work (pulse action won't work here because the state never changes).

Going through HA similar issue but instead the x_hass.state is used and the number pertains to how many presses 0 means one press, 3 means 2 presses and so on. But again the x_hass.state never resets to an "off" state so retriggering the rule will not work if you press the button again.

Before I tackle this in other ways using separate rules, input booleans and expressions is there any other way I can go about this? To me I need to trigger that is something like button_pressed.single but I don't see that option.

No logs since there is technically no issues and no real examples since I am stuck at the triggers part lol.

MSR 23302
Z Wave 0.1.23194
HA 2023.11.2

Multi-System Reactor
Upcoming Release -- Plan for the Future
toggledbitsT

Beginning with the next Reactor release, there will be some dependency changes and new deprecations.

These apply to users on bare-metal installs only. If you are running Reactor in a docker container, the following does not apply to you — the container supplies its own dependencies and will be up-to-date.

All versions of nodejs prior to 18 are now end-of-life (no maintenance), so starting with the next Reactor build, they are deprecated for use with Reactor; they will continue to work until March 1 2024 (about 3 months from now), so you need to upgrade before that date. The recommended version of nodejs is 20, which is the current long-term support (LTS) version (EOL in mid-2026). Version 18 is the prior LTS version and still supported (by OpenJS Foundation and Reactor) until mid-2025, so it's a good fallback if you have issues getting version 20 running. As of this writing, the current 20 is 20.10.0, and the current 18 is 18.18.2. Both have been tested with Reactor 23302.

Now, nodejs version 20.9.0 seems to have dependencies that are not easily resolved on Raspberry Pi OS (formerly Raspbian) Buster (Debian 10). If you are using an RPi running Buster, you should select nodejs 18. That gives you until mid-2025 to upgrade both nodejs and the RPi OS to a more modern version (the current RPi OS is bookworm, Debian 12, 64-bit). The tools/rpi-install.sh script will be enhanced for the next build to try to discern what is reasonable for your system and make the appropriate upgrades; it is safe to run even on a current Reactor install.

If you are running an OS other than Raspberry Pi OS, try for nodejs 20, but use 18 as a fallback if you can't get it installed and running.

Multi-System Reactor
Honeywell TH6320ZW2003_T6_Pro_ZWave shows hvac_control.state="heat" in zwaveJSController
SnowmanS

@togglebits I have another one for you.

HASS controller shows hvac_control.state="heating, cooling or idle".

ZWaveJSController controller shows hvac_control.state="heat, cool, or idle"

I believe hvac_control.state="heating, cooling or idle" should be what the ZWaveJSController should show.

"heat", "cool" or "off" are values assigned to the hvac_control.mode attribute.

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 thermostat 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

battery_power.level=0.95 battery_power.since=1700301347874 humidity_sensor.units="%" humidity_sensor.value=40 hvac_blower_unit.filter_change=null hvac_blower_unit.mode="low" hvac_blower_unit.state=true hvac_control.mode="heat" hvac_control.state="heat" hvac_cooling_unit.setpoint=23.5 hvac_cooling_unit.state=false hvac_cooling_unit.units="°C" hvac_heating_unit.setpoint=20.5 hvac_heating_unit.state=false hvac_heating_unit.units="°C" power_source.source=null temperature_sensor.units="°C" temperature_sensor.value=20.5 x_debug.dt={"entity_class":"Thermostat","match":"deviceClass.generic.key=8","capabilities":["hvac_control"],"primary_attribute":"hvac_control.state","description":"T6 Pro Z-Wave Programmable Thermostat","model":"TH6320ZW","default_name":"Honeywell T6 Pro Thermostat","values":[{"valueId":"113:Power Management:Mains status","capabilities":{"power_source":{"attributes":{"source":{"expr":"([ 'unknown', 'unknown', 'dc', 'ac' ])[value ?# 0] ?? 'unknown'","update_only":true}}}}}],"manufacturerId":57,"productType":17,"productId":8} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=95 x_zwave_values.Configuration_Adaptive_Intelligent_Recovery=1 x_zwave_values.Configuration_Air_Filter_1_Reminder=0 x_zwave_values.Configuration_Air_Filter_2_Reminder=0 x_zwave_values.Configuration_Air_Filters=1 x_zwave_values.Configuration_Auto_Changeover=0 x_zwave_values.Configuration_Auto_Differential=0 x_zwave_values.Configuration_Aux_Heat_Cycle_Rate=9 x_zwave_values.Configuration_Aux_Heat_Outdoor_Lockout=0 x_zwave_values.Configuration_Auxiliary_Emergency_Control=0 x_zwave_values.Configuration_Auxiliary_Heat_Droop=0 x_zwave_values.Configuration_Auxiliary_Heat_Type=0 x_zwave_values.Configuration_Balance_Point=0 x_zwave_values.Configuration_Clock_Format=1 x_zwave_values.Configuration_Compressor_Protection=5 x_zwave_values.Configuration_Cool_Stage_1_Cycle_Rate=3 x_zwave_values.Configuration_Cool_Stage_2_Cycle_Rate=3 x_zwave_values.Configuration_Cool_Stages=1 x_zwave_values.Configuration_Daylight_Saving=1 x_zwave_values.Configuration_Dehumidification_Filter_Reminder=0 x_zwave_values.Configuration_Emergency_Heat_Cycle_Rate=9 x_zwave_values.Configuration_Emergency_Heat_Type=0 x_zwave_values.Configuration_Equipment_Type=2 x_zwave_values.Configuration_Fossil_Kit_Control=0 x_zwave_values.Configuration_Heat_Stage_1_Cycle_Rate=3 x_zwave_values.Configuration_Heat_Stage_2_Cycle_Rate=3 x_zwave_values.Configuration_Heat_Stages=1 x_zwave_values.Configuration_High_Cool_Stage_Finish=0 x_zwave_values.Configuration_High_Heat_Stage_Finish=0 x_zwave_values.Configuration_Humidification_Pad_Reminder=0 x_zwave_values.Configuration_Idle_Brightness=0 x_zwave_values.Configuration_Maximum_Heat_Temperature=75 x_zwave_values.Configuration_Minimum_Cool_Temperature=66 x_zwave_values.Configuration_Outdoor_Temperature_Sensor=0 x_zwave_values.Configuration_Reversing_Valve=0 x_zwave_values.Configuration_Schedule_Type=2 x_zwave_values.Configuration_Temperature_Offset=0 x_zwave_values.Configuration_Temperature_Scale=1 x_zwave_values.Configuration_UV_Bulb_1_Reminder=0 x_zwave_values.Configuration_UV_Bulb_2_Reminder=0 x_zwave_values.Configuration_UV_Devices=0 x_zwave_values.Configuration_Up_Stage_Timer_Aux_Heat=0 x_zwave_values.Configuration_Ventilation_Filter_Reminder=0 x_zwave_values.Manufacturer_Specific_manufacturerId=57 x_zwave_values.Manufacturer_Specific_productId=8 x_zwave_values.Manufacturer_Specific_productType=17 x_zwave_values.Multilevel_Sensor_Air_temperature=20.5 x_zwave_values.Multilevel_Sensor_Humidity=40 x_zwave_values.Notification_Power_Management_Mains_status=3 x_zwave_values.Notification_alarmLevel=0 x_zwave_values.Notification_alarmType=0 x_zwave_values.Thermostat_Fan_Mode_mode=1 x_zwave_values.Thermostat_Fan_Mode_off=false x_zwave_values.Thermostat_Fan_State_state=1 x_zwave_values.Thermostat_Mode_manufacturerData=null x_zwave_values.Thermostat_Mode_mode=1 x_zwave_values.Thermostat_Operating_State_state=0 x_zwave_values.Thermostat_Setpoint_setpoint_1=20.5 x_zwave_values.Thermostat_Setpoint_setpoint_11=18 x_zwave_values.Thermostat_Setpoint_setpoint_12=26 x_zwave_values.Thermostat_Setpoint_setpoint_2=23.5 x_zwave_values.Version_firmwareVersions=["1.3","1.4"] x_zwave_values.Version_hardwareVersion=1 x_zwave_values.Version_libraryType=6 x_zwave_values.Version_protocolVersion="4.61" zwave_device.capabilities=[49,64,66,67,68,69,112,113,114,128,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Thermostat" zwave_device.impl_sig="23318: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=[57,17,8] zwave_device.max_data_rate=null zwave_device.node_id=16 zwave_device.specific_class="General Thermostat V2" zwave_device.status=4 zwave_device.status_text="alive" zwave_device.version_info=[null,"1.3"]
Multi-System Reactor
Dismiss -option for updates
tunnusT

Certain MSR updates are irrelevant for some users (e.g. only Hass related changes when you are not using one), so I was wondering if there could be a dismiss (firmware) feature similar to Hubitat?

Then when you'll use "dismiss", a blue checkmark would disappear until there's a new firmware.

Multi-System Reactor
case statement with a single when clause fails
tunnusT

Noticed that if I try to use a case statement, I'll have to have multiple when clauses, otherwise I'll get syntax error.

(I tried to include a screenshot, but got parse error from the forum...)

The following works:

case when condition == true: "This is true" when condition == false: "Now it is false" else "Something else" end

But this will end up with syntax error:

case when condition == true: "This is true" else "Something else" end

Using build 23242 on Docker

Multi-System Reactor
[Solved] HTTP API no response on perform action
CrilleC

When doing something like curl -o - 'http://localhost:8111/api/v1/entity/ezlo>device_61baf509129e0725bd9f80e1/attribute/dimming.level' I get a response with current dimming level for example "0.6"
but curl -o - 'http://localhost:8111/api/v1/entity/ezlo>device_61baf509129e0725bd9f80e1/perform/dimming.set?level=0.8' sets the dimming level to 0.8 but gives no response which causes the connection to eventually timeout.

Doing it in a browser performs the action but leaves the tab with a spinning wheel of a loading page.

Is this expected behavior?

Edit: Solved in build 22142

Multi-System Reactor
TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL
SnowmanS

@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

battery_power.level=0.99 battery_power.since=1699401727360 binary_sensor.state=false tamper.state=true tilt_sensor.state=null x_debug.dt={"entity_class":"Binary Sensor","match":"deviceClass.generic.key=7","description":"Z-Wave Plus Tilt Sensor","default_name":"Tilt Sensor","model":"TILTZWAVE2.5-ECO","capabilities":["tilt_sensor"],"primary_attribute":"tilt_sensor.state","values":[{"valueId":"32:currentValue:","capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}}],"manufacturerId":330,"productType":4,"productId":3} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=99 x_zwave_values.Binary_Sensor_Any=false x_zwave_values.Configuration_Basic_Sets_for_Association_Group_2=0 x_zwave_values.Configuration_Send_Reports=0 x_zwave_values.Manufacturer_Specific_manufacturerId=330 x_zwave_values.Manufacturer_Specific_productId=3 x_zwave_values.Manufacturer_Specific_productType=4 x_zwave_values.Notification_Access_Control_Door_state=23 x_zwave_values.Notification_Access_Control_Door_state_simple=23 x_zwave_values.Notification_Home_Security_Cover_status=3 x_zwave_values.Notification_Power_Management_Battery_maintenance_status=0 x_zwave_values.Notification_UNKNOWN_0x46=23 x_zwave_values.Notification_alarmLevel=0 x_zwave_values.Notification_alarmType=0 x_zwave_values.Version_firmwareVersions=["10.1"] x_zwave_values.Version_hardwareVersion=2 x_zwave_values.Version_libraryType=6 x_zwave_values.Version_protocolVersion="4.5" x_zwave_values.Wake_Up_controllerNodeId=1 x_zwave_values.Wake_Up_wakeUpInterval=14400 zwave_device.capabilities=[48,112,113,114,128,132,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Notification Sensor" zwave_device.impl_sig="23305:1:22057:1" zwave_device.is_beaming=false zwave_device.is_listening=false zwave_device.is_routing=true zwave_device.is_secure=false zwave_device.last_wakeup=1699563172708 zwave_device.manufacturer_info=[330,4,3] zwave_device.max_data_rate=null zwave_device.node_id=24 zwave_device.specific_class="Notification Sensor" zwave_device.status=1 zwave_device.status_text="asleep" zwave_device.version_info=[null,"10.1"] zwave_device.wakeup_interval=14400
Multi-System Reactor
Inovelli LZW31 / Aeotec ZWA037 switches always displaying power_switch.state = false in zwaveJSController
SnowmanS

I have just noticed that two of my z-wave switches, Inovelli LZW31 and Aeotec ZWA037, although responding correctly to commands such as (turning on the switch, changing LED color, etc.), are not displaying the right power_switch.state when turned ON. All other attributes are showing proper values.

Example when I turn on either switches,
In Home Assistant (hass), the power_switch.state = true while in ZWaveJSController (zwavejs), the power_switch.state = false.

Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3

Here's what the log shows.

[latest-23302]2023-11-01T21:14:00.303Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23302]2023-11-01T21:14:00.304Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23302]2023-11-01T21:14:00.304Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23302]2023-11-01T21:14:00.304Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23302]2023-11-01T21:14:00.308Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23302]2023-11-01T21:14:00.309Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23302]2023-11-01T21:14:00.309Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23302]2023-11-01T21:14:00.309Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23302]2023-11-01T21:14:00.311Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23302]2023-11-01T21:14:00.312Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23302]2023-11-01T21:14:00.312Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23302]2023-11-01T21:14:00.313Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23302]2023-11-01T21:14:00.315Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23302]2023-11-01T21:14:00.317Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23302]2023-11-01T21:14:00.317Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23302]2023-11-01T21:14:00.317Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23302]2023-11-01T21:14:03.258Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) starting evaluation; because entity-changed Light#hass>light_office_light [latest-23302]2023-11-01T21:14:03.259Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) trigger evaluation result is true (previously false) [latest-23302]2023-11-01T21:14:03.260Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluated; rule state transition from RESET to SET! [latest-23302]2023-11-01T21:14:03.271Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluation complete [latest-23302]2023-11-01T21:14:03.273Z <Engine:INFO> Enqueueing "Toggle office light LED color state between green/blue Copy<SET>" (rule-lof5hpwe:S) [latest-23302]2023-11-01T21:14:03.285Z <Engine:NOTICE> Starting reaction Toggle office light LED color state between green/blue Copy<SET> (rule-lof5hpwe:S) [latest-23302]2023-11-01T21:14:03.287Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.set_config on Light#zwavejs>138-0 with [Object]{ "parameter": "84", "size": 1, "value": 3, "bitmask": 0 } [latest-23302]2023-11-01T21:14:03.345Z <Engine:INFO> Resuming reaction Toggle office light LED color state between green/blue Copy<SET> (rule-lof5hpwe:S) from step 2 [latest-23302]2023-11-01T21:14:03.346Z <Engine:INFO> Toggle office light LED color state between green/blue Copy<SET> all actions completed. [latest-23302]2023-11-01T21:14:05.191Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs node 138-0 no value +currentValue: found for power_switch.state [latest-23302]2023-11-01T21:14:05.205Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) starting evaluation; because entity-changed Light#hass>light_office_light [latest-23302]2023-11-01T21:14:05.205Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) trigger evaluation result is true (previously true) [latest-23302]2023-11-01T21:14:05.206Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluated; trigger state unchanged (true); rule state remains SET [latest-23302]2023-11-01T21:14:05.206Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluation complete [latest-23302]2023-11-01T21:14:10.503Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs node 138-0 no value +currentValue: found for power_switch.state [latest-23302]2023-11-01T21:14:10.518Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) starting evaluation; because entity-changed Light#hass>light_office_light [latest-23302]2023-11-01T21:14:10.519Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) trigger evaluation result is false (previously true) [latest-23302]2023-11-01T21:14:10.520Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluated; rule state transition from SET to RESET! [latest-23302]2023-11-01T21:14:10.529Z <Rule:INFO> Toggle office light LED color state between green/blue Copy (rule-lof5hpwe in Office) evaluation complete [latest-23302]2023-11-01T21:14:10.530Z <Engine:INFO> Enqueueing "Toggle office light LED color state between green/blue Copy<RESET>" (rule-lof5hpwe:R) [latest-23302]2023-11-01T21:14:10.542Z <Engine:NOTICE> Starting reaction Toggle office light LED color state between green/blue Copy<RESET> (rule-lof5hpwe:R) [latest-23302]2023-11-01T21:14:10.543Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.set_config on Light#zwavejs>138-0 with [Object]{ "parameter": "84", "size": 1, "value": 2, "bitmask": 0 } [latest-23302]2023-11-01T21:14:10.596Z <Engine:INFO> Resuming reaction Toggle office light LED color state between green/blue Copy<RESET> (rule-lof5hpwe:R) from step 2 [latest-23302]2023-11-01T21:14:10.597Z <Engine:INFO> Toggle office light LED color state between green/blue Copy<RESET> all actions completed. [latest-23302]2023-11-01T21:14:12.441Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs node 138-0 no value +currentValue: found for power_switch.state

PS I am trying to attach an image but getting "Something went wrong while parsing server response". Also, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version.

Hopefully I have provided the necessary information.

Thanks in advance.

Multi-System Reactor
Rule's sustain / delay reset etc. value parameterization thru entities
M

Some background
I have two simple rules that will toggle my carport's down lights depending on outdoor brightness when I open the motorized sliding gate. I.e. if the brightness is 1500 lux or less and the gate is opened, the down lights will be switched on, and when the gate is closed, the lights will switch off after 3 minutes. Pretty simple 'coming home' functionality so to speak.

Here's the switch off rule showing the 'hard coded' thresholds

Screenshot from 2023-10-31 18-44-46.png

The problem
I would like to parameterize the lux and switch off delay using entities. I bet the lux threshold can be done with local expressions the same way I do my WC background music scheduling:

weekdays_enabled = (time() >= time(getEntity( "mqtt>wc-music-weekdays-enable" ).attributes.string_sensor.value )) && (time() <= time(getEntity( "mqtt>wc-music-weekdays-disable" ).attributes.string_sensor.value ))

But the since I'm using the Condition must be sustained for functionality for the switch off rule, I have no idea how to parameterize that with some entity value.

So my question is that is it even possible to do this using entities or could there some other way to accomplish the same functionality? In this example it's the sustain -value but I might need same kind of parameterization for the delay reset also.

I have to go with entities, since my own HA system will provide the threshold values for the MSR through the MQTTController.

Help would be appreciated @toggledbits
br,
mgvra

MSR latest-23302-b7def56a and MQTTController [0.1.23254]

Multi-System Reactor
Have reactor shut off a light with no motion unless I turned it on manually
S

So I have a strange one here and I don't know if there is a way to do this or not. I have blue iris triggering a vera virtual switch when AI detects motion on my front porch. Reactor then triggers the light, this works perfect. I want to shut the light off when there is no motion, this also works perfect. What I am having am issue with is when someone turns on the light manually I don't want it to turn off after motion is detected. Example: we are expecting a pizza so we turn on the porch light. 5 min later amazon delivers a package, trips motion. 10 min later Reactor is going to turn off the light. If I manually turn on the light before motion is detected I do not want reactor to turn it off. For the life of me I cannot figure the logic out. Does anyone have any ideas?

Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT

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
Variable Value select array part
wmarcolinW

Hi @toggledbits

Is there any way that in the trigger the Varable Value could select the desired part of the array?

For example, I could have a global variable VarTEST$[Part1, Part2, Part3] like this: ${{ [TestText, 5, 3] }}. Use the Variable Value to validate a VarTEST[Part2] == 5 trigger.

What am I doing today? I've defined 3 global variables:

3ae76d20-ffce-4f66-9002-1b4d6cc7c3c3-image.png

And I validate each variable.

3bcc1d62-2ce1-41ca-9f00-f98578c0d597-image.png

In short, I would like to have a global variable of the array type, and be able to select which element of the array I would use for validation in a trigger.

Thanks

Multi-System Reactor
Need Some Help Using browser_mod (HA integration)
PablaP

Hello all I am trying to run the service call browser_mod.popup from MSR to HA. If I enter the service data in YAML like this:

dismissable: true autoclose: false timeout: 120000 content: type: custom:mushroom-alarm-control-panel-card entity: alarm_control_panel.home_partition states: - armed_home - armed_away layout: vertical show_keypad: true target: device_id: e684ad00b76e330e57a8c915dc367bc4

For some reason the target portion of the data isn't sent and therefor the popup shows up on all my browser mod devices not the only one I had specified in the device_id. Here is a snippet of the reactor log, no errors that I see just looks like the target info isn't being passed on.

[latest-23242]2023-10-12T23:51:50.795Z <Engine:INFO> Enqueueing "Main Floor Tablet Alarm Arming Popup<SET>" (rule-lnmn8t54:S) [latest-23242]2023-10-12T23:51:50.800Z <Engine:NOTICE> Starting reaction Main Floor Tablet Alarm Arming Popup<SET> (rule-lnmn8t54:S) [latest-23242]2023-10-12T23:51:50.813Z <HassController:INFO> HassController#hass action x_hass_system.call_service([Object]{ "service": "browser_mod.popup", "data": "data:\n dismissable: true\n autoclose: false\n timeout: 120000\n content:\n type: custom:mushroom-alarm-control-panel-card\n entity: alarm_control_panel.home_partition\n states:\n - armed_home\n - armed_away\n layout: vertical\n show_keypad: true\ntarget:\n device_id: e684ad00b76e330e57a8c915dc367bc4" }) on System#hass>system succeeded [latest-23242]2023-10-12T23:51:50.816Z <Engine:INFO> Resuming reaction Main Floor Tablet Alarm Arming Popup<SET> (rule-lnmn8t54:S) from step 1 [latest-23242]2023-10-12T23:51:50.817Z <Engine:INFO> Main Floor Tablet Alarm Arming Popup<SET> all actions completed.

So I used an online YAML to JSON converter since I am not the good with JSON and it converted the YAML to this:

{ "data": { "dismissable": true, "autoclose": false, "timeout": 120000, "content": { "type": "custom:mushroom-alarm-control-panel-card", "entity": "alarm_control_panel.bar_partition", "states": [ "armed_home", "armed_away" ], "layout": "vertical", "show_keypad": true } }, "target": { "device_id": "34ae76561192c4bb0b64fb07ad0f01c1" } }

When I use this in my reaction the popup doesn't show up properly. Something pops up but it's just a grey bar. Interestingly the JSON version actually does target only the device_id I had specified. Here is the reactor log output:

[latest-23242]2023-10-12T23:52:39.875Z <Engine:INFO> Enqueueing "Main Floor Tablet Alarm Arming Popup<SET>" (rule-lnmn8t54:S) [latest-23242]2023-10-12T23:52:39.880Z <Engine:NOTICE> Starting reaction Main Floor Tablet Alarm Arming Popup<SET> (rule-lnmn8t54:S) [latest-23242]2023-10-12T23:52:40.291Z <HassController:INFO> HassController#hass action x_hass_system.call_service([Object]{ "service": "browser_mod.popup", "data": "{\n \"data\": {\n \"dismissable\": true,\n \"autoclose\": false,\n \"timeout\": 120000,\n \"content\": {\n \"type\": \"custom:mushroom-alarm-control-panel-card\",\n \"entity\": \"alarm_control_panel.home_partition\",\n \"states\": [\n \"armed_home\",\n \"armed_away\"\n ],\n \"layout\": \"vertical\",\n \"show_keypad\": true\n }\n },\n \"target\": {\n \"device_id\": \"e684ad00b76e330e57a8c915dc367bc4\"\n }\n}" }) on System#hass>system succeeded [latest-23242]2023-10-12T23:52:40.293Z <Engine:INFO> Resuming reaction Main Floor Tablet Alarm Arming Popup<SET> (rule-lnmn8t54:S) from step 1 [latest-23242]2023-10-12T23:52:40.294Z <Engine:INFO> Main Floor Tablet Alarm Arming Popup<SET> all actions completed.

My limited skill with JSON has kind of backed me into a corner here, so if anyone could help me format it correctly that would be great!

MSR latest 23242
HA 2023.10.1

Multi-System Reactor
reactor-lgtv: LG TV Controller for Reactor
therealdbT

Here's my second attempt at a Reactor Controller, this time to integrate LG TVs:

GitHub - dbochicchio/reactor-lgtv: Reactor controller for LG TV (webos) GitHub - dbochicchio/reactor-lgtv: Reactor controller for LG TV (webos)

Reactor controller for LG TV (webos). Contribute to dbochicchio/reactor-lgtv development by creating an account on GitHub.

Standard capabilities are provided and TV volume, mute and switch status are controllable.
There's also an action to send toast notifications on your TV.

webos 5+ is required.

Multi-System Reactor
[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
G

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.

Multi-System Reactor

Welcome. If you’d like to participate in the discussion, rather than just read, then you can join the forum. As a member, you can interact with others here to share your experience and ask the questions you need answered.

For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used

Latest version is installed, we are still working on some visual changes.

Power_switch.state - no change state - EzloPlus - Msr v. 21351-a3aef - Synology Docker

Scheduled Pinned Locked Moved Multi-System Reactor
22 Posts 2 Posters 519 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Offline
    N Offline
    noelab
    wrote on last edited by
    #1

    Hi, Power Switch and Dimmer don't change state, but seems only for this manifacture that I have:
    Widom Dimmer and Double Switch.
    On Ezlo plus they change correctly state, but in MSR Entities they are always on power_switch.state=false also If I put them ON with a reaction.

    EzloPlus - Msr v. 21351-a3aef - Synology Docker

    [latest-21351]2021-12-18T15:48:52.612Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:48:52.612Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:49:41.720Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:49:41.720Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:50:22.258Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_61475325129e29124dfcd7e6
[latest-21351]2021-12-18T15:50:22.259Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_61475325129e29124dfcd7e6
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_61475325129e29124dfcd7e6
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:51:09.464Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:51:09.465Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:51:09.514Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:51:09.515Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:52:02.630Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:52:02.631Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:52:02.680Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:52:02.681Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:52:51.736Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:52:51.736Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:52:51.764Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:52:51.764Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)

    Thanks in advance

    1 Reply Last reply
    0
  • N Offline
    N Offline
    noelab
    wrote on last edited by
    #2

    At the moment the bulb is on, and this is what I see in Entities

    dimming.level=0
    dimming.step=0.1
    energy_sensor.units=null
    energy_sensor.value=null
    power_switch.state=false
    x_ezlo_device.battery_powered=false
    x_ezlo_device.category="dimmable_light"
    x_ezlo_device.manufacturer="Unknown"
    x_ezlo_device.model="Unknown"
    x_ezlo_device.parent=""
    x_ezlo_device.reachable=true
    x_ezlo_device.ready=true
    x_ezlo_device.room="613e2012129e2912114c0938"
    x_ezlo_device.status="idle"
    x_ezlo_device.subcategory="dimmable_in_wall"
    x_ezlo_device.type_id="329_4628_2560"
    x_ezlo_item.dimmer=0
    x_ezlo_item.dimmer_down=0
    x_ezlo_item.dimmer_stop=0
    x_ezlo_item.dimmer_up=0
    x_ezlo_item.electric_meter_kwh=0.492000013589859
    x_ezlo_item.electric_meter_watt=0
    x_ezlo_item.meter_reset=0
    x_ezlo_item.switch=false
    x_ezlo_object.id="6147578c129e29124dfcd814"
    zwave_device.capabilities=null
    zwave_device.failed=false
    zwave_device.manufacturer_info=["Unknown","Unknown",null]
    zwave_device.node_id=41
    zwave_device.version_info=null
    Capabilities: dimming, energy_sensor, power_switch, toggle, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device
    Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, toggle.toggle, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #3

    Thanks for the report and good info. I've posted a blind update 21352. Upgrade your container to that and let's see if those errors go away (spoiler: they should).

    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
  • N Offline
    N Offline
    noelab
    wrote on last edited by noelab
    #4

    Hi, thanks... It is ok for power_switch.state when the bulb is on. This is what I see in entities:

    dimming.level=1
dimming.step=0.1
energy_sensor.units=null
energy_sensor.value=0.5
power_sensor.units=null
power_sensor.value=2.48000001907349
power_switch.state=true
x_ezlo_device.battery_powered=false
x_ezlo_device.category="dimmable_light"
x_ezlo_device.manufacturer="Unknown"
x_ezlo_device.model="Unknown"
x_ezlo_device.parent=""
x_ezlo_device.reachable=true
x_ezlo_device.ready=true
x_ezlo_device.room="613e2012129e2912114c0938"
x_ezlo_device.status="idle"
x_ezlo_device.subcategory="dimmable_in_wall"
x_ezlo_device.type_id="329_4628_2560"
x_ezlo_item.dimmer=100
x_ezlo_item.dimmer_down=0
x_ezlo_item.dimmer_stop=0
x_ezlo_item.dimmer_up=0
x_ezlo_item.electric_meter_kwh=0.5
x_ezlo_item.electric_meter_watt=2.48000001907349
x_ezlo_item.meter_reset=0
x_ezlo_item.switch=true
x_ezlo_object.id="6147578c129e29124dfcd814"
zwave_device.capabilities=null
zwave_device.failed=false
zwave_device.manufacturer_info=["Unknown","Unknown",null]
zwave_device.node_id=41
zwave_device.version_info=null
Capabilities: dimming, energy_sensor, power_sensor, power_switch, toggle, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device
Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, toggle.toggle, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors

    but in log, there is stil this problem:

    [latest-21352]2021-12-19T22:26:48.725Z <wsapi:INFO> wsapi: connection from ::ffff:172.18.0.1
[latest-21352]2021-12-19T22:26:48.808Z <wsapi:INFO> wsapi: connection from ::ffff:172.18.0.1
[latest-21352]2021-12-19T22:26:48.830Z <wsapi:INFO> wsapi: connection from ::ffff:172.18.0.1
[latest-21352]2021-12-19T22:27:13.704Z <wsapi:INFO> client "172.18.0.1#3" closed, code=1001, reason=
[latest-21352]2021-12-19T22:27:14.191Z <wsapi:INFO> wsapi: connection from ::ffff:172.18.0.1
[latest-21352]2021-12-19T22:27:19.338Z <wsapi:INFO> client "172.18.0.1#1" closed, code=1001, reason=
[latest-21352]2021-12-19T22:27:19.749Z <wsapi:INFO> wsapi: connection from ::ffff:172.18.0.1
[latest-21352]2021-12-19T22:27:25.745Z <wsapi:INFO> client "172.18.0.1#2" closed, code=1001, reason=
[latest-21352]2021-12-19T22:29:32.187Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'KWh' for attribute units of energy_sensor#electric_meter_kwh (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:32.187Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'W' for attribute units of power_sensor#electric_meter_watt (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:32.237Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'KWh' for attribute units of energy_sensor#electric_meter_kwh (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:32.237Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'W' for attribute units of power_sensor#electric_meter_watt (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:32.289Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'KWh' for attribute units of energy_sensor#electric_meter_kwh (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:32.289Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'W' for attribute units of power_sensor#electric_meter_watt (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:32.389Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'KWh' for attribute units of energy_sensor#electric_meter_kwh (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:32.389Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'W' for attribute units of power_sensor#electric_meter_watt (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:44.819Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'KWh' for attribute units of energy_sensor#electric_meter_kwh (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:44.820Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'W' for attribute units of power_sensor#electric_meter_watt (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:58.871Z <Rule:5:Rule.js:771> Rule#rule-kthqmgb6 vR4 DLT 01 Bulb ID  requesting eval; entity-changed from Entity#vera>device_726
    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #5

    OK. That's almost working as it should. At least it's not getting in the way of the state update. One more time... blind build 21353 is now available.

    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
  • N Offline
    N Offline
    noelab
    wrote on last edited by
    #6

    I divide in two posts the log :

    [latest-21353]2021-12-19T23:08:39.981Z <Structure:INFO> Starting controller EzloController#ezlo
[latest-21353]2021-12-19T23:08:39.995Z <EzloController:INFO> EzloController#ezlo device mapping data loaded; checking...
[latest-21353]2021-12-19T23:08:39.997Z <EzloController:ERR> EzloController#ezlo implementation data references undefined capability power_sensor#electric_meter_watt
[latest-21353]2021-12-19T23:08:39.998Z <EzloController:ERR> EzloController#ezlo implementation data references undefined capability energy_sensor#electric_meter_kwh
[latest-21353]2021-12-19T23:08:39.999Z <EzloController:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21353]2021-12-19T23:08:40.000Z <Structure:INFO> Starting controller OWMWeatherController#weather
[latest-21353]2021-12-19T23:08:40.028Z <Structure:INFO> Starting controller SystemController#reactor_system
[latest-21353]2021-12-19T23:08:40.030Z <SystemController:NOTICE> Controller SystemController#reactor_system is now online.
[latest-21353]2021-12-19T23:08:40.058Z <EzloController:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21353]2021-12-19T23:08:40.065Z <app:INFO> Structure running; pausing for controllers' initial ready
[latest-21353]2021-12-19T23:08:40.163Z <VeraController:WARN> VeraController#vera ignoring geotag ([Object]{ "iduser": 1520131, "geotags": [ { "PK_User": 0, "id": 1, "accuracy": 0, "ishome": 1, "notify": 1, "radius": 100, "address": ", "color": "006e45", "latitude": "43.79130238128065", "longitude": "11.251052767038345", "name": "", "status": --null-- } ] }) for user 1520131, user not in user list
[latest-21353]2021-12-19T23:08:40.203Z <EzloController:INFO> EzloController#ezlo hub websocket connected (wss://10.0.4.119:17000)
[latest-21353]2021-12-19T23:08:40.204Z <EzloController:INFO> EzloController#ezlo hub websocket connected; inventory hub...
[latest-21353]2021-12-19T23:08:40.272Z <EzloController:INFO> EzloController#ezlo hub "90000464" is h2.1 (undefined) firmware "2.0.23.1817.1"
[latest-21353]2021-12-19T23:08:40.315Z <OWMWeatherController:INFO> OWMWeatherController#weather done; 1 locations, 0 failed
[latest-21353]2021-12-19T23:08:40.317Z <OWMWeatherController:NOTICE> Controller OWMWeatherController#weather is now online.
[latest-21353]2021-12-19T23:08:40.596Z <VeraController:NOTICE> Controller VeraController#vera is now online.
[latest-21353]2021-12-19T23:08:41.069Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "613e2959129e2912114c0982" (Entity#ezlo>device_613e2959129e2912114c0982); has [Array][ "613e2959129e2912114c0983", "basic", "613e2959129e2912114c0984", "battery", "613e2959129e2912114c0985", "tampering_cover_alarm", "613e2959129e2912114c0986", "acceleration_x_axis", "613e2959129e2912114c0987", "acceleration_y_axis", "613e2959129e2912114c0988", "acceleration_z_axis", "613e2959129e2912114c0989", "motion", "613e2959129e2912114c098a", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.071Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "613e2959129e2912114c0982" (Entity#ezlo>device_613e2959129e2912114c0982); has [Array][ "613e2959129e2912114c0983", "basic", "613e2959129e2912114c0984", "battery", "613e2959129e2912114c0985", "tampering_cover_alarm", "613e2959129e2912114c0986", "acceleration_x_axis", "613e2959129e2912114c0987", "acceleration_y_axis", "613e2959129e2912114c0988", "acceleration_z_axis", "613e2959129e2912114c0989", "motion", "613e2959129e2912114c098a", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.074Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "613e2959129e2912114c098d" (Entity#ezlo>device_613e2959129e2912114c098d); has [Array][ "613e2959129e2912114c098e", "temp" ]
[latest-21353]2021-12-19T23:08:41.074Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "613e2959129e2912114c098d" (Entity#ezlo>device_613e2959129e2912114c098d); has [Array][ "613e2959129e2912114c098e", "temp" ]
[latest-21353]2021-12-19T23:08:41.076Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "613e2959129e2912114c098f" (Entity#ezlo>device_613e2959129e2912114c098f); has [Array][ "613e2959129e2912114c0990", "lux" ]
[latest-21353]2021-12-19T23:08:41.076Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "613e2959129e2912114c098f" (Entity#ezlo>device_613e2959129e2912114c098f); has [Array][ "613e2959129e2912114c0990", "lux" ]
[latest-21353]2021-12-19T23:08:41.078Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=level_sensor cap value_sensor
[latest-21353]2021-12-19T23:08:41.078Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "613e2959129e2912114c0991" (Entity#ezlo>device_613e2959129e2912114c0991); has [Array][ "613e2959129e2912114c0992", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.079Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "613e2959129e2912114c0991" (Entity#ezlo>device_613e2959129e2912114c0991); has [Array][ "613e2959129e2912114c0992", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.094Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "61425d55129e29124dfcd782" (Entity#ezlo>device_61425d55129e29124dfcd782); has [Array][ "61425d55129e29124dfcd783", "basic", "61425d56129e29124dfcd784", "battery", "61425d56129e29124dfcd785", "tampering_cover_alarm", "61425d56129e29124dfcd786", "acceleration_x_axis", "61425d56129e29124dfcd787", "acceleration_y_axis", "61425d56129e29124dfcd788", "acceleration_z_axis", "61425d56129e29124dfcd789", "motion", "61425d56129e29124dfcd78a", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.094Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "61425d55129e29124dfcd782" (Entity#ezlo>device_61425d55129e29124dfcd782); has [Array][ "61425d55129e29124dfcd783", "basic", "61425d56129e29124dfcd784", "battery", "61425d56129e29124dfcd785", "tampering_cover_alarm", "61425d56129e29124dfcd786", "acceleration_x_axis", "61425d56129e29124dfcd787", "acceleration_y_axis", "61425d56129e29124dfcd788", "acceleration_z_axis", "61425d56129e29124dfcd789", "motion", "61425d56129e29124dfcd78a", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.095Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=level_sensor cap value_sensor
[latest-21353]2021-12-19T23:08:41.096Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "61425d56129e29124dfcd78b" (Entity#ezlo>device_61425d56129e29124dfcd78b); has [Array][ "61425d56129e29124dfcd78c", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.096Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "61425d56129e29124dfcd78b" (Entity#ezlo>device_61425d56129e29124dfcd78b); has [Array][ "61425d56129e29124dfcd78c", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.097Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "61425d56129e29124dfcd78d" (Entity#ezlo>device_61425d56129e29124dfcd78d); has [Array][ "61425d56129e29124dfcd78e", "temp" ]
[latest-21353]2021-12-19T23:08:41.097Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "61425d56129e29124dfcd78d" (Entity#ezlo>device_61425d56129e29124dfcd78d); has [Array][ "61425d56129e29124dfcd78e", "temp" ]
[latest-21353]2021-12-19T23:08:41.098Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "61425d56129e29124dfcd78f" (Entity#ezlo>device_61425d56129e29124dfcd78f); has [Array][ "61425d56129e29124dfcd790", "lux" ]
[latest-21353]2021-12-19T23:08:41.099Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "61425d56129e29124dfcd78f" (Entity#ezlo>device_61425d56129e29124dfcd78f); has [Array][ "61425d56129e29124dfcd790", "lux" ]
[latest-21353]2021-12-19T23:08:41.106Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c693129e29124dfcd7a7" (Entity#ezlo>device_6145c693129e29124dfcd7a7); has [Array][ "6145c693129e29124dfcd7a8", "basic", "6145c693129e29124dfcd7a9", "battery", "6145c693129e29124dfcd7aa", "tampering_cover_alarm", "6145c693129e29124dfcd7ab", "acceleration_x_axis", "6145c693129e29124dfcd7ac", "acceleration_y_axis", "6145c694129e29124dfcd7ad", "acceleration_z_axis", "6145c694129e29124dfcd7ae", "motion", "6145c694129e29124dfcd7af", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.107Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c693129e29124dfcd7a7" (Entity#ezlo>device_6145c693129e29124dfcd7a7); has [Array][ "6145c693129e29124dfcd7a8", "basic", "6145c693129e29124dfcd7a9", "battery", "6145c693129e29124dfcd7aa", "tampering_cover_alarm", "6145c693129e29124dfcd7ab", "acceleration_x_axis", "6145c693129e29124dfcd7ac", "acceleration_y_axis", "6145c694129e29124dfcd7ad", "acceleration_z_axis", "6145c694129e29124dfcd7ae", "motion", "6145c694129e29124dfcd7af", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.108Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "6145c694129e29124dfcd7b0" (Entity#ezlo>device_6145c694129e29124dfcd7b0); has [Array][ "6145c694129e29124dfcd7b1", "temp" ]
[latest-21353]2021-12-19T23:08:41.109Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c694129e29124dfcd7b0" (Entity#ezlo>device_6145c694129e29124dfcd7b0); has [Array][ "6145c694129e29124dfcd7b1", "temp" ]
[latest-21353]2021-12-19T23:08:41.110Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "6145c694129e29124dfcd7b2" (Entity#ezlo>device_6145c694129e29124dfcd7b2); has [Array][ "6145c694129e29124dfcd7b3", "lux" ]
[latest-21353]2021-12-19T23:08:41.111Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c694129e29124dfcd7b2" (Entity#ezlo>device_6145c694129e29124dfcd7b2); has [Array][ "6145c694129e29124dfcd7b3", "lux" ]
[latest-21353]2021-12-19T23:08:41.112Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=level_sensor cap value_sensor
[latest-21353]2021-12-19T23:08:41.112Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "6145c694129e29124dfcd7b4" (Entity#ezlo>device_6145c694129e29124dfcd7b4); has [Array][ "6145c694129e29124dfcd7b5", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.112Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c694129e29124dfcd7b4" (Entity#ezlo>device_6145c694129e29124dfcd7b4); has [Array][ "6145c694129e29124dfcd7b5", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.113Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c7ca129e29124dfcd7ba" (Entity#ezlo>device_6145c7ca129e29124dfcd7ba); has [Array][ "6145c7ca129e29124dfcd7bb", "basic", "6145c7ca129e29124dfcd7bc", "battery", "6145c7ca129e29124dfcd7bd", "motion", "6145c7ca129e29124dfcd7be", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.114Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c7ca129e29124dfcd7ba" (Entity#ezlo>device_6145c7ca129e29124dfcd7ba); has [Array][ "6145c7ca129e29124dfcd7bb", "basic", "6145c7ca129e29124dfcd7bc", "battery", "6145c7ca129e29124dfcd7bd", "motion", "6145c7ca129e29124dfcd7be", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.115Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "6145c7ca129e29124dfcd7bf" (Entity#ezlo>device_6145c7ca129e29124dfcd7bf); has [Array][ "6145c7ca129e29124dfcd7c0", "lux" ]
[latest-21353]2021-12-19T23:08:41.115Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c7ca129e29124dfcd7bf" (Entity#ezlo>device_6145c7ca129e29124dfcd7bf); has [Array][ "6145c7ca129e29124dfcd7c0", "lux" ]
[latest-21353]2021-12-19T23:08:41.116Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "6145c7ca129e29124dfcd7c1" (Entity#ezlo>device_6145c7ca129e29124dfcd7c1); has [Array][ "6145c7ca129e29124dfcd7c2", "temp" ]
[latest-21353]2021-12-19T23:08:41.116Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c7ca129e29124dfcd7c1" (Entity#ezlo>device_6145c7ca129e29124dfcd7c1); has [Array][ "6145c7ca129e29124dfcd7c2", "temp" ]
[latest-21353]2021-12-19T23:08:41.124Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "614755cd129e29124dfcd805" (Entity#ezlo>device_614755cd129e29124dfcd805); has [Array][ "614755cd129e29124dfcd806", "basic", "614755cd129e29124dfcd807", "battery", "614755cd129e29124dfcd808", "tampering_cover_alarm", "614755cd129e29124dfcd809", "acceleration_x_axis", "614755cd129e29124dfcd80a", "acceleration_y_axis", "614755cd129e29124dfcd80b", "acceleration_z_axis", "614755cd129e29124dfcd80c", "motion", "614755cd129e29124dfcd80d", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.125Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "614755cd129e29124dfcd805" (Entity#ezlo>device_614755cd129e29124dfcd805); has [Array][ "614755cd129e29124dfcd806", "basic", "614755cd129e29124dfcd807", "battery", "614755cd129e29124dfcd808", "tampering_cover_alarm", "614755cd129e29124dfcd809", "acceleration_x_axis", "614755cd129e29124dfcd80a", "acceleration_y_axis", "614755cd129e29124dfcd80b", "acceleration_z_axis", "614755cd129e29124dfcd80c", "motion", "614755cd129e29124dfcd80d", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.126Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "614755cd129e29124dfcd80e" (Entity#ezlo>device_614755cd129e29124dfcd80e); has [Array][ "614755ce129e29124dfcd80f", "temp" ]
[latest-21353]2021-12-19T23:08:41.126Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "614755cd129e29124dfcd80e" (Entity#ezlo>device_614755cd129e29124dfcd80e); has [Array][ "614755ce129e29124dfcd80f", "temp" ]
[latest-21353]2021-12-19T23:08:41.127Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "614755ce129e29124dfcd810" (Entity#ezlo>device_614755ce129e29124dfcd810); has [Array][ "614755ce129e29124dfcd811", "lux" ]
[latest-21353]2021-12-19T23:08:41.127Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "614755ce129e29124dfcd810" (Entity#ezlo>device_614755ce129e29124dfcd810); has [Array][ "614755ce129e29124dfcd811", "lux" ]
[latest-21353]2021-12-19T23:08:41.129Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=level_sensor cap value_sensor
[latest-21353]2021-12-19T23:08:41.129Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "614755ce129e29124dfcd812" (Entity#ezlo>device_614755ce129e29124dfcd812); has [Array][ "614755ce129e29124dfcd813", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.129Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "614755ce129e29124dfcd812" (Entity#ezlo>device_614755ce129e29124dfcd812); has [Array][ "614755ce129e29124dfcd813", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.132Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "614e0c30129e29124dfcd83b" (Entity#ezlo>device_614e0c30129e29124dfcd83b); has [Array][ "614e0c30129e29124dfcd83c", "switch", "614e0c30129e29124dfcd83d", "dimmer", "614e0c31129e29124dfcd83e", "dimmer_up", "614e0c31129e29124dfcd83f", "dimmer_down", "614e0c31129e29124dfcd840", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.132Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "614e0c30129e29124dfcd83b" (Entity#ezlo>device_614e0c30129e29124dfcd83b); has [Array][ "614e0c30129e29124dfcd83c", "switch", "614e0c30129e29124dfcd83d", "dimmer", "614e0c31129e29124dfcd83e", "dimmer_up", "614e0c31129e29124dfcd83f", "dimmer_down", "614e0c31129e29124dfcd840", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.132Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "614e0c30129e29124dfcd83b" (Entity#ezlo>device_614e0c30129e29124dfcd83b); has [Array][ "614e0c30129e29124dfcd83c", "switch", "614e0c30129e29124dfcd83d", "dimmer", "614e0c31129e29124dfcd83e", "dimmer_up", "614e0c31129e29124dfcd83f", "dimmer_down", "614e0c31129e29124dfcd840", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.133Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "614e0c30129e29124dfcd83b" (Entity#ezlo>device_614e0c30129e29124dfcd83b); has [Array][ "614e0c30129e29124dfcd83c", "switch", "614e0c30129e29124dfcd83d", "dimmer", "614e0c31129e29124dfcd83e", "dimmer_up", "614e0c31129e29124dfcd83f", "dimmer_down", "614e0c31129e29124dfcd840", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.134Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd841" (Entity#ezlo>device_614e0c31129e29124dfcd841); has [Array][ "614e0c31129e29124dfcd842", "switch", "614e0c31129e29124dfcd843", "dimmer", "614e0c31129e29124dfcd844", "dimmer_up", "614e0c31129e29124dfcd845", "dimmer_down", "614e0c31129e29124dfcd846", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.134Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd841" (Entity#ezlo>device_614e0c31129e29124dfcd841); has [Array][ "614e0c31129e29124dfcd842", "switch", "614e0c31129e29124dfcd843", "dimmer", "614e0c31129e29124dfcd844", "dimmer_up", "614e0c31129e29124dfcd845", "dimmer_down", "614e0c31129e29124dfcd846", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.134Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd841" (Entity#ezlo>device_614e0c31129e29124dfcd841); has [Array][ "614e0c31129e29124dfcd842", "switch", "614e0c31129e29124dfcd843", "dimmer", "614e0c31129e29124dfcd844", "dimmer_up", "614e0c31129e29124dfcd845", "dimmer_down", "614e0c31129e29124dfcd846", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.134Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "614e0c31129e29124dfcd841" (Entity#ezlo>device_614e0c31129e29124dfcd841); has [Array][ "614e0c31129e29124dfcd842", "switch", "614e0c31129e29124dfcd843", "dimmer", "614e0c31129e29124dfcd844", "dimmer_up", "614e0c31129e29124dfcd845", "dimmer_down", "614e0c31129e29124dfcd846", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.135Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd847" (Entity#ezlo>device_614e0c31129e29124dfcd847); has [Array][ "614e0c31129e29124dfcd848", "switch", "614e0c31129e29124dfcd849", "dimmer", "614e0c31129e29124dfcd84a", "dimmer_up", "614e0c31129e29124dfcd84b", "dimmer_down", "614e0c31129e29124dfcd84c", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.136Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd847" (Entity#ezlo>device_614e0c31129e29124dfcd847); has [Array][ "614e0c31129e29124dfcd848", "switch", "614e0c31129e29124dfcd849", "dimmer", "614e0c31129e29124dfcd84a", "dimmer_up", "614e0c31129e29124dfcd84b", "dimmer_down", "614e0c31129e29124dfcd84c", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.136Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd847" (Entity#ezlo>device_614e0c31129e29124dfcd847); has [Array][ "614e0c31129e29124dfcd848", "switch", "614e0c31129e29124dfcd849", "dimmer", "614e0c31129e29124dfcd84a", "dimmer_up", "614e0c31129e29124dfcd84b", "dimmer_down", "614e0c31129e29124dfcd84c", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.136Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "614e0c31129e29124dfcd847" (Entity#ezlo>device_614e0c31129e29124dfcd847); has [Array][ "614e0c31129e29124dfcd848", "switch", "614e0c31129e29124dfcd849", "dimmer", "614e0c31129e29124dfcd84a", "dimmer_up", "614e0c31129e29124dfcd84b", "dimmer_down", "614e0c31129e29124dfcd84c", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.137Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd84d" (Entity#ezlo>device_614e0c31129e29124dfcd84d); has [Array][ "614e0c31129e29124dfcd84e", "switch", "614e0c32129e29124dfcd84f", "dimmer", "614e0c32129e29124dfcd850", "dimmer_up", "614e0c32129e29124dfcd851", "dimmer_down", "614e0c32129e29124dfcd852", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.137Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd84d" (Entity#ezlo>device_614e0c31129e29124dfcd84d); has [Array][ "614e0c31129e29124dfcd84e", "switch", "614e0c32129e29124dfcd84f", "dimmer", "614e0c32129e29124dfcd850", "dimmer_up", "614e0c32129e29124dfcd851", "dimmer_down", "614e0c32129e29124dfcd852", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.137Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd84d" (Entity#ezlo>device_614e0c31129e29124dfcd84d); has [Array][ "614e0c31129e29124dfcd84e", "switch", "614e0c32129e29124dfcd84f", "dimmer", "614e0c32129e29124dfcd850", "dimmer_up", "614e0c32129e29124dfcd851", "dimmer_down", "614e0c32129e29124dfcd852", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.138Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "614e0c31129e29124dfcd84d" (Entity#ezlo>device_614e0c31129e29124dfcd84d); has [Array][ "614e0c31129e29124dfcd84e", "switch", "614e0c32129e29124dfcd84f", "dimmer", "614e0c32129e29124dfcd850", "dimmer_up", "614e0c32129e29124dfcd851", "dimmer_down", "614e0c32129e29124dfcd852", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.145Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61508730129e29124787e30c" (Entity#ezlo>device_61508730129e29124787e30c); has [Array][ "61508730129e29124787e30d", "switch", "61508730129e29124787e30e", "dimmer", "61508730129e29124787e30f", "dimmer_up", "61508730129e29124787e310", "dimmer_down", "61508730129e29124787e311", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.145Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61508730129e29124787e30c" (Entity#ezlo>device_61508730129e29124787e30c); has [Array][ "61508730129e29124787e30d", "switch", "61508730129e29124787e30e", "dimmer", "61508730129e29124787e30f", "dimmer_up", "61508730129e29124787e310", "dimmer_down", "61508730129e29124787e311", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.146Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61508730129e29124787e30c" (Entity#ezlo>device_61508730129e29124787e30c); has [Array][ "61508730129e29124787e30d", "switch", "61508730129e29124787e30e", "dimmer", "61508730129e29124787e30f", "dimmer_up", "61508730129e29124787e310", "dimmer_down", "61508730129e29124787e311", "dimmer_stop" ]
    1 Reply Last reply
    0
  • N Offline
    N Offline
    noelab
    wrote on last edited by
    #7 
    [latest-21353]2021-12-19T23:08:41.146Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61508730129e29124787e30c" (Entity#ezlo>device_61508730129e29124787e30c); has [Array][ "61508730129e29124787e30d", "switch", "61508730129e29124787e30e", "dimmer", "61508730129e29124787e30f", "dimmer_up", "61508730129e29124787e310", "dimmer_down", "61508730129e29124787e311", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.147Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61508730129e29124787e312" (Entity#ezlo>device_61508730129e29124787e312); has [Array][ "61508730129e29124787e313", "switch", "61508730129e29124787e314", "dimmer", "61508730129e29124787e315", "dimmer_up", "61508730129e29124787e316", "dimmer_down", "61508730129e29124787e317", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.147Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61508730129e29124787e312" (Entity#ezlo>device_61508730129e29124787e312); has [Array][ "61508730129e29124787e313", "switch", "61508730129e29124787e314", "dimmer", "61508730129e29124787e315", "dimmer_up", "61508730129e29124787e316", "dimmer_down", "61508730129e29124787e317", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.148Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61508730129e29124787e312" (Entity#ezlo>device_61508730129e29124787e312); has [Array][ "61508730129e29124787e313", "switch", "61508730129e29124787e314", "dimmer", "61508730129e29124787e315", "dimmer_up", "61508730129e29124787e316", "dimmer_down", "61508730129e29124787e317", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.148Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61508730129e29124787e312" (Entity#ezlo>device_61508730129e29124787e312); has [Array][ "61508730129e29124787e313", "switch", "61508730129e29124787e314", "dimmer", "61508730129e29124787e315", "dimmer_up", "61508730129e29124787e316", "dimmer_down", "61508730129e29124787e317", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.149Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61508730129e29124787e318" (Entity#ezlo>device_61508730129e29124787e318); has [Array][ "61508730129e29124787e319", "switch", "61508730129e29124787e31a", "dimmer", "61508730129e29124787e31b", "dimmer_up", "61508730129e29124787e31c", "dimmer_down", "61508731129e29124787e31d", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.149Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61508730129e29124787e318" (Entity#ezlo>device_61508730129e29124787e318); has [Array][ "61508730129e29124787e319", "switch", "61508730129e29124787e31a", "dimmer", "61508730129e29124787e31b", "dimmer_up", "61508730129e29124787e31c", "dimmer_down", "61508731129e29124787e31d", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.150Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61508730129e29124787e318" (Entity#ezlo>device_61508730129e29124787e318); has [Array][ "61508730129e29124787e319", "switch", "61508730129e29124787e31a", "dimmer", "61508730129e29124787e31b", "dimmer_up", "61508730129e29124787e31c", "dimmer_down", "61508731129e29124787e31d", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.150Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61508730129e29124787e318" (Entity#ezlo>device_61508730129e29124787e318); has [Array][ "61508730129e29124787e319", "switch", "61508730129e29124787e31a", "dimmer", "61508730129e29124787e31b", "dimmer_up", "61508730129e29124787e31c", "dimmer_down", "61508731129e29124787e31d", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.151Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61508731129e29124787e31e" (Entity#ezlo>device_61508731129e29124787e31e); has [Array][ "61508731129e29124787e31f", "switch", "61508731129e29124787e320", "dimmer", "61508731129e29124787e321", "dimmer_up", "61508731129e29124787e322", "dimmer_down", "61508731129e29124787e323", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.151Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61508731129e29124787e31e" (Entity#ezlo>device_61508731129e29124787e31e); has [Array][ "61508731129e29124787e31f", "switch", "61508731129e29124787e320", "dimmer", "61508731129e29124787e321", "dimmer_up", "61508731129e29124787e322", "dimmer_down", "61508731129e29124787e323", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.152Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61508731129e29124787e31e" (Entity#ezlo>device_61508731129e29124787e31e); has [Array][ "61508731129e29124787e31f", "switch", "61508731129e29124787e320", "dimmer", "61508731129e29124787e321", "dimmer_up", "61508731129e29124787e322", "dimmer_down", "61508731129e29124787e323", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.152Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61508731129e29124787e31e" (Entity#ezlo>device_61508731129e29124787e31e); has [Array][ "61508731129e29124787e31f", "switch", "61508731129e29124787e320", "dimmer", "61508731129e29124787e321", "dimmer_up", "61508731129e29124787e322", "dimmer_down", "61508731129e29124787e323", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.154Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61522118129e291232d6d9fd" (Entity#ezlo>device_61522118129e291232d6d9fd); has [Array][ "61522118129e291232d6d9fe", "switch", "61522118129e291232d6d9ff", "dimmer", "61522118129e291232d6da00", "dimmer_up", "61522118129e291232d6da01", "dimmer_down", "61522118129e291232d6da02", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.155Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61522118129e291232d6d9fd" (Entity#ezlo>device_61522118129e291232d6d9fd); has [Array][ "61522118129e291232d6d9fe", "switch", "61522118129e291232d6d9ff", "dimmer", "61522118129e291232d6da00", "dimmer_up", "61522118129e291232d6da01", "dimmer_down", "61522118129e291232d6da02", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.155Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61522118129e291232d6d9fd" (Entity#ezlo>device_61522118129e291232d6d9fd); has [Array][ "61522118129e291232d6d9fe", "switch", "61522118129e291232d6d9ff", "dimmer", "61522118129e291232d6da00", "dimmer_up", "61522118129e291232d6da01", "dimmer_down", "61522118129e291232d6da02", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.155Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61522118129e291232d6d9fd" (Entity#ezlo>device_61522118129e291232d6d9fd); has [Array][ "61522118129e291232d6d9fe", "switch", "61522118129e291232d6d9ff", "dimmer", "61522118129e291232d6da00", "dimmer_up", "61522118129e291232d6da01", "dimmer_down", "61522118129e291232d6da02", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.156Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61522118129e291232d6da03" (Entity#ezlo>device_61522118129e291232d6da03); has [Array][ "61522118129e291232d6da04", "switch", "61522118129e291232d6da05", "dimmer", "61522118129e291232d6da06", "dimmer_up", "61522119129e291232d6da07", "dimmer_down", "61522119129e291232d6da08", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.157Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61522118129e291232d6da03" (Entity#ezlo>device_61522118129e291232d6da03); has [Array][ "61522118129e291232d6da04", "switch", "61522118129e291232d6da05", "dimmer", "61522118129e291232d6da06", "dimmer_up", "61522119129e291232d6da07", "dimmer_down", "61522119129e291232d6da08", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.157Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61522118129e291232d6da03" (Entity#ezlo>device_61522118129e291232d6da03); has [Array][ "61522118129e291232d6da04", "switch", "61522118129e291232d6da05", "dimmer", "61522118129e291232d6da06", "dimmer_up", "61522119129e291232d6da07", "dimmer_down", "61522119129e291232d6da08", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.157Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61522118129e291232d6da03" (Entity#ezlo>device_61522118129e291232d6da03); has [Array][ "61522118129e291232d6da04", "switch", "61522118129e291232d6da05", "dimmer", "61522118129e291232d6da06", "dimmer_up", "61522119129e291232d6da07", "dimmer_down", "61522119129e291232d6da08", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.158Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61522119129e291232d6da09" (Entity#ezlo>device_61522119129e291232d6da09); has [Array][ "61522119129e291232d6da0a", "switch", "61522119129e291232d6da0b", "dimmer", "61522119129e291232d6da0c", "dimmer_up", "61522119129e291232d6da0d", "dimmer_down", "61522119129e291232d6da0e", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.159Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61522119129e291232d6da09" (Entity#ezlo>device_61522119129e291232d6da09); has [Array][ "61522119129e291232d6da0a", "switch", "61522119129e291232d6da0b", "dimmer", "61522119129e291232d6da0c", "dimmer_up", "61522119129e291232d6da0d", "dimmer_down", "61522119129e291232d6da0e", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.159Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61522119129e291232d6da09" (Entity#ezlo>device_61522119129e291232d6da09); has [Array][ "61522119129e291232d6da0a", "switch", "61522119129e291232d6da0b", "dimmer", "61522119129e291232d6da0c", "dimmer_up", "61522119129e291232d6da0d", "dimmer_down", "61522119129e291232d6da0e", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.159Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61522119129e291232d6da09" (Entity#ezlo>device_61522119129e291232d6da09); has [Array][ "61522119129e291232d6da0a", "switch", "61522119129e291232d6da0b", "dimmer", "61522119129e291232d6da0c", "dimmer_up", "61522119129e291232d6da0d", "dimmer_down", "61522119129e291232d6da0e", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.161Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61522119129e291232d6da0f" (Entity#ezlo>device_61522119129e291232d6da0f); has [Array][ "61522119129e291232d6da10", "switch", "61522119129e291232d6da11", "dimmer", "61522119129e291232d6da12", "dimmer_up", "61522119129e291232d6da13", "dimmer_down", "61522119129e291232d6da14", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.162Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61522119129e291232d6da0f" (Entity#ezlo>device_61522119129e291232d6da0f); has [Array][ "61522119129e291232d6da10", "switch", "61522119129e291232d6da11", "dimmer", "61522119129e291232d6da12", "dimmer_up", "61522119129e291232d6da13", "dimmer_down", "61522119129e291232d6da14", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.162Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61522119129e291232d6da0f" (Entity#ezlo>device_61522119129e291232d6da0f); has [Array][ "61522119129e291232d6da10", "switch", "61522119129e291232d6da11", "dimmer", "61522119129e291232d6da12", "dimmer_up", "61522119129e291232d6da13", "dimmer_down", "61522119129e291232d6da14", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.162Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61522119129e291232d6da0f" (Entity#ezlo>device_61522119129e291232d6da0f); has [Array][ "61522119129e291232d6da10", "switch", "61522119129e291232d6da11", "dimmer", "61522119129e291232d6da12", "dimmer_up", "61522119129e291232d6da13", "dimmer_down", "61522119129e291232d6da14", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.173Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "6198168b129e2918c5ce97bc" (Entity#ezlo>device_6198168b129e2918c5ce97bc); has [Array][ "6198168b129e2918c5ce97bd", "dimmer", "6198168b129e2918c5ce97be", "dimmer_up", "6198168b129e2918c5ce97bf", "dimmer_down", "6198168b129e2918c5ce97c0", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.174Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "619816bb129e2918c5ce97c1" (Entity#ezlo>device_619816bb129e2918c5ce97c1); has [Array][ "619816bb129e2918c5ce97c2", "dimmer", "619816bb129e2918c5ce97c3", "dimmer_up", "619816bc129e2918c5ce97c4", "dimmer_down", "619816bc129e2918c5ce97c5", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.175Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "6198173f129e2918c5ce97c6" (Entity#ezlo>device_6198173f129e2918c5ce97c6); has [Array][ "6198173f129e2918c5ce97c7", "dimmer", "6198173f129e2918c5ce97c8", "dimmer_up", "6198173f129e2918c5ce97c9", "dimmer_down", "6198173f129e2918c5ce97ca", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.176Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "61981760129e2918c5ce97cb" (Entity#ezlo>device_61981760129e2918c5ce97cb); has [Array][ "61981760129e2918c5ce97cc", "dimmer", "61981760129e2918c5ce97cd", "dimmer_up", "61981760129e2918c5ce97ce", "dimmer_down", "61981760129e2918c5ce97cf", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.177Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "61981770129e2918c5ce97d0" (Entity#ezlo>device_61981770129e2918c5ce97d0); has [Array][ "61981770129e2918c5ce97d1", "dimmer", "61981770129e2918c5ce97d2", "dimmer_up", "61981770129e2918c5ce97d3", "dimmer_down", "61981770129e2918c5ce97d4", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.178Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "6198177e129e2918c5ce97d5" (Entity#ezlo>device_6198177e129e2918c5ce97d5); has [Array][ "6198177e129e2918c5ce97d6", "dimmer", "6198177e129e2918c5ce97d7", "dimmer_up", "6198177e129e2918c5ce97d8", "dimmer_down", "6198177e129e2918c5ce97d9", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.179Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "6198178b129e2918c5ce97da" (Entity#ezlo>device_6198178b129e2918c5ce97da); has [Array][ "6198178b129e2918c5ce97db", "dimmer", "6198178b129e2918c5ce97dc", "dimmer_up", "6198178b129e2918c5ce97dd", "dimmer_down", "6198178b129e2918c5ce97de", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.183Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "6198179b129e2918c5ce97df" (Entity#ezlo>device_6198179b129e2918c5ce97df); has [Array][ "6198179b129e2918c5ce97e0", "dimmer", "6198179b129e2918c5ce97e1", "dimmer_up", "6198179b129e2918c5ce97e2", "dimmer_down", "6198179b129e2918c5ce97e3", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.184Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "619817a6129e2918c5ce97e4" (Entity#ezlo>device_619817a6129e2918c5ce97e4); has [Array][ "619817a6129e2918c5ce97e5", "dimmer", "619817a7129e2918c5ce97e6", "dimmer_up", "619817a7129e2918c5ce97e7", "dimmer_down", "619817a7129e2918c5ce97e8", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.185Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "619817b2129e2918c5ce97e9" (Entity#ezlo>device_619817b2129e2918c5ce97e9); has [Array][ "619817b2129e2918c5ce97ea", "dimmer", "619817b3129e2918c5ce97eb", "dimmer_up", "619817b3129e2918c5ce97ec", "dimmer_down", "619817b3129e2918c5ce97ed", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.186Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "619817c2129e2918c5ce97ee" (Entity#ezlo>device_619817c2129e2918c5ce97ee); has [Array][ "619817c3129e2918c5ce97ef", "dimmer", "619817c3129e2918c5ce97f0", "dimmer_up", "619817c3129e2918c5ce97f1", "dimmer_down", "619817c3129e2918c5ce97f2", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.187Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "619817d0129e2918c5ce97f3" (Entity#ezlo>device_619817d0129e2918c5ce97f3); has [Array][ "619817d0129e2918c5ce97f4", "dimmer", "619817d0129e2918c5ce97f5", "dimmer_up", "619817d0129e2918c5ce97f6", "dimmer_down", "619817d0129e2918c5ce97f7", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.190Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "619817de129e2918c5ce97f8" (Entity#ezlo>device_619817de129e2918c5ce97f8); has [Array][ "619817de129e2918c5ce97f9", "dimmer", "619817de129e2918c5ce97fa", "dimmer_up", "619817de129e2918c5ce97fb", "dimmer_down", "619817de129e2918c5ce97fc", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.192Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=door_lock cap keypad
[latest-21353]2021-12-19T23:08:41.196Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "619903e9129e29123e89442e" (Entity#ezlo>device_619903e9129e29123e89442e); has [Array][ "619903e9129e29123e89442f", "basic", "619903e9129e29123e894430", "battery", "619903e9129e29123e894431", "tampering_cover_alarm", "619903e9129e29123e894432", "battery_maintenance_state", "619903e9129e29123e894433", "dw_state", "619903e9129e29123e894434", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.196Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "619903e9129e29123e89442e" (Entity#ezlo>device_619903e9129e29123e89442e); has [Array][ "619903e9129e29123e89442f", "basic", "619903e9129e29123e894430", "battery", "619903e9129e29123e894431", "tampering_cover_alarm", "619903e9129e29123e894432", "battery_maintenance_state", "619903e9129e29123e894433", "dw_state", "619903e9129e29123e894434", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.198Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "619903e9129e29123e894437" (Entity#ezlo>device_619903e9129e29123e894437); has [Array][ "619903ea129e29123e894438", "heat_alarm", "619903ea129e29123e894439", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.198Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "619903e9129e29123e894437" (Entity#ezlo>device_619903e9129e29123e894437); has [Array][ "619903ea129e29123e894438", "heat_alarm", "619903ea129e29123e894439", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.200Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "619903ea129e29123e89443a" (Entity#ezlo>device_619903ea129e29123e89443a); has [Array][ "619903ea129e29123e89443b", "temp" ]
[latest-21353]2021-12-19T23:08:41.200Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "619903ea129e29123e89443a" (Entity#ezlo>device_619903ea129e29123e89443a); has [Array][ "619903ea129e29123e89443b", "temp" ]
[latest-21353]2021-12-19T23:08:41.239Z <EzloController:INFO> EzloController#ezlo hub inventory complete/successful; 1034ms
    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #8

    OK. Those are benign, but I'd still like to try and clean them up. There are devices listed that aren't in the previous upload you gave me, so can I ask that you use that upload link previously sent (in DM to you here) and upload the latest [data--see edit below] file from your logs directory? That will tell me what the devices are reporting more clearly.

    Edit: the file is now called ezlo_inventory.json for the latest version.

    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
  • N Offline
    N Offline
    noelab
    wrote on last edited by
    #9

    Hi, the file it is uploaded.

    Thanks

    1 Reply Last reply
    0
  • N Offline
    N Offline
    noelab
    wrote on last edited by
    #10

    If can help, today I added another zwave device "Widom Smart Plug" https://www.widom.it/wp-content/uploads/2019/08/Widom-Smart-Plug_EN_20190404_0.pdf
    At the moment it is ON and in Entities power.switch_state is FALSE

    energy_sensor.units="kilo_watt_hour"
energy_sensor.value=0.0230000000447035
power_sensor.units="watt"
power_sensor.value=36.7000007629395
power_switch.state=false
x_ezlo_device.battery_powered=false
x_ezlo_device.category="switch"
x_ezlo_device.manufacturer="Unknown"
x_ezlo_device.model="Unknown"
x_ezlo_device.parent=""
x_ezlo_device.reachable=true
x_ezlo_device.ready=true
x_ezlo_device.room="613e2037129e2912114c093e"
x_ezlo_device.status="idle"
x_ezlo_device.subcategory="interior_plugin"
x_ezlo_device.type_id="329_4628_1792"
x_ezlo_item.electric_meter_kwh=0.0230000000447035
x_ezlo_item.electric_meter_volt=230.399993896484
x_ezlo_item.electric_meter_watt=36.7000007629395
x_ezlo_item.meter_reset=0
x_ezlo_item.switch=false
x_ezlo_object.id="61c18f96129e291255528096"
zwave_device.capabilities=null
zwave_device.failed=false
zwave_device.manufacturer_info=["Unknown","Unknown",null]
zwave_device.node_id=60
zwave_device.version_info=null
Capabilities: energy_sensor, power_sensor, power_switch, toggle, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device
Actions: power_switch.off, power_switch.on, power_switch.set, toggle.toggle, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors
```
    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #11

    OK. If you would please, upload your ezlo_inventory.json file again.

    I would also note that the switch item (seen in raw form in x_ezlo_item.switch) also says false, so check in the (Vera/Ezlo) mobile app what it reports for state. It's not relevant what state the switch is physically in, only what state the hub thinks its in. If they don't agree, neither will Reactor.

    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
  • N Offline
    N Offline
    noelab
    wrote on last edited by
    #12

    Hi, checking Ezlo app and the device is also in OFF state on Dashboard. So the problem is not Reactor but Ezlo.

    Thanks!

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #13

    OK. New data maps with no further changes to previous work, so I'm going to go ahead and build. Watch for the update announcement in that topic.

    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
  • N Offline
    N Offline
    noelab
    wrote on last edited by
    #14

    Hi and Happy New Year!
    Trying a new test between MSR capability vs. Ezlo attribute and they show different. At the moment all devices are ON in the room:

    abe6c505-f852-494a-b222-b1b365f974c1-image.png

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #15

    Any errors in the log? You know you always need to look there whenever things don't seem right, yes?

    Also, I would do a hard-refresh of the browser and open that page again. I have seen it get out of sync once in a while but I haven't been able to figure out why as yet.

    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
  • N Offline
    N Offline
    noelab
    wrote on last edited by
    #16

    Updating to the last version, and doing a hard-refresh (F5) on the page, comparing the two images: now there are two devices ON

    ![alt text](b4a4f3cc-d2d2-4512-b8b0-eea49f845e70-image.png image url)

    I will try to close the brower and to erase data on the browser.

    1 Reply Last reply
    0
  • N Offline
    N Offline
    noelab
    wrote on last edited by
    #17

    Now seems ok, no error in the log. It was related to Google Chrome. Thanks!

    ![alt text](28e558ac-598b-4063-b0f7-eb96de2f993c-image.png image url)

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #18

    Not so sure... try changing the switch state of one of them (toggle one of them manually), see if both attributes follow... I'm guessing they'll diverge...

    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
  • N Offline
    N Offline
    noelab
    wrote on last edited by
    #19

    eheh, I was hoping to go happy to sleep 🙂 Yes, they diverge:

    ![alt text](c32f3243-5ef7-48d4-a5e9-ef1b5d72df08-image.png image url)

    1 Reply Last reply
    0
  • N Offline
    N Offline
    noelab
    wrote on last edited by
    #20

    what I can notice in "Entities" is that at the moment this device is OFF, but dimmer_level is =1

    L Bulb Spot Widom Dimmer
ezlo>device_61475325129e29124dfcd7e6
1
2:16:40 AM
dimming.level=1
dimming.step=0.1
dimming.undefined=0
energy_sensor.undefined="KWh"
energy_sensor.units="KWh"
energy_sensor.value=0.994000017642975
power_sensor.undefined="W"
power_sensor.units="W"
power_sensor.value=7.96000003814697
power_switch.state=true
power_switch.undefined=false
x_ezlo_device.battery_powered=false
x_ezlo_device.category="dimmable_light"
x_ezlo_device.manufacturer="Unknown"
x_ezlo_device.model="Unknown"
x_ezlo_device.parent=""
x_ezlo_device.reachable=true
x_ezlo_device.ready=true
x_ezlo_device.room="613e2024129e2912114c093b"
x_ezlo_device.status="idle"
x_ezlo_device.subcategory="dimmable_in_wall"
x_ezlo_device.type_id="329_4628_2560"
x_ezlo_item.dimmer=0
x_ezlo_item.dimmer_down=0
x_ezlo_item.dimmer_stop=0
x_ezlo_item.dimmer_up=0
x_ezlo_item.electric_meter_kwh=0.996999979019165
x_ezlo_item.electric_meter_watt=0
x_ezlo_item.meter_reset=0
x_ezlo_item.switch=false
x_ezlo_object.id="61475325129e29124dfcd7e6"
zwave_device.capabilities=null
zwave_device.failed=false
zwave_device.manufacturer_info=["Unknown","Unknown",null]
zwave_device.node_id=38
zwave_device.version_info=null
Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device
Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors

    or this other one, dimmer level diverge from msr to ezlo

    K Bulb Domitech
ezlo>device_61423589129e29124dfcd756
0
2:30:41 AM
dimming.level=0
dimming.step=0.1
dimming.undefined=0.25
power_switch.state=false
power_switch.undefined=true
x_ezlo_device.battery_powered=false
x_ezlo_device.category="dimmable_light"
x_ezlo_device.manufacturer="Domitech"
x_ezlo_device.model="ZE27EU"
x_ezlo_device.parent=""
x_ezlo_device.reachable=true
x_ezlo_device.ready=true
x_ezlo_device.room="613e2020129e2912114c093a"
x_ezlo_device.status="idle"
x_ezlo_device.subcategory="dimmable_bulb"
x_ezlo_device.type_id="526_19522_12596"
x_ezlo_item.dimmer=25
x_ezlo_item.dimmer_down=0
x_ezlo_item.dimmer_stop=0
x_ezlo_item.dimmer_up=0
x_ezlo_item.switch=true
x_ezlo_object.id="61423589129e29124dfcd756"
zwave_device.capabilities=null
zwave_device.failed=false
zwave_device.manufacturer_info=["Domitech","ZE27EU",null]
zwave_device.node_id=26
zwave_device.version_info=null
Capabilities: dimming, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device
Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors
    1 Reply Last reply
    0

Recent Topics

  • toggledbitsT
    Run rule on dimmer change?
  • toggledbitsT
    CallMeBot new interface?
  • F
    Hue Tap Dial compatible online switch
  • V
    Motion activated light now showing activation delay
  • SnowmanS
    Using Zooz ZEN32 Scene Controller as Trigger
  • toggledbitsT
    Upcoming Release -- Plan for the Future
  • G
    floor heating automation
  • T
    Need help. Looking people
  • SnowmanS
    Honeywell TH6320ZW2003_T6_Pro_ZWave shows hvac_control.state="heat" in zwaveJSController
  • toggledbitsT
    Dismiss -option for updates
  • toggledbitsT
    case statement with a single when clause fails
Powered by NodeBB | Contributors
Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
  • Login
  • Don't have an account? Register
  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
  • Login
  • Don't have an account? Register
  • Login or register to search.