-
I am trying to display the primary attribute on this device like all my other Hubitat devices. The attribute is x_hubitat_extra_attributes.Status. This gives an error in the log. I can't see what I am doing wrong with this one. Do I need to to something different to display this?
[latest-21286]2021-10-16T14:42:23.141Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [latest-21286]2021-10-16T14:42:23.166Z <HassController:NOTICE> HassController#hass attempting reconnection to ws://192.168.1.21:8123/api/websocket [latest-21286]2021-10-16T14:42:23.168Z <HassController:NOTICE> HassController#hass connecting via WS to ws://192.168.1.21:8123/api/websocket [latest-21286]2021-10-16T14:42:23.246Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. [latest-21286]2021-10-16T14:42:23.269Z <app:INFO> Structure running; pausing for controllers' initial ready [latest-21286]2021-10-16T14:42:23.273Z <HubitatController:NOTICE> HubitatController#hubitat not ready; performing initial connect/query [latest-21286]2021-10-16T14:42:23.290Z <HassController:NOTICE> HassController#hass connected, starting protocol [latest-21286]2021-10-16T14:42:23.296Z <HassController:INFO> HassController#hass successful authentication with ws://192.168.1.21:8123; fetching initial data... [latest-21286]2021-10-16T14:42:23.300Z <HassController:INFO> HassController#hass Hass reports version "2021.10.5" location Home timezone America/Chicago state RUNNING safe_mode false [latest-21286]2021-10-16T14:42:23.303Z <HassController:ERR> HassController#hass reported Hass version "2021.10.5" is not supported! [latest-21286]2021-10-16T14:42:23.379Z <HassController:NOTICE> Controller HassController#hass is now online. [latest-21286]2021-10-16T14:42:23.563Z <default:ERR> [Entity:setPrimaryAttribute] Attempt to set primary to x_hubitat_extra_attributes.Status invalid, not in { "x_hubitat": { "id": "568", "name": "BlinkAPI", "commands": [ "ArmSystem", "Authorize", "CheckSyncModule", "DisableMotionDetection", "DisarmSystem", "EnableMotionDetection", "GetCameraInfo", "GetCameraLiveView", "GetCameraSensors", "GetCameraStatus", "GetCameraUsage", "GetHomescreen", "GetNetworkStatus", "GetNetworks", "GetNewThumbnail", "GetNotifications", "GetVideoEvents", "ListSchedules", "VerifyPIN", "refresh" ], "capabilities": [ "Actuator", "Refresh", "Sensor" ] }, "x_hubitat_Actuator": { }, "x_hubitat_Refresh": { }, "x_hubitat_Sensor": { }, "x_hubitat_extra_commands": { } } [latest-21286]2021-10-16T14:42:23.566Z <HubitatController:ERR> HubitatController#hubitat failed to connect/query http://192.168.1.70/apps/api/416: Error: Entity#hubitat>568:setPrimaryAttribute() can't set x_hubitat_extra_attributes.Status, not defined for entity [latest-21286]2021-10-16T14:42:23.567Z <HubitatController:CRIT> Error: Entity#hubitat>568:setPrimaryAttribute() can't set x_hubitat_extra_attributes.Status, not defined for entity Error: Entity#hubitat>568:setPrimaryAttribute() can't set x_hubitat_extra_attributes.Status, not defined for entity at Entity.setPrimaryAttribute (/opt/reactor/server/lib/Entity.js:403:19) at /opt/reactor/server/lib/HubitatController.js:865:183 at Array.forEach (<anonymous>) at /opt/reactor/server/lib/HubitatController.js:805:76 at processTicksAndRejections (internal/process/task_queues.js:95:5) [latest-21286]2021-10-16T14:42:23.713Z <OWMWeatherController:INFO> OWMWeatherController#weather done; 1 locations, 0 failed [latest-21286]2021-10-16T14:42:23.714Z <OWMWeatherController:NOTICE> Controller OWMWeatherController#weather is now online. [latest-21286]2021-10-16T14:42:48.577Z <HubitatController:NOTICE> HubitatController#hubitat not ready; performing initial connect/query [latest-21286]2021-10-16T14:42:48.779Z <HubitatController:INFO> HubitatController#hubitat connecting to hub's eventsocket WebSocket API at ws://192.168.1.70/eventsocket [latest-21286]2021-10-16T14:42:48.781Z <HubitatController:NOTICE> Controller HubitatController#hubitat is now online. [latest-21286]2021-10-16T14:42:48.786Z <app:NOTICE> Starting HTTP server and API... [latest-21286]2021-10-16T14:42:48.791Z <app:NOTICE> Starting Reaction Engine... [latest-21286]2021-10-16T14:42:48.792Z <Engine:INFO> Reaction Engine starting [latest-21286]2021-10-16T14:42:48.792Z <Engine:INFO> Checking rule sets... [latest-21286]2021-10-16T14:42:48.798Z <Engine:INFO> Checking rules...
Log:Screen Shot 2021-10-16 at 10.11.12 AM.png local_hubitat_devices.yaml:
Screen Shot 2021-10-16 at 9.56.43 AM.png -
In the background of other work, I've been putting together a build system for the OpenWrt version that Ezlo is using on the Plus. Job done. I can build pretty much any package, which may come in handy some day.
As a test of that, I thought, why not build nodejs... and you know where that leads, right?
It took some doing. There are a lot of dependencies, and the errors you get when the dependencies aren't met correctly can be cryptic and took quite a bit of research and experimentation to resolve... weeks, in fact, over a couple of hours here, a couple there.
But it's done and I now have Reactor running on an Ezlo Plus.
I'm not sure what the long term utility of this might be. Since the new Ezlo philosophy is to upgrade your system automatically on reboots, and so far the upgrades have wiped substantial parts of the file system in my experience, this could be a non-starter as a platform — you wouldn't want your automations to get blown off the machine every time Ezlo upgrades firmware (because you don't know when that's going to be, and Murphy says it will be while you are on vacation with no remote access). But, if there is some place it can be tucked away safely, or if, as probably should be demanded by the user community, updates become elective and user-driven, it actually makes a nice Pi-ish platform to run on.
On to the next skunkworks project...
-
Timestamps do not match the UI time or the system time:
[latest-21286]2021-10-16T03:10:43.922Z <Engine:INFO> Engine#1 master timer tick, local time "10/15/2021, 8:10:43 PM" (TZ offset -420 mins from UTC)I tried adding TZ to the docker container with "docker exec reactor apk add tzdata" but there was no change in log timestamps. I have the TZ in the compose file as:
environment: REACTOR_DATA_PREFIX: /var/reactor TZ: America/Los_AngelesThis does set the UI time correctly. The Reactor config is also set correctly:
location: city: "Los Angeles" -
I'd like to invoke in Reactor a Home Assistant service through the HA API. I use the following code in a vera plugin I wrote to send an HTTP request to Home Assistant to trigger an announcement on Alexa--using a Home Assistant Alexa integration that you can install through HACS.
myEchoDevice = "alexa_media_".. myEchoDevice myEchoMessage = table.concat(myEchoMessage) local request_body = json.encode {message = myEchoMessage, data = {["type"] = "announce",method = "all"}} local response_body = {} local theURL = 'http://'..HomeAssistantIP..':'..HomeAssistantPort..'/api/services/notify/'..myEchoDevice r, c, h = http.request { url = theURL, method = "POST", headers = { ["Content-Type"] = "application/json", ["Authorization"] = "Bearer ".. HomeAssistantToken, ["Content-Length"] = request_body:len() }, source = ltn12.source.string(request_body), sink = ltn12.sink.table(response_body) }I don't see the "notify" service in the HA attributes revealed by reactor. Is there a way to access the Home Assistant API through reactor, or do I need to use HTTP requests to initiate services.
-
Hi
I have some devices on my Vera Plus controller that sometimes change to say "Can't detect device".
I can clear those red banners that show up in the Vera UI7 web GUI, for a device by running some LUA code like this:
luup.set_failure(0, 331)Maybe I can use the new MSR matchEntities to find and detect any devices on Vera that have developed the "Can't detect device" error and then reset them. ?
I can currently manually specify a particular problem device in a ruleset trigger like this:
6f789006-ce19-4776-b3dd-290e28e84c8b-image.png
But if I could have a rule that automatically detects any device that develops this problem that would be better.
Thanks
-
Hi Patrick! @toggledbits
I don't remember before version 21277 receiving this kind of message.
dbea16f0-39f8-475a-bee8-8899069f2db3-image.png
This is in the log, this warning appears hundreds of times, every 1 second it repeats.
[latest-21281]2021-10-10T16:13:46.107Z Rule:WARN Rule#rule-ku32lfti (Warning (93) Devices) update rate 61/min exceeds limit (60/min)! Logic loop? Throttling...
[latest-21281]2021-10-10T16:13:46.482Z Rule:WARN Rule#rule-ku32lfti (Warning (93) Devices) update rate 61/min exceeds limit (60/min)! Logic loop? Throttling...
[latest-21281]2021-10-10T16:13:46.835Z Rule:WARN Rule#rule-ku32lfti (Warning (93) Devices) update rate 61/min exceeds limit (60/min)! Logic loop? Throttling...As you can see, the rule that has generated this warning is run on demand at 10am, where the information is loaded into local variables, and then I use it to send the information by Telegram, only once a day.
5d55901a-bcbe-4cd6-8989-01d7a0ff9c67-image.png
I started using this matchEntities() instruction recently when it was made available, and I see you have been making recent adjustments. Wouldn't this situation of continuing to evaluate be related?
I will turn the rule off, so as not to generate this situation that surely damages the functioning of the MSR, and I look forward to your comments please.
Thanks
-
Hi!
- id: reactor_system enable: true implementation: SystemController name: Reactor System config: # # The update_interval can be set lower for more frequent updates. The default is 60 # seconds, which is probably fine for most cases, but causes the 15-second load av- # erage to be inaccurate (the first value in reactor_system.system_load). If you # don't care about the 15-second load average, then the default 60 seconds is fine. # This value is expressed in milliseconds. update_interval: 60000 locale: sv-SE #
I would like to try out the swedish translation (thanks @Crille ). I have tried to edit my reactor.yaml file in many ways, but the translation don't show up. I have done a browser hard refresh every time. Where do I go wrong? Here's my latest try:What's the correct syntax, placement and intendention?
Thanks!
/Fanan -
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. -
Got a warning that "Rule is being throttled because its update rate exceeds 60 updates per minute. Check for logic errors that may be causing an evaluation loop, or devices that are "flapping".
Device in question here is Aeotec Smart Switch 6 connected to Vera Plus, and its configuration is below:
Screenshot 2021-08-31 at 13.13.22.png
Shouldn't be an evaluation loop as the rule is very simple (two AND'ed conditions where the first checks whether alarm state is "disarmed" and the second if smart switch power switch state is false).
Noticed though at the time of warning that wattage measured/reported was changing quite rapidly, so even though wattage was not used in the rule, could that be the reason for throttling? If so, is there anything else that could be done other than raising minimum change values in device configuration? Would like to retain sensitivity for other purposes.
-
Just noticed that when trying to reorder some expressions, e.g. move the most recent one from the bottom of the list to the first, this new order didn't "stick".
At first yes, but when visiting some other menus (obviously saving before that) and then coming back, the moved item was in its original position (in the end of the list).
I currently have 29 global expressions (which may or may not have some relevance to this problem). Using build 21281 on linux.
Can log a PR with logs, if this seems hard to reproduce.
-
Hey crew, I followed the tutorial to get MSR installed on Rasbperry Pi (bare metal). Just having a little trouble getting Vera to connect to it.
I'm getting error messages-- I searched in the forum and didn't see other people running into these messages. Here are the two main errors I've been getting...
2021-09-21T01:30:36.477Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632187836460 failed, reason: socket hang upand
2021-09-21T01:26:08.296Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632187568275 failed, reason: connect ECONNREFUSED 10.0.0.141:3480I'm sure it'll be an easy fix, but truthfully I'm stumped here and would love any advice. Thank you!
-
@toggledbits I've done a (test) Swedish translation for MSR, I don't want/need a translated version, but I had the time and perhaps some future users would find it useful 🙂
I noticed it's a bit early in the process to go live with systemwide localizations so no github in place yet, do you want input on this now or should we wait a few releases? considering it may be low priority issues.
If so, do you want feedback here or in mantis? -
Let's say I have an array like the one below:
["vera>device_216","vera>device_235","vera>device_241"]How do I remove "vera>device_235" out of it?
Alternatively, when filtering entities:
each id in dynamic_array: getEntity( id ).attributes.x_vera_svc_micasaverde_com_HaDevice1?.CommFailure == 1 ? id : nullHow could I exclude certain id from the array that is produced?
-
I have some battery powered sensors that doesn't report battery level and thought it would be nice if can make MSR to send me a notification if a sensor value doesn't change for 24h.
I tried to make a rule that monitored if a temperature value NOT changes, but in this setup I couldn't choose Sustained For as I expected.
Any way around this?
Any reason that Sustained For can't be used when monitoring a value Change? -
@toggledbits Today I got a false positive from Reactor saying my Ezlo Plus was offline, a restart of Reactor solved it.
2021-10-01T06:32:29.441Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: RangeError: Maximum call stack size exceeded 2021-10-01T06:32:29.441Z <EzloController:CRIT> RangeError: Maximum call stack size exceeded RangeError: Maximum call stack size exceeded at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1134:127) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) 2021-10-01T06:32:38.985Z <EzloController:ERR> EzloController#ezlo request "17c3a8dccaf" (hub.info.get) failed: TimedPromise timeout 2021-10-01T06:32:38.985Z <EzloController:ERR> EzloController#ezlo failed to complete inventory: TimedPromise timeout 2021-10-01T06:32:38.985Z <EzloController:CRIT> !TimedPromise timeout 2021-10-01T06:32:38.988Z <EzloController:NOTICE> EzloController#ezlo connection closed: 1002
This was found in the log before the restart:Reactor latest-21270-48528ec, updated to latest-21270-46679ac just now.
-
@toggledbits I followed to the letter your excellent step-by-step guide on launching a Docker container from the image I fetched from PR #58 this morning.
All proceeded swimmingly – folder creation, image upload, settings & parameters, etc. – until the moment of actual Launch.
Whereupon, Docker threw up the following on-screen "Stopped Unexpectedly" warning (which repeated every 30 seconds or so until I Stop'ped the container from running/restarting):
docker_msr_stopped.pngConcurrently, every attempt to access http://<mySynNAS_IP>:8111/ resulted in a "This site can't be reached" error page in Chrome (under Windows, mind you).
Immediately, I took the liberty of inspecting and Export'ing the logfile (Container ► Details ► Log) as an HTML file, which I attach below (oops, no attachment feature in this forum, so here is the direct link) for your inspection.
Hope you find some clues, because I'm not at all sure where things went wrong. (The only facet of setup where I expressly deviated from your typed notes involved creating a "Shared" (i.e. top-level, rather than under /home) folder called "Reactor" with r/w access, under which I created a subfolder named "Data", to which I pointed /var/reactor during container creation.)
Excellent write-up and thanks for the chance to test this out!!
LibraFOLLOW-UP NOTES
I do see where Container ► Edit ► Environment ► variable PATH has a value of "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" which strikes me as odd, but maybe that's normal nomenclature? (By contract, Windows and DOS always use semicolons, not colons, to separate PATH variable entries.)RESOLVED
Noting that the Log displayed an error message related to /var/reactor/config, I went and created a folder named 'config' (all lowercase) under the NAS's top-level Reactor\Data folder, then restarted the container. It's running fine now, and I'm able to access the :8111 interface for the first time.
Log ► "Configuration path: /var/reactor/config resolved /var/reactor/config"SUGGEST
Please add explicit declaration in your How-To regarding the need for a /config underneath the data folder. -
Hi, I was trying to setup influxdb for MSR and on my Synology Nas, docker installation, I started with Influxdb 2.0.
influxdb: api_version: 2 ssl: false host: 10.0.0.11 port: 8086 token: Your HomeAssistant - Write token organization: Home bucket: HomeAssistant
Now seems it is very different from 1.x.
Databases don't exist anymore, they are named "buckets" now and there are token values.
Looking around, I found something on HA like this in "configuration.yaml" file.I don't use HA, just starting to bring devices on ezlo plus. Does MSR support this version Influxdb 2.0? or better to re-install 1.x?
Thanks in advance
-
I did a fresh install of MSR yesterday and noticed that the latest docker image was not pulling down. I had to use the CLI command "docker-compose pull MSR" where "MSR" is the service name I gave to the container in docker compose. After pulling the image, most everything worked as expected and the localization bug I saw was resolved. I've seen this type of update behavior before in other containers-- usually when the docker tags are not updated, but it could be something wacky on my end as well.
I also saw a small bug in the config file that I tried to post on Mantis, but I could not log in. Are you using the bug tracker, or do you prefer forum posts?
-
Hi everyone
I'm about to set up notifications from MSR and would like input on what works best.
Quick and reliable delivery to Android devices is the goal.(Tried to set up pushover last night, but probably missed something because it doesn't work. Succeed thru homeassistant, but not with MSR.)
Is pushover worth its money?
what do you use and why?Greatly appreciate your thoughts 🙂
-
I'm struggling to get MSR working in my QNAP (TS-321P). I am obviously not doing something correct in the setup, but cannot work out what. When I select 'Start' a second or so later the container stops. I get the following message in the container station - container tab 'standard_init_linux.go:219: exec user process caused: exec format error'. Assistance would be very much appreciated!
Safari Mac Rule Sets Menu after upgrade build 21275
-
I can no longer access the Rule Sets menu after upgrading to build 21275. Nothing happens when I click on Rule Sets. Other menu options work fine. I have cleared history, hard refreshed the browser, Rebooted. Works fine in Firefox and google chrome. I have always used Safari.
Suggestions?Safari for Mac version 15.0
MSR Version 21275-df3d784
Synology Docker -
I don't have a Mac or Safari, but let's try this. Enable the "Develop" menu in your browser if you haven't already (Safari > Preferences > Advanced and find the checkbox to enable the menu). Then Cmd + Option + C opens the console. Refresh the page and try to click into the Rule Sets menu. See if logs anything useful to the console (post here).
-
@toggledbits I did as you suggested. It is showing an error on refresh but nothing changes when clicking Rule sets. If I continually hit refresh, sometimes the error is gone and then the rule sets menu works. It appears if I open in a private window the error is not there either.
Edit: The reactor.log shows this also. I do not know if it related but I have no idea what the 172. address is.
2021-10-03T19:07:55.494Z Engine:5:1448:Engine.js Engine#1 reaction rule-kpw0p0rl:R step 0 perform { "entity": "hubitat>11", "action": "power_switch.off" }
2021-10-03T19:07:55.494Z HubitatController:null HubitatController#hubitat final action path for power_switch.off on Entity#hubitat>11: http://192.168.1.70/apps/api/416/devices/11/off
2021-10-03T19:07:55.495Z Engine:5:1351:Engine.js _process_reaction_queue() task returned, new status 3; task 66
2021-10-03T19:07:55.496Z Engine:5:1386:Engine.js _process_reaction_queue ending with 1 in queue; none delayed/ready; waiting
2021-10-03T19:07:55.538Z Engine:5:1386:Engine.js _process_reaction_queue() wake-up!
2021-10-03T19:07:55.540Z Engine:5:1347:Engine.js _process_reaction_queue() running task 66 { "tid": 66, "id": "rule-kpw0p0rl:R", "rule": "rule-kpw0p0rl", "__reaction": [RuleReaction#rule-kpw0p0rl:R], "next_step": 1, "status": 1, "ts": 1633288075480, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 1 }
2021-10-03T19:07:55.540Z Engine:NOTICE Resuming reaction Pantry Light<RESET> (rule-kpw0p0rl:R) from step 1
2021-10-03T19:07:55.540Z Engine:INFO Pantry Light<RESET> all actions completed.
2021-10-03T19:07:55.540Z Engine:5:1351:Engine.js _process_reaction_queue() task returned, new status -1; task 66
2021-10-03T19:07:55.541Z Engine:5:1386:Engine.js _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting
2021-10-03T19:08:22.586Z wsapi:INFO wsapi: connection from ::ffff:172.17.0.1
2021-10-03T19:08:30.307Z wsapi:INFO client "172.17.0.1#51" closed, code=1006, reason=
2021-10-03T19:08:30.416Z wsapi:INFO wsapi: connection from ::ffff:172.17.0.1
2021-10-03T19:08:31.621Z wsapi:INFO client "172.17.0.1#52" closed, code=1006, reason=
2021-10-03T19:08:31.705Z wsapi:INFO wsapi: connection from ::ffff:172.17.0.1Synology Docker MSR, Hubitat, Home Assistant, Homebridge
-
Well, unfortunately, the message doesn't really help me. It points to a line with a class declaration, no variable reference on it at all. If it's actually complaining about something inside the class declaration, it isn't detailed enough to figure out what in over 1300 lines of code in that class it may be. My usual lint (code checking) tools don't complain, and other browsers don't, so while I'd like to fix it, I don't really have a path to fixing it, and you have other options, so I'm afraid it's going to stay broken for now.
The 172 addresses are bridge addresses between your real network and the docker containers internal/virtual LAN.
-
@sweetgenius said in Safari Mac Rule Sets Menu after upgrade build 21275:
It appears if I open in a private window the error is not there either.
Kind of suggests something in your browser cache is a problem. Maybe try a hard refresh (always a good idea after an upgrade), and the usual debugging steps for this kind of thing: flush your browser cache and restart the browser, turn off all extensions, etc.
Safari 15.0 was officially released about two weeks ago, and there are lots of reports of problems with commonly-used web sites, so I have doubts. Do some Google searches. Other things perhaps to try here: https://apple.stackexchange.com/questions/427935/safari-15-0-error-message-a-problem-repeatedly-occurred-catalina-10-15-7
-
@toggledbits I agree, I think it's a browser issue. I have tried all the recommended fixes to no avail. Clear Caches, History, Hard Refresh, Reinstall etc.. Will see if they fix it in a later version of Safari. I have found if I keeping hitting refresh it I can get it to work or use a private window or other browser. So I have plenty of options.
Thanks for the suggestions.