Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down.
I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor).
My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long
I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
https://github.com/dbochicchio/reactor-mqtt-contrib
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me.
While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users.
I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do.
Just an idea
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically.
That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button.
Example: Light 1 ON → OFF, then Light 2 ON → OFF.
The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule.
Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Use case:
When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled.
To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work.
Then another situation: the water pump system and garden irrigation, another switch.
In short, I had to create several virtual switches in Hubitat to disable rules in MSR.
Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR.
If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR.
Would it be possible to do something like this? Any recommendations from the experts?
Probably a really dumb question.
Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great.
Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly.
Any thoughts?
Apologies if the ask is not clear/
TIA
C
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well.
As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API.
Updates: (the latest versions first in the list)
OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
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 foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page.
Once logged back in I can no longer remove errant panes nor is the + available to add new ones.
Brave Browser v1.80.122 (Jul 16, 2025)
What have I done?!
Will check other browsers on my M1.
UPDATE: Safari exhibits same behaviour.
I've tried both sans last-four public key entry and with - no change.
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of.
Thanks.
Plugin InfluxFeed - Selecting Capabilities for Export - how to
-
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
