Hi guys,
Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular.
Maybe there are better ways to organize my rule sets.
I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
I have installed MSR on a RP5 bare metal and then copied the config and store files. Everything seems to be on the RP5 but I am missing all global expression and I don't see the controller time.
Screenshot 2025-04-06 201446.png
My browser is Microsoft Edge Version 135.0.3179.54 (Official build) (64-bit)
I have probably done something stupid or missed a step but I am stuck.
Thanks for any help.
Hi,
It seems that the widget deletion does not work. I tried to drag the widget to the left (as explained in here https://smarthome.community/topic/1071/deleting-widgets?_=1744037333660)
but it does not delete it. Anyone else experiencing the same problem?
Also the landing page after login is empty and seems be have some JS issues on the dev console:
Screenshot from 2025-04-07 18-06-19.png
fd7f0424-debb-49d3-86d8-9a3b09ad3868-image.png
Using dockerized version of Reactor (Multi-hub) latest-25082-3c348de6 on Chromium 135.0.7049.52 (Official Build) snap (64-bit)
br,
mgvra
Good day all,
I have an notification set up for my washing machine to let me know when it's complete. I have a templete sensor set up in HAAS to let me know if it's Washing, in Standby, or off, based upon the power consumption (Shelly 1PM on outlets)
The MSR code is relatively simple. I have a built in false positive attribute for if MSR gets rebooted, because I would suddenly get tons of notifications when I upgraded MSR.
6774565a-06cc-443f-99c1-e71301b33d83-image.png
What I'm trying to introduce, is a way to verify that I just didn't bump the knob on the washing machine when transferring loads from the washer to the dryer, which turns on the display and brings the power above the Standby threshold.
The power goes up to 3.7W for about 4 minutes if the selector knob is bumped/turned.
What would the best way to do this be? I have most of my MSR code set up for a couple of years now, and my coding logic is struggling a bit.
I think I need a power threshold to be substained for a minimum time period (say 2 or 3 minutes, above 10W), before the other triggers can act. What would the best way to do that be?
Running: latest-25082-3c348de6
Fedora 41 Server
HAAS:
Core
2025.3.4
Supervisor
2025.03.4
Operating System
15.1
Frontend
20250306.0
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
I have the following yaml configuration in local_mqtt_devices file
x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }'While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Hi!
I get this message when I'm on the status tab:
System Configuration Check
The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds.
I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6.
HA versions are:
Core 2025.3.4
Supervisor 2025.03.4
Operating System 15.1
I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version.
Do anyone know what I can try?
Thanks in advance!
Let's Be Careful Out There (Hill Street reference...) 🙂
/Fanan
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB.
While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed.
So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response.
While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits
Thanks!
Hi ,
I'm on
-Reactor (Multi-hub) latest-25067-62e21a2d
-Docker on Synology NAS
-ZWaveJSUI 9.31.0.6c80945
Problem with ZwaveJSUI:
When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white.
I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui.
I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb".
After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color.
This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite.
x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33}The "cold white" and "warm white" settings interfer with the rgb color settings.
Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white
are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white.
So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have
x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColorIn zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set.
x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this?
x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33}Thanks in advance.
Good day all,
I have a reaction set up, that I use for both troubleshooting and changing home modes when one of my family members either arrive or are leaving. I use the companion app for HAAS on our iPhones, and HAAS reports if the person associated with the iPhone enters or leaves the geofenced area around my home. I'm sure most MSR and HAAS users are familiar with this.
I use this rule set mainly as a condition for other rules, however, as part of troubleshooting, a notification is sent through HAAS to the companion app when the rule becomes true. The problem is that I'm getting notifications now for both arriving and departing simultaneously.
96b3f7db-ba09-499e-a78c-86903b603857-image.png
36903cdd-a87f-473b-82ef-af9ef96d3c44-image.png It used to work fine as intended. I'm not sure exactly when it changed, but now I'm getting two notifications when either of these conditions change.
Any idea what could be happening?
Edit:
Running: latest-25082-3c348de6, bare-metal Linux
ZWaveJSControllerr [0.1.25082]
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem?
I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Similarly as for local expressions, global expressions evaluate and update fine when getEntity(...) structure is used. However, at least when certain functions are in use, expressions do not update.
Consider the following test case:
Screenshot 2025-03-13 at 16.29.42.png
Even though auto-evaluation is active, value does not change (it changes only if that expression is manually run). MSR restarts do not help.
Screenshot 2025-03-13 at 16.31.43.png
Note: Tested using build 25067 on Docker. I have also a PR open (but couldn't now get details or PR number as my Mantis account was somehow expired?).
Trying to understand what cause a local expresssion to be evaluated. I have read the manual but I am still not clear about it. Using the test rule below, I can see in the log that the rule is being automatically evaluated every time the temperature entity is changing. That is great...
What I am trying to understand is why the expression is not evaluated based on time as well since the "case" statement has time dependencies.
Any help would be appreciated
I have the following test rule:
eba6a3ea-ff61-4610-88c9-9b9864f11ff8-Screenshot 2025-01-21 095244.png
2d9c1ff5-7b73-4005-b324-9029c2709db9-Screenshot 2025-01-21 095302.png
Here is the expressioncode:
vFrom1 = "09:25:00", vFrom2 = "09:30:00", vFrom3 = "09:41:00", vTo = "10:55:00", # Get current time (format HH:MM:SS) vToDay = strftime("%H:%M:%S"), #Get current house temperature CurrentHouseTemp = getEntity( "hass>Thermostat2 " ).attributes.temperature_sensor.value, case when CurrentHouseTemp <= 19 and vToDay >= vFrom1 && vToDay <= vTo: "true1" # From1 when CurrentHouseTemp <= 20 and vToDay >= vFrom2 && vToDay <= vTo: "true2" # From2 when CurrentHouseTemp < 26 and vToDay >= vFrom3 && vToDay <= vTo: "true3" # From3 else "false" endI am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved.
The Runtime Error is different in the two browsers
Safari v18.3
Google Chrome 133.0.6943.142
TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.Steps to reproduce:
Click the pencil to edit a global reaction with a group.
Click the Exit button.
Runtime error appears.
or
Click Create Reaction
Click Add Action
Select Group
Add Condition such as Entity Attribute.
Add an Action.
Click Save
Click Exit
Runtime error appears.
I don’t know how long the error has been there as I haven’t edited the global reaction in a long time.
Reactor (Multi-hub) latest-25060-f32eaa46
Docker
Mac OS: 15.3.1
Thanks
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons.
I have not created a global expression for some times and just noticed this while doing some clean-up.
I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success.
Here's what the log shows.
[latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" }Reactor latest-25067-62e21a2d
Docker on Synology NAS
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method.
This was prompted by yesterday's fun and games with my ISP.
I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone)
I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions?
TIA
C
Hi,
I'm trying to integrate the sonos-mqtt (https://sonos2mqtt.svrooij.io/) with the MSR and it's coming along nicely so far.
But cannot wrap my head around how to define custom capabilities in MQTT templates. I need this for the TTS announcements and similarly for the notification sounds where I would pass the sound file as parameter.
So this is what I have in the local_mqtt_devices.yaml
capabilities: x_sonos_announcement: attributes: actions: speak: arguments: text: type: string volume: type: int delay: type: intAnd this is the template:
templates: sonos-announcement: capabilities: - x_sonos_announcement actions: x_sonos_announcement: speak: topic: "sonos/cmd/speak" payload: expr: > { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" } type: jsonSo the speak action should send something like this to topic sonos/cmd/speak
{ "text": "message goes here", "volume": 50, "delayMs": 100, "onlyWhenPlaying": false, "engine": "neural" }At startup the MSR seems to be quite unhappy with my configuration:
reactor | [latest-25016]2025-02-09T08:19:59.029Z <MQTTController:WARN> MQTTController#mqtt entity Entity#mqtt>sonos-announcement unable to configure capabilities [Array][ "x_sonos_announcement" ] reactor | i18n: missing fi-FI language string: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | i18n: missing fi-FI language string: Configuration for {0:q} has unrecognized capability {1:q} in actions reactor | Trace: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | at _T (/opt/reactor/server/lib/i18n.js:611:28) reactor | at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:125:25) reactor | at MQTTController.sendWarning (/opt/reactor/server/lib/Controller.js:627:30) reactor | at MQTTController.start (/var/reactor/ext/MQTTController/MQTTController.js:268:26) reactor | at async Promise.allSettled (index 0) Configuration for "sonos-announcement" has unrecognized capability "x_sonos_announcement" in actions Controller: MQTTController#mqtt Last 10:21:37 AM Configuration for "sonos-announcement" is incomplete because the following requested capabilities are undefined: x_sonos_announcement Controller: MQTTController#mqtt Last 10:21:37 AMThis is probably a pretty stupid question and the approach may not even work at all, but maybe someone or @toggledbits for sure, could point me to the right direction.
Basically the idea is to be able to send TTS messages from reactions using entity actions. I've previously used HTTP requests to Sonos HTTP API (https://hub.docker.com/r/chrisns/docker-node-sonos-http-api/) for the same functionality, but since moving to sonos-mqtt, I need a way to send the TTS notifications using MQTTController. Along with the actual message, volume and delay must also be parameterizable.
br,
mgvra
MSR latest-25016-d47fea38 / MQTTController [0.2.24293]
Hi, @toggledbits
I just noticed that following a reboot of my raspberry pi, some of the rules, that I was expecting to recover, are not catching up following a reboot. I have made a simple test rule (rule-m6rz6ol1) with only "after Date/time" as trigger and "turn on a lamp" as a set reaction. All my infrastructure is on the same board so Reactor, Hass, Zwavejs, ... are all rebooting.
Here is the sequence of the test case (All time converted to Zulu to match logs):
Rule "after Date/Time" set to 14:05:00z Shutdown on Raspberry Pi at 14:04:00z Power back up at 14:08:00z Rule overview shows true as of 14:08:14z waiting for 00:00:00 in GUIFrom the log I can see that MSR is picking up the rule and knows that the state of the rule has changed from false to true and tries to send the update to HASS but failed with websocket error.
Here is what I see from the log:
14:04:04z shutdown complete 14:08:08z Power up 14:08:13.111z websocket connection 14:08:15:323z Reaction to the light failed, Websocket not opened After there is a series of websocket connection attempt until 14:08:51z where it seemed to be really ready.Back in 2021 we had a discussion (https://smarthome.community/topic/700/solved-start-up?_=1738766986566) and you proposed to add a startup_delay:xxxx and startup_wait:xxxx parameter in the engine section of "reactor.yaml". When I try the startup_delay (this used to be a hard delay), the engine failed to start (I think). I then try the startup_wait:xxxx without any success. Since it wait for the connection status to be up to cancel the delay, it does not do anyting since Hass is reporting the socket up without really being up ( I think...).
Questions:
Did I figured it all wrong? should the startup_delay:xxxxx have worked? Any ideas?Here is the log:
OK now I am stuck. I did add the log but when I submit the editor complained saying that I am limited to 32767 characters. The log from the shutdown to the time the websocket is stable is about 300000 character long. What are my options?
Not a big issue simply a request if easily doable.
The MSR logs files inside the container are owned by root witch is fine however, the permissions are very restrictive. I do not know if there is something wrong with my installation but the logs permission are set to 222 (write only). Even if the docker volume is set for Read/Write the log files are retaining these values.
I go around the problem by doing a chmod 777 on all reactor logs but every time there is an MSR log rotation the permissions are set back to 222. So unless the permission are implemented in the container there is no permanent solution to this (that I know of).
I do not know much about Docker container so I do not know what is involved here.
Can the logfiles permission be simply chaged in the container to at least allow "other" read permission?
Could the MSR log rotation routine implement a chmod to set the permission?
Just a small anoyance
Thanks
Plugin InfluxFeed - Selecting Capabilities for Export - how to
-
hi, I'm trying to modify reator.yaml as illustrated in docs but no luck to change something, I continue to see only default capabilities/attributes.
How can I understand better the problem?Example OWM:
I want to add wx.feels_like and wx.pressure
is it correct? if yes, there are no changes in db fieldsselect_capabilities: x_ezlo_item: true wx: attributes: - feels_like - pressure - electric_meter_kwh - electric_meter_wattIf I want to add these parameter?
- x_ezlo_item.electric_meter_kwh
- x_ezlo_item.electric_meter_watt
After I did the changes, I let to start influxdb first and then MSR.
Also creating new bucket, I don't see any changes.Synology - Docker
Influxdb 2.1.1
Reactor (Multi-hub) latest-21342-ead7ca9Thanks in advance
-
Can you show your entire config for InfluxDB plugin? The indenting of your example would be incorrect to start, so I'd like to see the whole thing and make sure you're starting from something that has a chance at being functional. This doesn't look right on its face, but being a subset of the entire, it's hard to be sure.
-
Hi, this is the config
plugins: - id: influx # See the docs under Standard Plugins for configuration details. implementation: InfluxFeed enabled: true name: InfluxDB Feed config: # influx_url - URL to access InfluxDB server (default: http://localhost:8086) influx_url: "http://10.0.4.71:8086" # # ----- For InfluxDB 2.0+ ONLY ----- # influx_token - Token from InfluxDB 2.0 UI (required) influx_token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx # # influx_org - Organization ID (required) influx_org: myhome # # influx_bucket - Bucket name to which points are written (required) influx_bucket: reactor # # # ----- Optional (all versions) ----- # influx_retention_policy - Retention policy (optional). If not specified, # the retention policy of the bucket/database # will be used. #influx_retention_policy: "" # # ----- Filtering (all versions) ----- # select_capabilities - Capabilities that should be exported in addition # to the defaults. These are key/value pairs. If the # value is false, the capability is not exported (so # you can override the default). If the value is an # object, it may contain an "attributes" key with an # array value containing the names of attributes to # be exported (other attributes in the capability # are ignored). select_capabilities: light_sensor: true power_sensor: true dimming: false x_ezlo_item: true attributes: - electric_meter_kwh - electric_meter_watt # zwave_network: false # do not export this capability wx: # export wx capability, but only named attributes attributes: - temperature - humidity - feels_like -
OK. Your indenting is wonky and there's another error that's probably causing problems parsing the entire config. You should use a tool like https://yamlchecker.com on any changes you make (paste the entire config file) until you get used to the idiosyncrasies of YAML, and then any time you run into problems. There are also probably messages in the log file about problems reading the file, too, so be sure and always check there when something is not working as expected.
Specifically, on line 42, you can't have object keys in this position, because line 41 defines a value (
true) forx_ezlo_item. Usingtruesays you want everything from that capability; it's a short-cut. If you mean to limit the set of attributes forx_ezlo_item, then the value there must be an object for whichattributesis a key. So that would correctly look like this (other lines redacted for clarity):select_capabilities: x_ezlo_item: attributes: - electric_meter_kwh - electric_meter_wattYour
wxline (47) is not correctly indented, nor is the comment line before it, so that's going to be trouble as well. It should look like this in all:plugins: - id: influx # See the docs under Standard Plugins for configuration details. implementation: InfluxFeed enabled: true name: InfluxDB Feed config: # influx_url - URL to access InfluxDB server (default: http://localhost:8086) influx_url: "http://10.0.4.71:8086" # # ----- For InfluxDB 2.0+ ONLY ----- # influx_token - Token from InfluxDB 2.0 UI (required) influx_token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx # # influx_org - Organization ID (required) influx_org: myhome # # influx_bucket - Bucket name to which points are written (required) influx_bucket: reactor # # # ----- Optional (all versions) ----- # influx_retention_policy - Retention policy (optional). If not specified, # the retention policy of the bucket/database # will be used. #influx_retention_policy: "" # # ----- Filtering (all versions) ----- # select_capabilities - Capabilities that should be exported in addition # to the defaults. These are key/value pairs. If the # value is false, the capability is not exported (so # you can override the default). If the value is an # object, it may contain an "attributes" key with an # array value containing the names of attributes to # be exported (other attributes in the capability # are ignored). select_capabilities: light_sensor: true power_sensor: true dimming: false x_ezlo_item: attributes: - electric_meter_kwh - electric_meter_watt #zwave_network: false # do not export this capability wx: # export wx capability, but only named attributes attributes: - temperature - humidity - feels_likeUnfortunately, I realize YAML is a nuisance, but JSON would be worse, I loathe XML and its progeny, and the Microsoft-ish INI format isn't really up to the task either. I begrudgingly chose YAML because there's little that's better, and a lot of tools and documentation for it. Eventually, there will be a GUI for this kind of configuration, but that's a good way off yet.
-
I corrected the file
Valid YAML!
Still no changes in influxdb
I created a new bucket and new api tokens, when I go in "Explore" --> Filter Measurement -->Filter
I see only default data:
dimming is there
no wx.feels_like
and no x_ezlo_itemalso I stopped both container and I started first influxdb and then MSR, where I can check now?
-
It will only log things when things change. So make sure you are making things happen.
Also, what version of InfluxDB are you using?
And check the log file, particularly the messages output at startup.
-
Is is version InfluxDB 2.1.1
a lot of Warm from Ezlo
[latest-21342]2021-12-11T22:44:11.586Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=level_sensor cap value_sensor [latest-21342]2021-12-11T22:44:11.599Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=level_sensor cap value_sensor [latest-21342]2021-12-11T22:44:11.615Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=level_sensor cap value_sensor [latest-21342]2021-12-11T22:44:11.633Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=level_sensor cap value_sensor [latest-21342]2021-12-11T22:44:11.637Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.red for attribute rgb_color.red in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member red of null [latest-21342]2021-12-11T22:44:11.637Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.green for attribute rgb_color.green in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member green of null [latest-21342]2021-12-11T22:44:11.637Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.blue for attribute rgb_color.blue in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member blue of null [latest-21342]2021-12-11T22:44:11.638Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.cwhite > 0 ? floor( 5500 + value.cwhite * 3500 / 255 ) : floor( 2000 + value.wwhite * 3500 / 255 ) for attribute color_temperature.value in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member cwhite of null [latest-21342]2021-12-11T22:44:11.639Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.red for attribute rgb_color.red in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member red of null [latest-21342]2021-12-11T22:44:11.639Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.green for attribute rgb_color.green in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member green of null [latest-21342]2021-12-11T22:44:11.640Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.blue for attribute rgb_color.blue in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member blue of null [latest-21342]2021-12-11T22:44:11.640Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.cwhite > 0 ? floor( 5500 + value.cwhite * 3500 / 255 ) : floor( 2000 + value.wwhite * 3500 / 255 ) for attribute color_temperature.value in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member cwhite of null [latest-21342]2021-12-11T22:44:11.641Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.red for attribute rgb_color.red in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member red of null [latest-21342]2021-12-11T22:44:11.641Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.green for attribute rgb_color.green in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member green of null [latest-21342]2021-12-11T22:44:11.642Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.blue for attribute rgb_color.blue in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member blue of null [latest-21342]2021-12-11T22:44:11.642Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.cwhite > 0 ? floor( 5500 + value.cwhite * 3500 / 255 ) : floor( 2000 + value.wwhite * 3500 / 255 ) for attribute color_temperature.value in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member cwhite of null [latest-21342]2021-12-11T22:44:11.643Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.red for attribute rgb_color.red in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member red of null [latest-21342]2021-12-11T22:44:11.643Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.green for attribute rgb_color.green in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member green of null [latest-21342]2021-12-11T22:44:11.644Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.blue for attribute rgb_color.blue in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member blue of null [latest-21342]2021-12-11T22:44:11.644Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.cwhite > 0 ? floor( 5500 + value.cwhite * 3500 / 255 ) : floor( 2000 + value.wwhite * 3500 / 255 ) for attribute color_temperature.value in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member cwhite of null [latest-21342]2021-12-11T22:44:11.648Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.red for attribute rgb_color.red in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member red of null [latest-21342]2021-12-11T22:44:11.649Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.green for attribute rgb_color.green in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member green of null [latest-21342]2021-12-11T22:44:11.649Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.blue for attribute rgb_color.blue in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member blue of null [latest-21342]2021-12-11T22:44:11.649Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.cwhite > 0 ? floor( 5500 + value.cwhite * 3500 / 255 ) : floor( 2000 + value.wwhite * 3500 / 255 ) for attribute color_temperature.value in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member cwhite of null [latest-21342]2021-12-11T22:44:11.651Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.red for attribute rgb_color.red in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member red of null [latest-21342]2021-12-11T22:44:11.651Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.green for attribute rgb_color.green in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member green of null [latest-21342]2021-12-11T22:44:11.651Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.blue for attribute rgb_color.blue in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member blue of null [latest-21342]2021-12-11T22:44:11.651Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.cwhite > 0 ? floor( 5500 + value.cwhite * 3500 / 255 ) : floor( 2000 + value.wwhite * 3500 / 255 ) for attribute color_temperature.value in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member cwhite of null [latest-21342]2021-12-11T22:44:11.657Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.red for attribute rgb_color.red in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member red of null [latest-21342]2021-12-11T22:44:11.657Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.green for attribute rgb_color.green in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member green of null [latest-21342]2021-12-11T22:44:11.658Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.blue for attribute rgb_color.blue in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member blue of null [latest-21342]2021-12-11T22:44:11.658Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.cwhite > 0 ? floor( 5500 + value.cwhite * 3500 / 255 ) : floor( 2000 + value.wwhite * 3500 / 255 ) for attribute color_temperature.value in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member cwhite of null [latest-21342]2021-12-11T22:44:11.659Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.red for attribute rgb_color.red in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member red of null [latest-21342]2021-12-11T22:44:11.660Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.green for attribute rgb_color.green in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member green of null [latest-21342]2021-12-11T22:44:11.660Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.blue for attribute rgb_color.blue in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member blue of null [latest-21342]2021-12-11T22:44:11.660Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.cwhite > 0 ? floor( 5500 + value.cwhite * 3500 / 255 ) : floor( 2000 + value.wwhite * 3500 / 255 ) for attribute color_temperature.value in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member cwhite of null [latest-21342]2021-12-11T22:44:11.663Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.red for attribute rgb_color.red in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member red of null [latest-21342]2021-12-11T22:44:11.663Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.green for attribute rgb_color.green in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member green of null [latest-21342]2021-12-11T22:44:11.663Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.blue for attribute rgb_color.blue in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member blue of null [latest-21342]2021-12-11T22:44:11.664Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.cwhite > 0 ? floor( 5500 + value.cwhite * 3500 / 255 ) : floor( 2000 + value.wwhite * 3500 / 255 ) for attribute color_temperature.value in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member cwhite of null [latest-21342]2021-12-11T22:44:11.665Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.red for attribute rgb_color.red in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member red of null [latest-21342]2021-12-11T22:44:11.666Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.green for attribute rgb_color.green in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member green of null [latest-21342]2021-12-11T22:44:11.666Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.blue for attribute rgb_color.blue in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member blue of null [latest-21342]2021-12-11T22:44:11.666Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.cwhite > 0 ? floor( 5500 + value.cwhite * 3500 / 255 ) : floor( 2000 + value.wwhite * 3500 / 255 ) for attribute color_temperature.value in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member cwhite of null [latest-21342]2021-12-11T22:44:11.667Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.red for attribute rgb_color.red in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member red of null [latest-21342]2021-12-11T22:44:11.668Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.green for attribute rgb_color.green in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member green of null [latest-21342]2021-12-11T22:44:11.668Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.blue for attribute rgb_color.blue in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member blue of null [latest-21342]2021-12-11T22:44:11.669Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.cwhite > 0 ? floor( 5500 + value.cwhite * 3500 / 255 ) : floor( 2000 + value.wwhite * 3500 / 255 ) for attribute color_temperature.value in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member cwhite of null [latest-21342]2021-12-11T22:44:11.670Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.red for attribute rgb_color.red in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member red of null [latest-21342]2021-12-11T22:44:11.670Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.green for attribute rgb_color.green in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member green of null [latest-21342]2021-12-11T22:44:11.671Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.blue for attribute rgb_color.blue in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member blue of null [latest-21342]2021-12-11T22:44:11.671Z <EzloController:ERR> EzloController#ezlo failed to evaluate expression value.cwhite > 0 ? floor( 5500 + value.cwhite * 3500 / 255 ) : floor( 2000 + value.wwhite * 3500 / 255 ) for attribute color_temperature.value in category=dimmable_light;subcategory=dimmable_colored: ReferenceError: Invalid reference to member cwhite of null [latest-21342]2021-12-11T22:44:11.693Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=door_lock cap keypad [latest-21342]2021-12-11T22:44:11.727Z <EzloController:INFO> EzloController#ezlo hub inventory complete/successful; 971ms [latest-21342]2021-12-11T22:44:11.728Z <EzloController:NOTICE> Controller EzloController#ezlo is now online. [latest-21342]2021-12-11T22:44:11.730Z <DynamicGroupController:ERR> DynamicGroupController#groups selector criterion invalid type, expecting object, got string (battery_power) [latest-21342]2021-12-11T22:44:11.731Z <DynamicGroupController:ERR> DynamicGroupController#groups error in selection for Group#groups>low_battery: Error: Invalid selector [latest-21342]2021-12-11T22:44:11.731Z <DynamicGroupController:CRIT> Error: Invalid selector Error: Invalid selector at DynamicGroupController._select (/opt/reactor/server/lib/DynamicGroupController.js:314:23) at DynamicGroupController._update_group (/opt/reactor/server/lib/DynamicGroupController.js:219:44) at /opt/reactor/server/lib/DynamicGroupController.js:298:38 at Array.forEach (<anonymous>) at DynamicGroupController._update (/opt/reactor/server/lib/DynamicGroupController.js:295:82) at /opt/reactor/server/lib/DynamicGroupController.js:174:42 at processTicksAndRejections (node:internal/process/task_queues:96:5) [latest-21342]2021-12-11T22:44:11.732Z <app:NOTICE> Starting HTTP server and API... [latest-21342]2021-12-11T22:44:11.737Z <app:NOTICE> Starting Reaction Engine... [latest-21342]2021-12-11T22:44:11.737Z <Engine:INFO> Reaction Engine starting [latest-21342]2021-12-11T22:44:11.738Z <Engine:INFO> Checking rule sets... [latest-21342]2021-12-11T22:44:11.747Z <Engine:INFO> Checking rules... [latest-21342]2021-12-11T22:44:11.748Z <Engine:INFO> Data check complete; no corrections. -
Well, we're looking for InfluxDB messages at the moment. Anything?
-
About InfluxDb I don't see any warn at startup
[latest-21342]2021-12-11T23:21:26.561Z <app:null> Reactor latest-21342-ead7ca9 starting on v16.11.1 [latest-21342]2021-12-11T23:21:26.562Z <app:INFO> Process ID 1; platform linux/x64 #42218 SMP Mon Oct 18 19:16:55 CST 2021; locale (undefined) [latest-21342]2021-12-11T23:21:26.563Z <app:INFO> Basedir /opt/reactor; data in /var/reactor/storage [latest-21342]2021-12-11T23:21:26.563Z <app:INFO> NODE_PATH=/opt/reactor [latest-21342]2021-12-11T23:21:26.566Z <app:INFO> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-21342]2021-12-11T23:21:26.588Z <app:INFO> Loaded locale en-US [latest-21342]2021-12-11T23:21:26.597Z <Capabilities:null> Module Capabilities v21333 [latest-21342]2021-12-11T23:21:26.639Z <Plugin:null> Module Plugin v21186 [latest-21342]2021-12-11T23:21:26.644Z <TimerBroker:null> Module TimerBroker v21333 [latest-21342]2021-12-11T23:21:26.646Z <default:INFO> Module Entity v21334 [latest-21342]2021-12-11T23:21:26.650Z <Controller:null> Module Controller v21333 [latest-21342]2021-12-11T23:21:26.650Z <default:null> Module Structure v21338 [latest-21342]2021-12-11T23:21:26.658Z <default:null> Module Ruleset v21096 [latest-21342]2021-12-11T23:21:26.659Z <default:null> Module Rulesets v21096 [latest-21342]2021-12-11T23:21:26.667Z <GlobalExpression:null> Module GlobalExpression v21333 [latest-21342]2021-12-11T23:21:26.679Z <default:null> Module Rule v21337 [latest-21342]2021-12-11T23:21:26.683Z <GlobalReaction:null> Module GlobalReaction v21333 [latest-21342]2021-12-11T23:21:26.684Z <AlertManager:null> Module AlertManager v21333 [latest-21342]2021-12-11T23:21:26.685Z <default:null> Module Engine v21342 [latest-21342]2021-12-11T23:21:26.685Z <default:null> Module httpapi v21333 [latest-21342]2021-12-11T23:21:26.687Z <default:null> Module httpproxy v21333 [latest-21342]2021-12-11T23:21:26.702Z <default:null> Module wsapi v21334 [latest-21342]2021-12-11T23:21:26.703Z <app:NOTICE> Starting Structure... [latest-21342]2021-12-11T23:21:26.740Z <InfluxFeed:null> Module InfluxFeed v21333 [latest-21342]2021-12-11T23:21:26.742Z <Structure:INFO> Structure#1 starting plugin influx (InfluxFeed) [latest-21342]2021-12-11T23:21:26.743Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController) [latest-21342]2021-12-11T23:21:26.752Z <VeraController:null> Module VeraController v21334 [latest-21342]2021-12-11T23:21:26.757Z <Structure:INFO> Structure#1 loading controller interface ezlo (EzloController) [latest-21342]2021-12-11T23:21:26.769Z <EzloController:null> Module EzloController v21324 [latest-21342]2021-12-11T23:21:26.772Z <EzloController:null> EzloController#ezlo created, config { "source": "wss://10.0.4.119:17000", "serial": "90000464" } [latest-21342]2021-12-11T23:21:26.772Z <EzloController:null> EzloController#ezlo instance log level (null) (4) [latest-21342]2021-12-11T23:21:26.773Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-21342]2021-12-11T23:21:26.777Z <DynamicGroupController:null> Module DynamicGroupController v21334 [latest-21342]2021-12-11T23:21:26.779Z <Structure:INFO> Structure#1 loading controller interface weather (OWMWeatherController) [latest-21342]2021-12-11T23:21:26.783Z <OWMWeatherController:null> Module OWMWeatherController v21313 [latest-21342]2021-12-11T23:21:26.785Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-21342]2021-12-11T23:21:26.788Z <SystemController:null> Module SystemController v21342 [latest-21342]2021-12-11T23:21:26.790Z <Structure:INFO> Starting controller VeraController#vera [latest-21342]2021-12-11T23:21:26.790Z <VeraController:NOTICE> VeraController#vera starting [latest-21342]2021-12-11T23:21:26.835Z <VeraController:INFO> VeraController#vera loaded mapping ver 21301 rev 1 format 1 notice [latest-21342]2021-12-11T23:21:26.837Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members [latest-21342]2021-12-11T23:21:26.837Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty [latest-21342]2021-12-11T23:21:26.838Z <VeraController:INFO> VeraController: deviceclass vera_system_object capability sys_system does not provide attribute state [latest-21342]2021-12-11T23:21:26.850Z <Structure:INFO> Starting controller EzloController#ezlo [latest-21342]2021-12-11T23:21:26.863Z <EzloController:INFO> EzloController#ezlo device mapping data loaded; checking... [latest-21342]2021-12-11T23:21:26.866Z <EzloController:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled) [latest-21342]2021-12-11T23:21:26.867Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-21342]2021-12-11T23:21:26.869Z <DynamicGroupController:NOTICE> Controller DynamicGroupController#groups is now online. [latest-21342]2021-12-11T23:21:26.870Z <Structure:INFO> Starting controller OWMWeatherController#weather [latest-21342]2021-12-11T23:21:26.896Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-21342]2021-12-11T23:21:26.897Z <SystemController:NOTICE> Controller SystemController#reactor_system is now online. [latest-21342]2021-12-11T23:21:26.921Z <EzloController:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000 [latest-21342]2021-12-11T23:21:26.922Z <EzloController:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000 [latest-21342]2021-12-11T23:21:26.928Z <app:INFO> Structure running; pausing for controllers' initial ready [latest-21342]2021-12-11T23:21:27.062Z <EzloController:INFO> EzloController#ezlo hub websocket connected (wss://10.0.4.119:17000) [latest-21342]2021-12-11T23:21:27.062Z <EzloController:INFO> EzloController#ezlo hub websocket connected; inventory hub... [latest-21342]2021-12-11T23:21:27.114Z <EzloController:INFO> EzloController#ezlo hub "90000464" is h2.1 (undefined) firmware "2.0.21.1785.1" [latest-21342]2021-12-11T23:21:27.151Z <OWMWeatherController:INFO> OWMWeatherController#weather done; 1 locations, 0 failed [latest-21342]2021-12-11T23:21:27.152Z <OWMWeatherController:NOTICE> Controller OWMWeatherController#weather is now online. [latest-21342]2021-12-11T23:21:27.396Z <VeraController:NOTICE> Controller VeraController#vera is now online. -
OK. Thanks for uploading the logs and data. It looks like I made an error in the parsing of attribute lists. But, I think there's an easy workaround for you until I get a fix out... just change
select_capabilitiestodefault_capabilities. No other changes needed, I think. -
Thanks to you!
The fix is working.
Now I can truck energy consuption on Influxdb. The idea is to try to make in MSR what in HA is doing with utility_meter, Trend and Lovelace UI togheter. Maybe in future we will see a standard MSR energy plugin too.
-
T toggledbits locked this topic on
Utility Meter
