-
Hubitat C7 = 2.3.2.141 AND 2.3.3.123
MSR in a docker = latest-22264-93bf3814 and latest-22266-88868fc0I'm curious if this is a bug or expected behavior. Unfortunately I don't know exactly when this began either. I have renamed a few devices over the course of the last few MSR builds, but never really brought it up before. Plus I don't rename devices too often. But I have a motion sensor right now that I renamed in Hubitat from "Office Motion" to "Living Room Motion" over 2 weeks week ago. Probably closer to 3 or 4 weeks now. I have restarted MSR several times since the rename, hard refreshed the browser, tried a different machine and different browser, and even an updated version of MSR. MSR is still showing the old name within the Entities section. I know I could rename it within MSR, but I would prefer to only have to rename devices in one location. I don't recall how long ago I started noticing this, which I know does not help at all.
-
The reason for my question is a rather long story involving a virtual thermostat on my Hubitat and using InfluxDB and Grafana to graph the state of the thermostat.
The TL;DR version is that it would be helpful if I could send MSR expressions (variables) to InfluxDB. I don't currently see any way to do that, and if it isn't a current capability of MSR it might be useful as a future enhancement.
Long version: I have a rule in MSR that runs every minute to pull the thermostat information from my thermostat's cloud API. I parse the response into global variables, and then update a Hubitat virtual thermostat when those global variables change. I added the x_hubitat_Thermostat entity, along with selected capabilities, to my reactor.yaml in the InfluxDB section, 'default_capabilities', so the changes to the virtual thermostat get logged into the db.
It's working OK except when the API reports that the temperature has reached the setpoint but the system is still operating. For example, in the morning when the heat is turned up, the temp will climb until the setpoint == the temperature, but the system will continue heating for a while afterwards. It's a variable speed/heat system so it continues to run at very low output for quite a while after the temps match.
The issue I'm having is that when the temperature matches the setpoint, the Hubitat virtual thermostat switches to idle mode on it's own, despite the fact that the API is still reporting heating mode. When the virtual device sees that the setpoint has been reached, it automatically changes to idle, which makes sense as that's how you'd want a real thermostat to work .
I am working around this by having the rule that updates the temperature on the virtual device also update the operatingState. This fixes it, but for just a few milliseconds the virtual thermostat switches to idle before the rule sets it back to heat, and that state change shows up in Grafana.
If I could just directly log changes to the expressions to InfluxDB I could avoid the issue and get the same data into the database. Also I can see other applications for something like this with other APIs where MSR and InfluxDB could be used to log data without having any virtual device entities involved.
-
Hey Patrick, had to switch over my HA VM from VirtualBox to VMware since VirtualBox stopped playing well. Anyways I updated the IP address to the new VM IP and deleted the Long Lived Access Token and created a new one just in case (copy pasted the new token into the config file). Tried rebooting both the HA machine and the MSR one too and MSR is still not connecting. The only thing I have not tried yet is creating another controller entry, but I am worried it may create all new entities for everything forcing me to redo all my logic. Here are some logs:
[latest-22258]2022-09-20T21:17:24.749Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:17:24.749Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:17:24.749Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:18:09.753Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket [latest-22258]2022-09-20T21:18:24.761Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:18:24.761Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:18:24.761Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:19:01.083Z <VeraController:INFO> VeraController#vera 0 dead entities older than 86400000s purged [latest-22258]2022-09-20T21:19:14.780Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket [latest-22258]2022-09-20T21:19:29.785Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:19:29.785Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:19:29.785Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:20:24.791Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket [latest-22258]2022-09-20T21:20:39.813Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:20:39.820Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:20:39.820Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out -
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. -
Patrick,
I've just imported a large set of rules from Vera, and I had already played with creating rules in MSR that are mixed throughout the existing Vera rules. Is there any sort of way to "find/replace" in MSR, so I can find all matches to the old rules and replace them with the new ones? -
Patrick,
Yesterday I migrated a large luup Reactor group over from Vera to MSR, following the directions to importing it from Vera in the documentation. One of the odd things in the migration was the conditional rules for House Modes. Many of my rules had conditions such as "House Mode is any of Home, Night, or changes to Away.The way the import did it was changes from 1,3 to null. This importation did not seem to trigger rules correctly.
I was able to fix all the instances by creating multiple triggers in a group:
Entity Attribute: House Mode (vera>housemode) x_vera_housemode.mode contains home
OR Entity Attribute: House Mode (vera>housemode) x_vera_housemode.mode contains nightIs this what you are expecting in importation?
-
Good morning all,
This weekend I've been playing around with Home Assistant as a replacement (long term) for my aging Vera platform. I'm pretty amazed how much more capability it has. On the other hand, the sheer amount of variables it pulls in from devices is massive.In any case, I have added Google Calendar into Home Assistant for things like Federal Holidays and my daughter's school calendar. It connected to them without issue, which I had been having problems with in Vera an GCal3.
I connected MSR to Home Assistant, so I can start using some of the systems I've integrated into Home Assistant in MSR, and continue migrating my luup Reactor rules over to MSR. Now I'm trying to create a rule based on if today is a Federal Holiday or not. Reactor sees the calendar just fine, however, for whatever reason, it's not pulling data for today, but the next event, which in this case is Columbus day, three weeks away. The attribute that is pulling this is x_haas_attr.message.
I tested with my daughter's school calendar, and it did have an entry for today, and none of the other values seemed to be different, such as a "true" or something to tell me there is an entry.
a8478a6e-d8eb-4572-ac84-c94ff012a1ec-image.png
60632486-e80b-4f0f-aed9-dc67113689a4-image.png
ab04cd0f-f849-4e14-be7d-f4c00735da77-image.png
The only thing I've been able to come up with, is there is a start_time attribute, which shows the date as 2022-10-10 00:00:00
1cbe4526-7f63-4329-a088-b331f1d03376-image.png
The only thing I can think of is there might be a way to compare the current system date to that date, but I can't seem to figure that out in MSR.
Has anybody done this? Any suggestions?
-
I started kicking around the VEC last evening, was cut short, and dug in a bit more this morning.
My reactor.yaml:
d3df4d99-aa7f-4b8b-8fb9-5a6c615daad9-image.png
I verified the yaml is good at https://yamlchecker.com/
What I'm seeing in MSR:
0f89ce8e-7abe-4779-baca-43123e030cf4-image.png
87560ded-7dfa-4340-8585-8be58ff22852-image.png
I believe I have followed all steps (standard disclaimers apply).
Anyone else started to tinker with this newness and, if so, what were your results?
-
Having just embarrassed myself to @toggledbits by asserting that the latest release somehow had a bug when in reality it was surfacing underlying issues with my approach to building out my rulesets and automations I wanted to ask the collective for their feedback on how they've designed their rulesets.
For me, I built out a list of Global Reactions that I commonly use. For instance, for mode changes I typically change the mode entity and write that mode to a variable for some future use. When building out a ruleset I just pull in that Global Reaction vs manually recreating the entity list as my ruleset Reaction. Example, for lighting:
270bbe18-9680-491d-81d4-20308a9fe63c-image.png
Each of these contains the appropriate group of lights to turn on/off, etc.
I also have what I've dubbed my "Armed for..." rulesets. These are rulesets that can be referenced as true or false in other rulesets. Example, for my various lighting configurations in and out of the house I have these:
0d9f55d4-5d5d-42e2-a83c-8afa95df08fb-image.png
I think this is resulting in reactions stomping on other reactions creating race conditions that result in things looking like they're working when, in reality, they're one restart away from disaster.
So how are you all designing your superstructure, if you will, at a high level?
-
Maybe more of a cosmetic issue, but certain entities could be hidden from entity actions as you cannot set any meaningful action? See Vera as an example:
Screenshot 2022-09-16 at 15.11.29.png
vera>system is then obviously a different story and should be there
-
Hi @toggledbits,
I have a bridge consuming Vera's variable using the MQTTController in MSR, and I've noticed that after I've updated to the latest version (22257), some variables are not echoed. I've already tried to reboot MSR, with no luck.
These variables are under urn:smarthome-community:serverId:Vacuum
0fe837ed-3a29-4d5d-a06c-445981d44e13-image.png
A trace via MQTT explorer:
cf919028-4f7b-4761-b99a-c3943945704a-image.pngMy config has just exclude_capabilities: [] and it was working OK before the latest build. Even /query command doesn't seem to retrieve all the attributes. The values are retrieved correctly from the Vera controller, and I could use them in MSR, they're just not echoed to the bridge. Thanks!
-
Good morning all,
I"m working on converting my luup Reactor scenes over to MSR, so I can eventually introduce an Ezlo plus into the mix and not loose all the work I've done with Reactor. If nothing else, this should free up some resources on my aging Vera Plus, and maybe speed up some functions. Maybe that's just wishful thinking.In any case, I'm moving move my first Reactor set, which is a set of rules to control the blilnds/window coverings in my home. I have two types of blinds:
iBlinds retrofit motors (IB2.1-ZWx) version from late 2019.
Bali roman shades with factory installed Somfy CSZ1 Z-wave motors.I'm setting up reactions for both types of window coverings. One of the problems I always had in Vera was with iBlinds, I had to do it by luup commands:
luup.call_action("urn:upnp-org:serviceId:Dimming1","SetLoadLevelTarget",{ newLoadlevelTarget="50" },316)The reason for this, is that the open position was 100%, and the close position was 0%. In other words, the blinds were closed one way 100% an closed 100% the other way. I've been informed by iBlinds support that even in Ezlo, they still do it this way, which is different than most other Z-wave controller manufacturers. I'm not sure how the others do it, but some how "open" is right in the middle (50%).
So, in MSR, i can still set the Dimming1.SetLoadLevelTarget to 50, but I also noticed some other commands I haven't seen before in Reactor
3cdeeb89-5986-45bc-8a3b-79067050a22c-image.png
Is there some way in MSR to set that middle value to 50% so I can use cover.open? The command cover.close works as expected, so I'm wondering how I might use that cover.set.
Thanks for any advise.
-
I configured OWM Weather on MSR (latest-22257-dd9b9271), created an account with OWM, generated an API key, put the key in the yaml file, and I’ve waited over a day now. OWM Weather shows as up on the the Controller Status widget.
I’ve tried to create a trigger or constraint to use the data, and nothing is really showing up.
5B8611C1-33D0-4D3C-B507-7383CB81E25A.jpeg
I only have a free subscription with OWM, but I was expecting some data.
Is this expected behavior (i.e., still in development), or do I do more configuration other than the .yaml file?’
I still am able to pull Weather data through Dark Sky in my Vera plus controller, however, I know that will no longer work at some point.
-
Was just looking at the new metadata stuff in Entities for a lamp. I was on the dimming.level attritube and I then changed the dim level of the lamp several times and some how I got all these windows.
I then selected a different attribute color_temperature.value and that window was then shown over the top of all the others.
267e6d0d-7245-4816-ac93-ac83cfda509e-image.png
I don't know how to close these windows down ?
b09fd5f1-fffe-40c2-8ba6-8cffacd1e28b-image.png
Thanks
-
Hey Patrick, similar to R4V it would be nice if we could set the max amount of time a condition pulses. Currently in MSR you can only set it to pulse once or repeat continually until the condition goes false.
I currently have a rule that pings dead devices and occasionally the dead device needs a few pings for it to come back alive but I don't want it to keep pinging forever if the device is actually not functioning.
-
Hi
Anyone else been having issues with the MSR web UI not connecting after a period of time? Or is it just me?
If I reboot the Linux Debian box then MSR starts working again and I can open the web UI and it says connected.
However after sometime I then cannot later connect to the web GUI. It just says connecting all the time.
I also have Node-Red and HA Bridge running on the same box and I can connect to those two fine still.
Thanks
-
Is is possible for MSR to show newly detected ZwaveJS devices in the current alerts windows like Hubitat and HA? New devices show in the Entities but there is not an alert.
-
Hi Patrick,
For as long as I can remember, I have red x's instead of icons in MSR.05f25684-b338-4f69-8d0a-8a482a9fe1a2-image.png
I am running MSR in Docker and am on version 22252. If hosted in the cloud, they could be getting blocked by pihole.
Thanks,
Roger -
TLDR: I'm getting an alert saying I have to edit and re-save a rule containing a HTTP POST request in order to update it, but following the instructions in the alert doesn't seem to fix the issue.
I am receiving this message in the Current Alerts when sending a HTTP POST request.
The action at step 1 of "Send Notification Reaction" (re-I7yq7e15) needs to be edited to update it to the latest stored form. The action will continue, but should be updated as soon as possible, before this form is deprecated and no longer functions. Just make a trivial edit to the "headers" argument and then save the reaction to update it.
Details:
I am using a self-hosted notification system - Gotify. Many of my rules use a HTTP POST action to send a notification through this system. The message contains a JSON body with the title, body, and message priority. It is posted to a URL on my LAN where the Gotify server resides.
When I updated to latest-22252-65e94b36 I started to receive the above error. Since I had the http request in many rules I took the opportunity to simplify things by moving the http request to a Reaction in the Reactions section of MSR. I created two variables to pass the notification content to the Reaction and now send all notifications via the one Reaction. Each rule that needs to send a reaction sets the variable values and then runs the Reaction.
For example, this rule runs if the Kitchen Main leak sensor detects a leak. It sets the variable "g_gotify_token" to a value (this is used as part of the URL when making the HTTP request) and sets "g_gotify"body" to a JSON formatted string. In this case that string is
{ "title":"Water Alert", "message": "Kitchen Main Leak Sensor Tripped", "priority": 8 }Finally, the rule runs the Reaction "Send Notification Reaction"
79fd4034-c611-4173-b4e4-18cf5091b453-image.png
That reaction contains the http request. It uses the variables in the URL and request body fields. The request headers field is static and is set to "Content-Type: application/json"
d75d9305-a5ab-4401-9b75-ea72d08787fa-image.png
I get the same error when I directly call the HTTP request from a rule without using any variables. Either way, the notification goes through successfully. The only issue is the alert being raised in MSR.
I tried editing and re-saving the Reaction, and also tried creating an entirely new reaction. I get the same warning message either way.
footnote: Because I use the same process to send a notification whenever there is an alert raised in MSR, this also created a loop (that thankfully got throttled pretty quickly) where the system was making the http request to send a notification that this alert had been raised, and the action of sending that notification raised the alert again... etc...
Is this just a bug? Am I missing something about the request format that needs to be updated? I checked the manual and this forum for answers, but didn't find anything that looked relevant.
-
I use a number of multistring devices in my vera plus. My 'original' multistring devices work in Reactor i.e.:
9c5203dd-1993-4b5b-aeee-44377c1ee1c5-image.png
42b97524-9428-4222-a3fb-ce4e0009c00b-image.png
However, the new ones I have added do not show the device data sets / parameters (not sure what the correct term is?):
a54ddf29-ea32-47c9-906e-260a25dcb482-image.png
3efa1d0a-5466-4220-93d3-0a67da42a5d0-image.png
Is there something that I am doing wrong?
[SOLVED] Fatal error on upgrade to 22021 / Raspberry Pi4 Docker
-
I attempted to upgrade my Docker container to "toggledbits/reactor:latest-raspbian-armv7l" and the container started but the Reactor interface wouldn't load in the browser. The logs showed this:
# # Fatal error in , line 0 # unreachable code # # # #FailureMessage Object: 0xbec2458c # # Fatal error in , line 0 # unreachable code # # # #FailureMessage Object: 0xbedec58c # # Fatal error in , line 0 # unreachable code # # # #FailureMessage Object: 0xbed3358c # # Fatal error in , line 0 # unreachable code # # # #FailureMessage Object: 0xbef7f58c # # Fatal error in , line 0 # unreachable code # # # #FailureMessage Object: 0xbedd958c # # Fatal error in , line 0 # unreachable code # # # #FailureMessage Object: 0xbe86958cThe logs continued throwing errors with different object IDs.
I removed the container and tried to install again using toggledbits/reactor:1.0.2-raspbian-armv7l and now the container won't start and the logs show this:
NODE_PATH /opt/reactor FileLogStream { type: 'file', name: 'reactor.log', mode: 438, maxsize: 2, keep: 5 } [1.0.2-21350]2022-01-22T14:35:21.715Z <app:null> Reactor "1.0.2-21350-252f948" starting on v16.11.1 [1.0.2-21350]2022-01-22T14:35:21.717Z <app:INFO> Process ID 1; platform linux/arm #1457 SMP Tue Sep 28 11:26:14 BST 2021; locale (undefined) [1.0.2-21350]2022-01-22T14:35:21.718Z <app:INFO> Basedir /opt/reactor; data in /var/reactor/storage [1.0.2-21350]2022-01-22T14:35:21.719Z <app:INFO> NODE_PATH=/opt/reactor [1.0.2-21350]2022-01-22T14:35:21.727Z <app:INFO> Configured locale (undefined); selected locale(s) en-US.UTF-8 [1.0.2-21350]2022-01-22T14:35:21.786Z <app:INFO> Loaded locale en-US [1.0.2-21350]2022-01-22T14:35:21.812Z <Capabilities:null> Module Capabilities v21333 [1.0.2-21350]2022-01-22T14:35:21.890Z <Plugin:null> Module Plugin v21186 [1.0.2-21350]2022-01-22T14:35:21.902Z <TimerBroker:null> Module TimerBroker v21333 [1.0.2-21350]2022-01-22T14:35:21.908Z <default:INFO> Module Entity v21334 [1.0.2-21350]2022-01-22T14:35:21.916Z <Controller:null> Module Controller v21333 [1.0.2-21350]2022-01-22T14:35:21.917Z <default:null> Module Structure v21338 [1.0.2-21350]2022-01-22T14:35:21.934Z <default:null> Module Ruleset v21096 [1.0.2-21350]2022-01-22T14:35:21.935Z <default:null> Module Rulesets v21096 [1.0.2-21350]2022-01-22T14:35:21.956Z <GlobalExpression:null> Module GlobalExpression v21333 [1.0.2-21350]2022-01-22T14:35:21.986Z <default:null> Module Rule v21348 [1.0.2-21350]2022-01-22T14:35:21.994Z <GlobalReaction:null> Module GlobalReaction v21333 [1.0.2-21350]2022-01-22T14:35:21.997Z <AlertManager:null> Module AlertManager v21333 [1.0.2-21350]2022-01-22T14:35:21.998Z <default:null> Module Engine v21346 [1.0.2-21350]2022-01-22T14:35:21.999Z <default:null> Module httpapi v21345 [1.0.2-21350]2022-01-22T14:35:22.004Z <default:null> Module httpproxy v21333 [1.0.2-21350]2022-01-22T14:35:22.037Z <default:null> Module wsapi v21334 [1.0.2-21350]2022-01-22T14:35:22.048Z <app:NOTICE> Starting Structure... [1.0.2-21350]2022-01-22T14:35:22.131Z <InfluxFeed:null> Module InfluxFeed v21345 [1.0.2-21350]2022-01-22T14:35:22.135Z <Structure:INFO> Structure#1 starting plugin influx (InfluxFeed) [1.0.2-21350]2022-01-22T14:35:22.137Z <Structure:INFO> Structure#1 loading controller interface hubitat (HubitatController) [1.0.2-21350]2022-01-22T14:35:22.162Z <HubitatController:null> Module HubitatController v21338 [1.0.2-21350]2022-01-22T14:35:22.174Z <Structure:INFO> Structure#1 loading controller interface hubitat_11705 (HubitatController) [1.0.2-21350]2022-01-22T14:35:22.180Z <Structure:INFO> Structure#1 loading controller interface weather (OWMWeatherController) [1.0.2-21350]2022-01-22T14:35:22.194Z <OWMWeatherController:null> Module OWMWeatherController v21313 [1.0.2-21350]2022-01-22T14:35:22.198Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [1.0.2-21350]2022-01-22T14:35:22.205Z <SystemController:null> Module SystemController v21345 [1.0.2-21350]2022-01-22T14:35:22.211Z <Structure:INFO> Structure#1 loading controller interface mqtt (MQTTController) [1.0.2-21350]2022-01-22T14:35:22.223Z <MQTTController:null> Module MQTTController v21361 [1.0.2-21350]2022-01-22T14:35:22.227Z <Controller:CRIT> Controller: failed to load mqtt implementation file:///var/reactor/ext/MQTTController/MQTTController.js: [TypeError]TypeError: require(...).requires is not a function [1.0.2-21350]2022-01-22T14:35:22.229Z <Controller:CRIT> TypeError: require(...).requires is not a function TypeError: require(...).requires is not a function at Object.<anonymous> (/var/reactor/ext/MQTTController/MQTTController.js:14:53) at Module._compile (node:internal/modules/cjs/loader:1101:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:196:29) at ModuleJob.run (node:internal/modules/esm/module_job:183:25) at async Loader.import (node:internal/modules/esm/loader:178:24) at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15) Trapped unhandled Promise rejection TypeError: require(...).requires is not a function at Object.<anonymous> (/var/reactor/ext/MQTTController/MQTTController.js:14:53) at Module._compile (node:internal/modules/cjs/loader:1101:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:196:29) at ModuleJob.run (node:internal/modules/esm/module_job:183:25) at async Loader.import (node:internal/modules/esm/loader:178:24) at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15) TypeError: require(...).requires is not a function at Object.<anonymous> (/var/reactor/ext/MQTTController/MQTTController.js:14:53) at Module._compile (node:internal/modules/cjs/loader:1101:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:196:29) at ModuleJob.run (node:internal/modules/esm/module_job:183:25) at async Loader.import (node:internal/modules/esm/loader:178:24) at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15) { <rejected> TypeError: require(...).requires is not a function at Object.<anonymous> (/var/reactor/ext/MQTTController/MQTTController.js:14:53) at Module._compile (node:internal/modules/cjs/loader:1101:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:196:29) at ModuleJob.run (node:internal/modules/esm/module_job:183:25) at async Loader.import (node:internal/modules/esm/loader:178:24) at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15) } Trace at process.<anonymous> (/opt/reactor/app.js:267:142) at process.emit (node:events:390:28) at process.emit (node:domain:475:12) at emit (node:internal/process/promises:136:22) at processPromiseRejections (node:internal/process/promises:242:25) at processTicksAndRejections (node:internal/process/task_queues:97:32) [1.0.2-21350]2022-01-22T14:35:22.234Z <app:ERR> Trapped unhandled Promise rejection: [TypeError]TypeError: require(...).requires is not a function [1.0.2-21350]2022-01-22T14:35:22.234Z <app:ERR> Please refer to the console log for traceI noticed the reference to MQTT so I changed MQTT controller to enabled:False in my reactor.yaml file. I tried reinstalling latest with the same results as before. I was then able to install 1.0.2 successfully and Reactor is running. I'm only getting this error on the status page:
An Entity Attribute condition in rule "Notify when Reactor Alert is raised" failed because the referenced entity Reactor System (reactor_system>system) does not have attribute reactor_system.alert_lastI assume that 1.0.2 was prior to that feature being implemented.
Any advice on how to successfully upgrade to 22021 would be appreciated. I saw the instructions for bare metal, but I don't think that applies when I'm pulling the docker image and creating a new container.
-
@toggledbits Setting aside the hijack of my Raspberry Pi Docker thread by a Windows bare metal issue... any thoughts on why my docker install of "latest" failed?
-
@Alan_F version 1.0.2 will not support the version of MQTTController you are using. I have no issue starting a container on latest; not getting the error you are reporting (and I ran the container before deploying it and didn't see it then, either).
I think your first step should not be going backwards, but reinstalling the current version. If MQTTController won't load on latest, then disable it via config and try restarting. Post overall doesn't have much context (log snippet needs more context).
-
That wasn't a log snippet... at least not the first one. That was the entire log after upgrading to latest. The issue doesn't appear to be that MQTT controller won't load on latest. With MQTT set to false I still get nothing in the log file but "Fatal Error at line 0".
I assume something in my config file is the issue, so I'll start commenting out sections that aren't default and hope I can get it working.
Edit: I think I see one source of confusion... that first set of log entries is from the logs of the docker container, which I pulled from Portainer (used to manage my Docker containers). While Portainer shows the container as running, Reactor itself is not saving any logs at all. I guess that makes sense if it crashed out on line zero...
How can I get a new/clean version of reactor.yaml? I tried deleting my docker image, renaming the existing file, and pulling/running the docker image again, but it doesn't create a new reactor.yaml.
I also tried making sure my RPi4 was up to date (apt update / apt full-upgrade) then rebooted, but I'm still stuck.
-
After barking up many wrong trees I found this: https://www.giters.com/SensorsIot/IOTstack/issues/401
Which provided these steps to fix the issue
$ sudo apt-key adv --keyserver hkps://keyserver.ubuntu.com:443 --recv-keys 04EE7237B7D453EC 648ACFD622F3D138 $ echo "deb http://httpredir.debian.org/debian buster-backports main contrib non-free" | sudo tee -a "/etc/apt/sources.list.d/debian-backports.list" $ sudo apt update $ sudo apt install libseccomp2 -t buster-backportsAfter running those command, MSR is back in business on the latest build.
-
Interesting, so I found Sam Cater's blog, the source for your first link. That was necessary to build the image for RPi because docker would not even build the container on Alpine 3.13 or 3.14 without the patch. I did not anticipate that effect of the patch would penetrate the container, but I can see how it could.
I'm not inclined to back off back to 3.12, though. As your link points out, newer versions of Grafana and Mosquitto are affected in the same way, and I'm sure the other tools mentioned will soon follow. We're all in the same boat. So, I'm going to incorporate this step into the installation instructions for docker container users on Raspbian Buster.