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 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?
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.
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.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
@toggledbits In the MSR documentation, under Standard Capabilities, I noticed that the
button.since attribute was deprecated as of version 22256 and the metadata is the preferred way to access the last-modified time of an attribute.
Am I reading this right? Should I stop using it in my rules?
Thanks
When on my bare metal RPi with MSR I had a rule that ran every minute to check Internet status via a script in MSR called reactor_inet_check.sh
I've moved to containerized MSR and see in the instructions that this cannot be run from the container.
The script cannot run within the Reactor docker container. If you are using Reactor in a docker container, the script needs to be run by cron or an equivalent facility on the host system (e.g. some systems, like Synology NAS, have separate task managers that may be used to schedule the repeated execution of tasks such as this).
I've put a script on my container host that calls the reator_inet_check.sh script and it isn't erroring... but I still see the internet status within MSR as null.
Before I go diving down the rabbit hole... should this work?
My cronjob on the proxmox host:
909fe6f0-77fd-4734-80a4-c9e354c910b6-image.png
The contents of msr_internet_check_caller.sh
16337528-cf31-4968-bffe-af1149f7103e-image.png
Background: this is a Windows MSR install I've done for our local pool/amenity center just to run some fans and lights (not my daily driver at home). Install went perfectly fine.
Scenario: I want the lights to go on when it's dark enough (even if during a storm, not just after sunset) so I'm using solarRadiation from my weather station to drive that Trigger. Easy stuff.
Issue: sometimes, someone goes in the office and just starts flipping switches and the result can be lights turned on in the daytime or off at night. I'm trying to create a "catch-all" wherein if it is daytime and the lights somehow find their way ON, they will turn themselves back OFF.
I have the following Reaction built:
b30eab5b-5a14-4a3a-8c9a-47e3e7e53dc3-image.png
I also have this Reaction for opposite, ie the lights find themselves turned off after dark and they will turn themselves back on:
5c6946b1-297c-4eb1-9618-74820979df29-image.png
Here are my two rules:
288cba86-f941-4157-86d9-d8e7487905f7-image.png *NOTE that in my manual testing, ie I turn on the light switch at the incorrect time, when the solarRadiation level changes the Lights ON rule flags and shows as SET. On the next change of solarRadiation it goes back to reset again.
My expectation is that Lights OFF rule should see the lights are on, the solarRadiation is above the set limit, and turn them off. Instead, every other run, the ON rule moves to SET and then reset again on the following run.
Logs appear angry:
[latest-25016]2025-01-26T22:03:31.696Z <Engine:INFO> Enqueueing "Lights ON<RESET>" (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:03:31.712Z <Engine:NOTICE> Starting reaction Lights ON<RESET> (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:03:31.713Z <Engine:INFO> Lights ON<RESET> all actions completed. [latest-25016]2025-01-26T22:03:42.565Z <wsapi:INFO> client "127.0.0.1#3" closed, code=1001, reason= [latest-25016]2025-01-26T22:03:42.753Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang [latest-25016]2025-01-26T22:03:42.754Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 } [latest-25016]2025-01-26T22:03:42.790Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1 [latest-25016]2025-01-26T22:03:42.839Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#6" authorized [latest-25016]2025-01-26T22:03:43.353Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime [latest-25016]2025-01-26T22:03:43.353Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 } [latest-25016]2025-01-26T22:03:48.146Z <wsapi:INFO> client "127.0.0.1#6" closed, code=1001, reason= [latest-25016]2025-01-26T22:03:48.308Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang [latest-25016]2025-01-26T22:03:48.309Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 } [latest-25016]2025-01-26T22:03:48.346Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1 [latest-25016]2025-01-26T22:03:48.390Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#7" authorized [latest-25016]2025-01-26T22:03:49.412Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime [latest-25016]2025-01-26T22:03:49.413Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 } [latest-25016]2025-01-26T22:03:52.734Z <wsapi:INFO> client "127.0.0.1#7" closed, code=1001, reason= [latest-25016]2025-01-26T22:03:52.891Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang [latest-25016]2025-01-26T22:03:52.892Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 } [latest-25016]2025-01-26T22:03:52.925Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1 [latest-25016]2025-01-26T22:03:52.965Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#8" authorized [latest-25016]2025-01-26T22:03:54.383Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime [latest-25016]2025-01-26T22:03:54.384Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 } [latest-25016]2025-01-26T22:04:01.590Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25016]2025-01-26T22:04:39.646Z <Rule:INFO> Lights OFF (rule-m6e33ja3 in Atrium Lights) evaluated; rule state transition from RESET to SET! [latest-25016]2025-01-26T22:04:39.656Z <Rule:INFO> Lights ON (rule-m6e4ajh7 in Atrium Lights) evaluated; rule state transition from RESET to SET! [latest-25016]2025-01-26T22:04:39.663Z <Engine:INFO> Enqueueing "Lights OFF<SET>" (rule-m6e33ja3:S) [latest-25016]2025-01-26T22:04:39.665Z <Engine:INFO> Enqueueing "Lights ON<SET>" (rule-m6e4ajh7:S) [latest-25016]2025-01-26T22:04:39.668Z <Engine:NOTICE> Starting reaction Lights OFF<SET> (rule-m6e33ja3:S) [latest-25016]2025-01-26T22:04:39.669Z <Engine:NOTICE> Starting reaction Lights ON<SET> (rule-m6e4ajh7:S) [latest-25016]2025-01-26T22:04:39.669Z <Engine:INFO> Lights ON<SET> all actions completed. [latest-25016]2025-01-26T22:04:39.675Z <Rule:INFO> Lights OFF (rule-m6e33ja3 in Atrium Lights) evaluated; rule state transition from SET to RESET! [latest-25016]2025-01-26T22:04:39.680Z <Engine:NOTICE> ReactionHistory: no entry for [latest-25016]2025-01-26T22:04:39.683Z <Engine:NOTICE> [Engine]Engine#1 entry 256 reaction rule-m6e33ja3:S-1q2f1j0p: [Error] terminated [parent terminating] [latest-25016]2025-01-26T22:04:39.683Z <Engine:CRIT> Error: terminated [parent terminating] Error: terminated at Engine._process_reaction_queue (C:\Users\Jalan\msr\reactor\server\lib\Engine.js:1644:47) [latest-25016]2025-01-26T22:04:39.699Z <Engine:NOTICE> [Engine]Engine#1 entry 254 reaction rule-m6e33ja3:S: [Error] terminated [preempted by rule state change] [latest-25016]2025-01-26T22:04:39.699Z <Engine:CRIT> Error: terminated [preempted by rule state change] Error: terminated at Engine._process_reaction_queue (C:\Users\Jalan\msr\reactor\server\lib\Engine.js:1644:47) [latest-25016]2025-01-26T22:04:39.700Z <Engine:INFO> Enqueueing "Lights OFF<RESET>" (rule-m6e33ja3:R) [latest-25016]2025-01-26T22:04:39.704Z <Engine:NOTICE> Starting reaction Lights OFF<RESET> (rule-m6e33ja3:R) [latest-25016]2025-01-26T22:04:39.705Z <Engine:INFO> Lights OFF<RESET> all actions completed. [latest-25016]2025-01-26T22:05:48.822Z <Rule:INFO> Lights ON (rule-m6e4ajh7 in Atrium Lights) evaluated; rule state transition from SET to RESET! [latest-25016]2025-01-26T22:05:48.831Z <Engine:INFO> Enqueueing "Lights ON<RESET>" (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:05:48.847Z <Engine:NOTICE> Starting reaction Lights ON<RESET> (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:05:48.847Z <Engine:INFO> Lights ON<RESET> all actions completed.
Hi @toggledbits
I found this very old post that talked about a way to limit device reading to avoid the throttled problem, because it's not a question of logic, it's that the device actually sends a lot of information, in my case the NUT ups installed in HE.
https://smarthome.community/topic/687/flapping-device?_=1737652139854
It mentions engine section of reactor.yaml by setting update_rate_limit, but I looked in the current MSR documentation and I can't find this information, so I don't know if it's still valid, its effect and parameters.
My situation is simple, when I have a UPS problem the NUT is sending dozens of reports per second and then I have the throttled problem. The same rule applies when the power is normal.
This is the rule, and the parameter that fails is the Tripp Lite UPS status.
cf9ddabf-3144-4e5a-80a4-0dc7664b9573-image.png
a813a077-974e-4737-897c-e383085b3d8f-image.png
All error is the same scenario.
[latest-25016]2025-01-23T12:01:32.753Z <Rule:WARN> (13) NUT Disconected (rule-l4djr0p7 in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:32.756Z <Rule:WARN> (27) Falta de Energia (rule-l4h9ceod in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:32.769Z <Rule:WARN> (73) UPS Battery Low (rule-l4hj850o in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:32.772Z <Rule:WARN> (74) UPS Comm Fail (rule-l4kbs5cp in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttlin> [latest-25016]2025-01-23T12:01:32.776Z <Rule:WARN> (76) UPS Utility Back (rule-l4hjhs6m in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:32.780Z <Rule:WARN> UPS On Battery (rule-l4hjuka5 in Datacenter) update rate 121/min exceeds limit (120/min)! Logic loop? Throttling> [latest-25016]2025-01-23T12:01:32.781Z <Rule:WARN> UPS Info (rule-l4gheo63 in Datacenter) update rate 121/min exceeds limit (120/min)! Logic loop? Throttling... [latest-25016]2025-01-23T12:01:40.757Z <Rule:WARN> (13) NUT Disconected (rule-l4djr0p7 in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:40.759Z <Rule:WARN> (27) Falta de Energia (rule-l4h9ceod in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:40.776Z <Rule:WARN> (73) UPS Battery Low (rule-l4hj850o in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:40.777Z <Rule:WARN> (74) UPS Comm Fail (rule-l4kbs5cp in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttlin> [latest-25016]2025-01-23T12:01:40.778Z <Rule:WARN> (76) UPS Utility Back (rule-l4hjhs6m in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott>Thanks.
Hello -
Long time. Hope everyone is good.
I have a rule that looks at a number of temperature sensors around the house. It simply sends a general alert if any of them fall below their threshold. (A basic “House is too cold” alert for when we’re away)
Generally, this has worked well. But I was wondering if there’s a way to make the message somewhat dynamic without creating separate rules for each sensor.
E.g. “House is too cold due to Sump Temperature below 45 degrees.”
I thought I remember reading about someone doing this in the past but couldn’t find it.
Thanks for any ideas!
[Solved] Entities error when updating MQTTController from 24120 to 24142
-
[Solution: Reactor 24115 is not compatible with MQTTController > 24120]
Reactor latest-24115 bare metal.
All MQTT entities stop working after updating MQTTController to 24142, downgrade to 24120 and they are back. Templates and configured entities has not been changed between versions.
I'm not sure ifuses_templateshould be replaced byìncludein entity configuration in reactor.yaml but I guess not, I've tried it and it did not do any difference.
I have not tried to update Reactor to userauth version.Example entity in reactor.yaml that uses MQTTController included template:
entities: "takflakt_kallare": name: "Takfläkt källare" topic: "Källartemp" unit: "" uses_template: tasmota_generic_relay init: "cmnd/%topic%/POWER%unit%"Any hints? Do you need more info, please let me know.
Log from startup:[latest-24115]2024-05-28T14:42:35.995Z <app:null> Reactor build latest-24115-55b591da starting on v20.13.1 [latest-24115]2024-05-28T14:42:35.996Z <app:null> Process ID 38403 user/group 1000/1000; bare-metal; platform linux/x64 #117-Ubuntu SMP Fri Apr 26 12:26:49 UTC 2024; locale sv_SE.utf8 [latest-24115]2024-05-28T14:42:35.996Z <app:null> Basedir /home/homebridge/reactor; data in /home/homebridge/reactor/storage [latest-24115]2024-05-28T14:42:35.996Z <app:null> NODE_PATH=/home/homebridge/reactor [latest-24115]2024-05-28T14:42:36.010Z <app:null> Resolved timezone=Europe/Stockholm, environment TZ=(undefined); offset minutes from UTC=120 [latest-24115]2024-05-28T14:42:36.012Z <app:null> Configured locale sv-SE; selected locale(s) sv-SE [latest-24115]2024-05-28T14:42:36.018Z <app:null> Loaded locale sv-SE for sv-SE [latest-24115]2024-05-28T14:42:36.018Z <app:null> Local date/time using configured timezone and locale formatting is "2024-05-28 16:42:36" [latest-24115]2024-05-28T14:42:36.020Z <Structure:null> Module Structure v24099 [latest-24115]2024-05-28T14:42:36.021Z <Capabilities:null> Module Capabilities v23331 [latest-24115]2024-05-28T14:42:36.028Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 24108 revision 1 [latest-24115]2024-05-28T14:42:36.035Z <Plugin:null> Module Plugin v22300 [latest-24115]2024-05-28T14:42:36.038Z <TimerBroker:null> Module TimerBroker v22283 [latest-24115]2024-05-28T14:42:36.039Z <Entity:null> Module Entity v24108 [latest-24115]2024-05-28T14:42:36.041Z <Controller:null> Module Controller v24099 [latest-24115]2024-05-28T14:42:36.047Z <default:null> Module Ruleset v24099 [latest-24115]2024-05-28T14:42:36.047Z <default:null> Module Rulesets v24099 [latest-24115]2024-05-28T14:42:36.050Z <GlobalExpression:null> Module GlobalExpression v24099 [latest-24115]2024-05-28T14:42:36.056Z <Predicate:null> Module Predicate v23093 [latest-24115]2024-05-28T14:42:36.058Z <AlertManager:null> Module AlertManager v24099 [latest-24115]2024-05-28T14:42:36.060Z <Rule:null> Module Rule v24115 [latest-24115]2024-05-28T14:42:36.061Z <GlobalReaction:null> Module GlobalReaction v24099 [latest-24115]2024-05-28T14:42:36.062Z <Engine:null> Module Engine v24099 [latest-24115]2024-05-28T14:42:36.064Z <httpapi:null> Module httpapi v24099 [latest-24115]2024-05-28T14:42:36.072Z <wsapi:null> Module wsapi v24115 [latest-24115]2024-05-28T14:42:36.072Z <app:NOTICE> Starting Structure... [latest-24115]2024-05-28T14:42:36.075Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController) [latest-24115]2024-05-28T14:42:36.092Z <TaskQueue:null> Module TaskQueue 21351 [latest-24115]2024-05-28T14:42:36.093Z <VeraController:null> Module VeraController v24050 [latest-24115]2024-05-28T14:42:36.144Z <Structure:INFO> Structure#1 loading controller interface ezlo (EzloController) [latest-24115]2024-05-28T14:42:36.150Z <EzloController:null> Module EzloController v23345 [latest-24115]2024-05-28T14:42:36.153Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-24115]2024-05-28T14:42:36.155Z <DynamicGroupController:null> Module DynamicGroupController v22313 [latest-24115]2024-05-28T14:42:36.159Z <Structure:INFO> Structure#1 loading controller interface virtual (VirtualEntityController) [latest-24115]2024-05-28T14:42:36.162Z <VirtualEntityController:null> Module VirtualEntityController v24076 [latest-24115]2024-05-28T14:42:36.164Z <Structure:INFO> Structure#1 loading controller interface hass (HassController) [latest-24115]2024-05-28T14:42:36.168Z <HassController:null> Module HassController v24115 [latest-24115]2024-05-28T14:42:36.217Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-24115]2024-05-28T14:42:36.218Z <SystemController:null> Module SystemController v24076 [latest-24115]2024-05-28T14:42:36.220Z <Structure:INFO> Structure#1 loading controller interface mosquitto-mqtt (MQTTController) [latest-24115]2024-05-28T14:42:36.223Z <MQTTController:null> Module MQTTController v24144 [latest-24115]2024-05-28T14:42:36.252Z <Controller:INFO> Loaded MQTTController version "0.2.24144"; Patrick Rigney/Kedron Holdings LLC <patrick@toggledbits.com> https://reactor.toggledbits.com/docs/MQTTController/ [latest-24115]2024-05-28T14:42:36.263Z <Structure:INFO> Structure#1 loading controller interface mqtt (MQTTController) [latest-24115]2024-05-28T14:42:36.263Z <Controller:INFO> Loaded MQTTController version "0.2.24144"; Patrick Rigney/Kedron Holdings LLC <patrick@toggledbits.com> https://reactor.toggledbits.com/docs/MQTTController/ [latest-24115]2024-05-28T14:42:36.267Z <Structure:INFO> Starting controller VeraController#vera [latest-24115]2024-05-28T14:42:36.268Z <VeraController:NOTICE> VeraController#vera starting... [latest-24115]2024-05-28T14:42:36.270Z <Controller:INFO> VeraController#vera loaded vera capabilities ver 22253 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.283Z <Controller:INFO> VeraController#vera loaded implementation data ver 23109 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.283Z <Structure:INFO> Starting controller EzloController#ezlo [latest-24115]2024-05-28T14:42:36.284Z <Controller:INFO> EzloController#ezlo loaded ezlo capabilities ver 22266 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.288Z <Controller:INFO> EzloController#ezlo loaded implementation data ver 22344 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.288Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-24115]2024-05-28T14:42:36.290Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online. [latest-24115]2024-05-28T14:42:36.290Z <Structure:INFO> Starting controller VirtualEntityController#virtual [latest-24115]2024-05-28T14:42:36.291Z <Controller:INFO> VirtualEntityController#virtual loaded virtualentity capabilities ver 22263 rev 2 format 1 [latest-24115]2024-05-28T14:42:36.291Z <Controller:INFO> VirtualEntityController#virtual loaded implementation data ver 22280 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.291Z <Structure:INFO> Starting controller HassController#hass [latest-24115]2024-05-28T14:42:36.291Z <HassController:NOTICE> HassController#hass starting... [latest-24115]2024-05-28T14:42:36.292Z <Controller:INFO> HassController#hass loaded hass capabilities ver 23289 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.295Z <Controller:INFO> HassController#hass loaded implementation data ver 24004 rev 3 format 1 [latest-24115]2024-05-28T14:42:36.295Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-24115]2024-05-28T14:42:36.296Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. [latest-24115]2024-05-28T14:42:36.337Z <Structure:INFO> Starting controller MQTTController#mosquitto-mqtt [latest-24115]2024-05-28T14:42:36.338Z <Controller:INFO> MQTTController#mosquitto-mqtt loaded mqtt capabilities ver 22353 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.338Z <Controller:INFO> MQTTController#mosquitto-mqtt loaded implementation data ver 24122 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.338Z <Structure:INFO> Starting controller MQTTController#mqtt [latest-24115]2024-05-28T14:42:36.338Z <MQTTController:WARN> mqtt_capabilities redefines existing x_mqtt [latest-24115]2024-05-28T14:42:36.338Z <MQTTController:WARN> mqtt_capabilities redefines existing x_mqtt_device [latest-24115]2024-05-28T14:42:36.338Z <Capabilities:INFO> [Capabilities][object Object] overriding capability x_mqtt [latest-24115]2024-05-28T14:42:36.339Z <Capabilities:INFO> [Capabilities][object Object] overriding capability x_mqtt_device [latest-24115]2024-05-28T14:42:36.339Z <Controller:INFO> MQTTController#mqtt loaded mqtt capabilities ver 22353 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.339Z <Controller:INFO> MQTTController#mqtt loaded implementation data ver 24122 rev 1 format 1 [latest-24115]2024-05-28T14:42:36.341Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members [latest-24115]2024-05-28T14:42:36.341Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty [latest-24115]2024-05-28T14:42:36.342Z <EzloController:INFO> EzloController#ezlo device mapping data loaded; checking... [latest-24115]2024-05-28T14:42:36.342Z <EzloController:WARN> EzloController: implementation of capability battery_maintenance does not provide attribute state [latest-24115]2024-05-28T14:42:36.343Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [latest-24115]2024-05-28T14:42:36.343Z <HassController:WARN> HassController: implementation of capability light_effect does not provide attribute speed [latest-24115]2024-05-28T14:42:36.344Z <HassController:WARN> HassController: implementation of capability battery_maintenance does not provide attribute state [latest-24115]2024-05-28T14:42:36.344Z <HassController:WARN> HassController: implementation of capability input_select.selector does not provide attribute values [latest-24115]2024-05-28T14:42:36.355Z <EzloController:INFO> EzloController#ezlo: connecting to hub "xxxxxxxx" via anonymous local connection to wss://xxx.xxx.xxx.xxx [latest-24115]2024-05-28T14:42:36.358Z <VirtualEntityController:INFO> VirtualEntityController#virtual configuring virtual Dyr El (dyrEl) [latest-24115]2024-05-28T14:42:36.365Z <VirtualEntityController:INFO> VirtualEntityController#virtual configuring virtual Solar Production Forecast (solar_production_forecast) [latest-24115]2024-05-28T14:42:36.369Z <Controller:INFO> VirtualEntityController#virtual 0 dead entities older than 86400000s purged [latest-24115]2024-05-28T14:42:36.369Z <HassController:NOTICE> HassController#hass connecting to ws://xxx.xxx.xxx.xxx/api/websocket [latest-24115]2024-05-28T14:42:36.371Z <MQTTController:WARN> MQTTController#mqtt file my_tasmota_generic_relay.yaml in /home/homebridge/reactor/config/mqtt_templates/my_tasmota_generic_relay.yaml overrides existing template definition my _tasmota_generic_relay [latest-24115]2024-05-28T14:42:36.372Z <MQTTController:WARN> MQTTController#mqtt file shelly_plug_s.yaml in /home/homebridge/reactor/config/mqtt_templates/shelly_plug_s.yaml overrides existing template definition shelly_plug_s [latest-24115]2024-05-28T14:42:36.372Z <MQTTController:WARN> MQTTController#mqtt file tasmota_sensor_lyw.yaml in /home/homebridge/reactor/config/mqtt_templates/tasmota_sensor_lyw.yaml overrides existing template definition tasmota_sensor _lyw [latest-24115]2024-05-28T14:42:36.372Z <MQTTController:WARN> MQTTController#mqtt file wallbox_pulsar_plus.yaml in /home/homebridge/reactor/config/mqtt_templates/wallbox_pulsar_plus.yaml overrides existing template definition wallbox_puls ar_plus [latest-24115]2024-05-28T14:42:36.372Z <MQTTController:WARN> MQTTController#mqtt file xiaofang_motion_light_sensor.yaml in /home/homebridge/reactor/config/mqtt_templates/xiaofang_motion_light_sensor.yaml overrides existing template defin ition xiaofang_motion_light_sensor [latest-24115]2024-05-28T14:42:36.374Z <Controller:NOTICE> Controller VirtualEntityController#virtual is now online. [latest-24115]2024-05-28T14:42:36.394Z <HassController:NOTICE> HassController#hass connected, starting protocol [latest-24115]2024-05-28T14:42:36.396Z <HassController:INFO> HassController#hass successful authentication with ws://xxx.xxx.xxx.xxx; fetching initial data... [latest-24115]2024-05-28T14:42:36.400Z <HassController:INFO> HassController#hass Hass reports version "2024.5.5" location Hem timezone Europe/Stockholm state RUNNING safe_mode false [latest-24115]2024-05-28T14:42:36.402Z <HassController:ERR> HassController#hass reported Hass version "2024.5.5" is not supported! [latest-24115]2024-05-28T14:42:36.403Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_control_outlet.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_trad fri.zip/zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_control_outlet.yaml overrides existing template definition zigbee2mqtt_tradfri_control_outlet [latest-24115]2024-05-28T14:42:36.405Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradfri. zip/zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb [latest-24115]2024-05-28T14:42:36.405Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradfri. zip/zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb_d [latest-24115]2024-05-28T14:42:36.416Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_supervisor_update [latest-24115]2024-05-28T14:42:36.417Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_core_update [latest-24115]2024-05-28T14:42:36.417Z <HassController:NOTICE> HassController#hass no signature match for update.terminal_ssh_update [latest-24115]2024-05-28T14:42:36.417Z <HassController:NOTICE> HassController#hass no signature match for update.esphome_update [latest-24115]2024-05-28T14:42:36.417Z <HassController:NOTICE> HassController#hass no signature match for update.file_editor_update [latest-24115]2024-05-28T14:42:36.418Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_operating_system_update [latest-24115]2024-05-28T14:42:36.418Z <HassController:NOTICE> HassController#hass no signature match for sun.sun [latest-24115]2024-05-28T14:42:36.420Z <HassController:NOTICE> HassController#hass no signature match for conversation.home_assistant [latest-24115]2024-05-28T14:42:36.420Z <HassController:NOTICE> HassController#hass no signature match for remote.samsung_vardagsrummet [latest-24115]2024-05-28T14:42:36.457Z <HassController:NOTICE> HassController#hass no signature match for update.infopanel_hall_firmware [latest-24115]2024-05-28T14:42:36.465Z <Controller:INFO> HassController#hass 0 dead entities older than 86400000s purged [latest-24115]2024-05-28T14:42:36.466Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradf ri.zip/zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb_ws [latest-24115]2024-05-28T14:42:36.466Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_ikea_tradf ri.zip/zigbee2mqtt_ikea_tradfri/zigbee2mqtt_ikea_tradfri_light_bulb_ws.yaml overrides existing template definition zigbee2mqtt_tradfri_light_bulb_ws_d [latest-24115]2024-05-28T14:42:36.466Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_tuya_door_sensor.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_door_sensor.yaml overrides existing temp late definition zigbee2mqtt_tuya_door_sensor [latest-24115]2024-05-28T14:42:36.467Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_tuya_light_bulb_rgbcw.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_light_bulb_rgbcw.yaml overrides exi sting template definition zigbee2mqtt_tuya_light_bulb_rgbcw [latest-24115]2024-05-28T14:42:36.467Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_tuya_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_occupancy_illuminance.yaml ove rrides existing template definition zigbee2mqtt_tuya_motion_light_sensor [latest-24115]2024-05-28T14:42:36.467Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_tuya_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_occupancy_illuminance.yaml ove rrides existing template definition zigbee2mqtt_tuya_light_motion_sensor [latest-24115]2024-05-28T14:42:36.467Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_tuya_smart_plug_pm.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_tuya_smart_plug_pm.yaml overrides existing template definition zigbee2mqtt_tuya_smart_plug_pm [latest-24115]2024-05-28T14:42:36.528Z <Controller:INFO> VeraController#vera 0 dead entities older than 86400000s purged [latest-24115]2024-05-28T14:42:36.529Z <Controller:NOTICE> Controller VeraController#vera is now online. [latest-24115]2024-05-28T14:42:36.531Z <Controller:NOTICE> Controller HassController#hass is now online. [latest-24115]2024-05-28T14:42:36.533Z <EzloController:INFO> EzloController#ezlo: successful unauthenticated local connection to "xxxxxxx" [latest-24115]2024-05-28T14:42:36.534Z <EzloController:INFO> EzloController#ezlo starting hub inventory [latest-24115]2024-05-28T14:42:36.535Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_xiaomi_aqara_mini_switch.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqtt_xiaomi_a qara_mini_switch.yaml overrides existing template definition zigbee2mqtt_aqara_mini_switch [latest-24115]2024-05-28T14:42:36.537Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_xiaomi_aqara_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqt t_xiaomi_aqara_occupancy_illuminance.yaml overrides existing template definition zigbee2mqtt_aqara_motion_light_sensor [latest-24115]2024-05-28T14:42:36.537Z <MQTTController:WARN> MQTTController#mosquitto-mqtt file zigbee2mqtt_xiaomi_aqara_occupancy_illuminance.yaml in /home/homebridge/reactor/config/mqtt_templates/zigbee2mqtt_xiaomi_aqara.zip/zigbee2mqt t_xiaomi_aqara_occupancy_illuminance.yaml overrides existing template definition zigbee2mqtt_aqara_light_motion_sensor [latest-24115]2024-05-28T14:42:36.538Z <MQTTController:INFO> MQTTController#mqtt instance topic ident is mqtt [latest-24115]2024-05-28T14:42:36.540Z <MQTTController:ERR> MQTTController#mqtt error initializing entity takflakt_kallare: [TypeError] Cannot read properties of undefined (reading 'length') [-] [latest-24115]2024-05-28T14:42:36.540Z <MQTTController:CRIT> TypeError: Cannot read properties of undefined (reading 'length') [-] TypeError: Cannot read properties of undefined (reading 'length') at MQTTController.start (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:250:30) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.allSettled (index 7) [latest-24115]2024-05-28T14:42:36.541Z <MQTTController:ERR> MQTTController#mqtt error initializing entity kaminflakt: [TypeError] Cannot read properties of undefined (reading 'length') [-] [latest-24115]2024-05-28T14:42:36.541Z <MQTTController:CRIT> TypeError: Cannot read properties of undefined (reading 'length') [-] TypeError: Cannot read properties of undefined (reading 'length') at MQTTController.start (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:250:30) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.allSettled (index 7) [latest-24115]2024-05-28T14:42:36.542Z <MQTTController:ERR> MQTTController#mqtt error initializing entity kallartemp: [TypeError] Cannot read properties of undefined (reading 'length') [-] [latest-24115]2024-05-28T14:42:36.542Z <MQTTController:CRIT> TypeError: Cannot read properties of undefined (reading 'length') [-] TypeError: Cannot read properties of undefined (reading 'length') at MQTTController.start (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:250:30) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.allSettled (index 7) [latest-24115]2024-05-28T14:42:36.543Z <MQTTController:ERR> MQTTController#mqtt error initializing entity fasadvedbod: [TypeError] Cannot read properties of undefined (reading 'length') [-] [latest-24115]2024-05-28T14:42:36.543Z <MQTTController:CRIT> TypeError: Cannot read properties of undefined (reading 'length') [-] TypeError: Cannot read properties of undefined (reading 'length') at MQTTController.start (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:250:30) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.allSettled (index 7) [latest-24115]2024-05-28T14:42:36.544Z <MQTTController:ERR> MQTTController#mqtt error initializing entity fasadgarage: [TypeError] Cannot read properties of undefined (reading 'length') [-] [latest-24115]2024-05-28T14:42:36.544Z <MQTTController:CRIT> TypeError: Cannot read properties of undefined (reading 'length') [-] TypeError: Cannot read properties of undefined (reading 'length') at MQTTController.start (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:250:30) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.allSettled (index 7) [latest-24115]2024-05-28T14:42:36.545Z <MQTTController:ERR> MQTTController#mqtt error initializing entity draneringspump: [TypeError] Cannot read properties of undefined (reading 'length') [-] [latest-24115]2024-05-28T14:42:36.545Z <MQTTController:CRIT> TypeError: Cannot read properties of undefined (reading 'length') [-] TypeError: Cannot read properties of undefined (reading 'length') at MQTTController.start (/home/homebridge/reactor/config/ext/MQTTController/MQTTController.js:250:30) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.allSettled (index 7) ... "same error for all configured MQTT entities" ... [latest-24115]2024-05-28T14:42:36.642Z <Controller:INFO> MQTTController#mosquitto-mqtt 0 dead entities older than 86400000s purged [latest-24115]2024-05-28T14:42:36.642Z <MQTTController:NOTICE> MQTTController#mosquitto-mqtt connecting to broker at mqtt://xxx.xxx.xxx.xxx/ [latest-24115]2024-05-28T14:42:36.643Z <app:NOTICE> Starting HTTP server and API... [latest-24115]2024-05-28T14:42:36.645Z <httpapi:NOTICE> httpapi: starting HTTP service on port 8111 [latest-24115]2024-05-28T14:42:36.647Z <app:NOTICE> Starting Reaction Engine... [latest-24115]2024-05-28T14:42:36.648Z <Engine:INFO> Reaction Engine starting [latest-24115]2024-05-28T14:42:36.648Z <Engine:INFO> Checking rule sets... [latest-24115]2024-05-28T14:42:36.649Z <Engine:INFO> Checking rules... [latest-24115]2024-05-28T14:42:36.692Z <Engine:INFO> Data check complete; no corrections. -
MQTTController build 24142 is intended to be used only with the
userauthbranch of Reactor, which is why I announced its availability there rather than in the general Announcements thread (but I see I probably should have been more clear about that).Downgrading MQTTController is the correct response.
The
userauthbuild has been folded into mainline development on my end and is ready to be released, I've just been really busy and have held off letting such a major build go out when I know I won't have time in the 48-72 hours after to address issues and help with upgrade questions. Hopefully, today wraps up my external dependencies and I can get a newlatestbuild out tomorrow. -
That makes sense, and I actually typo'd the version number in my post reply (now edited/corrected). Stay on 24120 until the new
latestbuild comes out, and don't upgrade any templates from other developers if they are using new MQTTController features.Also, side note, the localization data/language file has been updated early in anticipation of the release.
-
T toggledbits locked this topic on
