@toggledbits I understand that you do not perform testing on Mac computers but thought I'd share the following with you in case something can be done.
I started seeing these errors with version 24302. I thought that upgrading to 24343 would have fixed the issue but unfortunately not. I either have to close the browser or clear the cache for the errors to stop popping-up but they slowly come back.
I see these errors on the following browsers:
Safari 16.6.1 on macOS Big Sur Safari 18.1.1 on MacOS Sonoma DuckDuckGo 1.118.0 on macOS Big Sur and Sonoma Firefox 133.0.3 on macOS Big Sur Chrome 131.0.6778 on macOS Big SurHere are the errors
Safari while creating/updating an expression
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:21 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:29 reindexExpressions@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:32 @http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:608:40 dispatch@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:40040DuckDuckGo while clicking on status
http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:789:44 asyncFunctionResume@[native code] saveGridLayout@[native code] dispatchEvent@[native code] _triggerEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1401:30 _triggerAddEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1383:31 makeWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:968:30 addWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:388:24 placeWidgetAdder@http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:183:44Firefox while updating a rule
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:82:21 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:47:26 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1460:39 forEach@[native code] @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1459:58Chrome while creating/updating an expression
TypeError: Cannot read properties of undefined (reading 'getEditor') at RuleEditor.makeExprMenu (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:1788:86) at Object.handler (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:2174:54) at http://192.168.0.13:8111/client/MessageBus.js:98:44 at Array.forEach (<anonymous>) at MessageBus._sendToBus (http://192.168.0.13:8111/client/MessageBus.js:95:54) at MessageBus.send (http://192.168.0.13:8111/client/MessageBus.js:106:44) at ExpressionEditor.publish (http://192.168.0.13:8111/client/Observable.js:78:28) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:14) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:15) at ExpressionEditor.reindexExpressions (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:18) ``Not sure that it is the same issue but just got this on built 24302 when running a reaction for testing purpose. Despite the error message, the reaction ran properly.
Error: Command timeout (195 start_reaction)
at _ClientAPI._commandTimeout (http://192.168.2.163:8111/client/ClientAPI.js:552:136)
1a3422eb-d760-4609-a740-a40d04a6bab2-Screenshot 2024-12-29 231851.png
Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.
Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce
A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.
Hi
Having to rebuild my Linux Debian box as the SSD failed. And I have forgotten exactly what I did the first time to get it all setup.
I have Debian 12 up and running on the new SSD, I only have console no Desktop GUI.
I am trying to do the bare metal install for MSR. However I am not sure if I am meant to install nodejs whlist logged in as the root user or as the none root user with my name ?
I used putty and connected via SSH and logged in as root and I installed nodejs but I think this was wrong as when logged in as my user name and I do a node -v command it says node is not installed or doesn't show any version number anyway.
But when logged in as root and I do a node -v command it does show me its installed and displays the version number. maybe its a path issue for my username and he can't see node is installed?
So now I am thinking I should of installed node whilst logged in as my user name and not as the root user.
This is how I installed nodejs as whilst logged in as root
ac7bf6c3-23ad-46fc-8ada-44af6704e63e-image.png
Thanks in advance.
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.As the title says, here's my OpenAI Controller for Reactor:
OpenAI Controller per Reactor. Contribute to dbochicchio/reactor-openai development by creating an account on GitHub.
It supports both OpenAI and Azure OpenAI endpoints. You'll need keys/endpoints, according to each service.
The controller supports multiple models, and each one could be mapped as an entity.
It's quite easy to use, and responses can be stored in variables, for easy access. Or sent to another action (Text To Speech, another endpoint, etc).
9013ae50-fd68-42a2-87c3-97479132e465-image.png
80a88eec-7c89-464a-8196-690b4b72d044-image.png
Have fun with LLM into your scenes!
In Home Assistant I have an integration that if I add entities to it, I will get the following error in MSR as certain entity values I'm using in expressions are null for a moment. This is more or less cosmetic issue and happens very rarely as I rarely modify that integration on the hass side.
Screenshot 2024-11-28 at 22.20.41.png
And the expression is
Screenshot 2024-11-28 at 22.38.19.png
Could I "wrap" hass-entity shown above somewhat differently to prevent this error from happening? Using build 24302.
Hello
I am trying to set up Multi System Reactor to automate routines across multiple smart home devices & platforms (e.g., Home Assistant, SmartThings, and Hubitat). While I have successfully linked the systems; I am facing issues with:
-Delays in triggering actions on secondary devices.
-Inconsistent execution of complex logic conditions.
-Synchronization of states between devices when one system updates.
Is there a recommended way to optimize performance & confirm seamless state sharing across systems?
I have checked https://smarthome.community/category/22/multi-system-reactor-msbi guide for reference but still need advice.
Any tips on debugging or log analysis to pinpoint where the issue arises would also be appreciated.
Thank you !
I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.
Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.
( *Drag & drop of rule conditions have never worked on a mobile)
@toggledbits Since I have upgraded ZWaveJSController to 24293 from 24257 I am seeing entries related to registering action set_volume, but action is not defined by the capability 143 every time I restart Reactor.
The Siren seems to be doing what it is supposed to do. The volume levels are fine. Should I worry about it?
Reactor version 24302
ZWaveJSController version 24293
Z-Wave JS UI version 9.27.4
zwave-js version 14.3.4
I have the following ACL defined:
groups: admin: users: - admin applications: true api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: trueAnd I have authenticated to MSR as "admin" user. However, I'm getting "access denied" when trying to access http://*******:8111/api/v1/log
So what I'm missing, is my ACL incorrectly defined?
Using build 24302 on Docker.
Hi
I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.
They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.
This is how that device looks in the Ezlo API.
Devices Info:
_id: "10696001" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "level_sensor" subcategory: "" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Digital" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696001" deviceId: "10696001" hasGetter: true hasSetter: false name: "smoke_density" show: true valueType: "substance_amount" scale: "parts_per_million" value: 2.7472610473632812 valueFormatted: "2.75" status: "idle"There is also an Analog Gas sensor that one did import in to MSR OK.
68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png
Devices Info:
_id: "10696000" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "security_sensor" subcategory: "gas" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Analog" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696000" deviceId: "10696000" hasGetter: true hasSetter: false name: "gas_alarm" show: true valueType: "token" enum: 0: "no_gas" 1: "combustible_gas_detected" 2: "toxic_gas_detected" 3: "unknown" valueFormatted: "no_gas" value: "no_gas" status: "idle"And this is how this MQ2 Gas Sensor looks like on their dashboard:
Digital
cb77dfa3-4af5-4d06-9635-89207a716a89-image.png
Analog
4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png
They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!
And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.
THANKS.
A couple of things for you @toggledbits, since you mentioned that this release has new features and some tweaks are expected.
Local expressions cannot be deleted. Pushing the X button has no effect for me.
When cloning an entity action, the result is strange (first is cloned one, second is the original action):
a92ea094-9e2c-4aaa-bf47-2d07a6ffdbd0-image.png
When changing the action on the cloned element, the params are added to the original one. See screenshot:
92ac3011-83c8-466b-bd23-47d483ad7a52-image.png
Dark theme has a couple of strange contrasts. One is visible in the previous screenshots (white text on yellow background). Another one is in groups (blue text on blue background):
9b3c4988-53ef-44e6-9672-30e744cacb75-image.png
Overall, I found blue, yellow, red and green (in buttons and forms) to be too bright.
On the bright side:
I love the new script action: thank you! The dark theme is a great start to avoid getting blinded at night I promise I'll try very soon the new features around actions. Thanks!@toggledbits
I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:
I followed the new directions about npm
npm i --no-save --no-package-lock --omit dev
Any idea what the issue is?
Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)
Things I have tried:
Hard refresh
Different browser
Different computer
Restarting Reactor
Failed troubleshooting attempts:
No errors in Chrome console
No relevant errors in Reactor log (can still PM the full log file)
Reactor version: latest-24293-ea42a81d
Hardware: Odroid N2+
Linux version: Ubuntu 24.04.1 LTS
3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled
ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled
iPhone location or alternative.
-
Reposting here because core people seem to be here daily.
Hello Everyone,
I am using iPhone locator on Vera, and yesterday it stopped working. Looking at the logs, I can see the connection is refused, but nothing on my end changed. iPhone locator is really important in my particular setup, so I guess I have two questions.
Is it broken, or is it me?
I don't see anyone else saying there is an issue, but I am not sure how many people are still using it (or Vera for location) at this point. I installed it on a blank Vera test controller, same issue. It might be something with the iCloud account, but it works everywhere else.Is there something similar on another platform?
Mainly what I would like is the ability to force a poll of iCloud location on demand. I have a bunch of triggers setup, including magnetic sensors in my driveway to sense vehicles and determine if the motion is egress or ingress. These triggers in conjunction with MSR have been a great way to double check phone location, and I would hate to lose this functionality. It looks like HA might have something with "iCloud3". Is anyone using it?
Thanks,
Mike -
@therealdb Thanks DB. I also looked at that, but I will check it out more thoroughly.
I wanted to try to keep the force refresh option available, but looking quickly, I didn't think there was a way to do that. I really liked the behavior of asking the phone, "where do you think you are, and do me a favor and double-check just to be sure." Using that one feature stopped a lot of delayed or false location reports during a critical event, but in fairness, maybe this stuff has gotten good enough that it won't be an issue.
-
@mikereadington it’s constantly refreshing, so your use case doesn’t seems to be useful in my scenario.
@CatmanV2 yes, don’t use the messages as they come. You need to filter them. I’m using global variables to maintain the status, but maybe the new metadata could be enough.
-
Looks like it's an overall thing. I've just checked the two devices on OpenLuup. Both of them are reporting 'No Devices for this account, check network/credentials'
They can been seen on Find my. The user and pass are correct. Logs
2022-10-07 17:54:39.684 luup_log:55: IPhoneLocator: iCloud refused access, Check credentials ?
My logs only go back to yesterday but this appears consistent since then.
(I know I'm not sticking to the posting guides but I'm not actually asking for help simply confirming that it seems rather bust)
C
-
Final note I suspect: My device checked in 1707 05/10/2022 BST and has not checked out since
Mrs C's device checked out 0800 05/10/2022 BST and never checked in, although she came home at about 1800 that night (it was our wedding anniversary so we're pretty clear on that)So that narrows down the window a chunk....
C
-
@CatmanV2 Well, at least I know it was not just me. I knew this day was coming because he had said something in August when it was broken that he didn't know if it was fixable because of Apple's API. I am thinking they kicked everything that did not use 2FA authentication.
@therealdb I set up Owntracks on Hubitat because it was easy, and I could play with it. Looks like it is very flexible. How hard is it on the battery? I realize mileage will vary a lot on this, but that was a feature I liked about the iPhone locator app. It ran using Apple's "Find My" that was already running on the phone. It's slow to update, but if I needed to know where the phone was, I would force a poll of location from the app. Since I started refining my logic in MSR I have been using manual polling almost exclusively. Thanks again for the point in this direction.
-
Something of note from OwnTracks with iOS.
"Why do location publishes sometimes seem to cease to work?
Here's what happens:
If the app goes into Background, the connection is disconnected because the app cannot maintain the TCP connection in background.
If you bring the app back into foreground, the app will re-connect.
When a location change is recorded (no matter if manual, significant, move or region mode), a message is prepared and an attempt to connect to the broker is started. If there is an error, connect will be retried after 2, 4, 8, ..., 64, 64, .... seconds until it succeeds.
BUT...
If the application is in background or is sent to the background, retries are restarted eventually - depending on iOS' background execution model about every 10 minutes.
With automatic modes switched off, even when bringing the app to foreground, no new location updates are generated." -
@mikereadington said in iPhone location or alternative.:
I am thinking they kicked everything that did not use 2FA authentication.
Quite quite possible
C
-
@mikereadington and this precisely explains the issues I saw. And makes perfect sense (I'm engaged with a company that is developing an a for iOS and Apple's restrictions and what happens when an App backgrounds (read 'is stopped') are quite severe.
Taking this, and my own recent experience into account, I don't think Owntracks is going to be viable. In fact, given the limitations from Apple I'm not sure anything is going to be viable for a geofence
C
-
iOS has a background system to preserve battery life. It’s designed to be reliable and to not impact battery life. If you define your zones (I have home and office) at the very same moment you’ll cross the boundaries, a message is sent. I’m on my 2nd year with the system and never missed a bit. I also have a Bayesian sensor to detect if I’m connected to WiFi, and this is used as a second factor to confirm I’m home. But generally speaking, the entry/exit is totally demanded to OwnTracks.
-
@therealdb It is indeed so designed, but that's not what I am seeing in terms of behaviour. Of course I may have misconfigured it on my phone so I am happy to be corrected!
(but I'll probably bug you for help)
But not right now
C
-
@CatmanV2 I concur with @therealdb here, I've been using the OwnTracks on iOS via the Hubitat app integrations and it works well. I also use, as a secondary, a Home Assistant integration called iCloud3 which mitigates the 2FA issues you found with iPhone Locator. I've seen no noticeable battery issues (once I had iC3 configured correctly.)
@toggledbits got me into OwnTracks when he had his Logo trial up and running.
-
Well I fully expect to be wrong I know that Geolocation is one of the use cases that Apple permit (or at least tolerate) in their process (and it's documented in the Owntracks literature as well as being the workaround for our devs.
I strongly suspect I fubarred the config somewhere (possibly as basic as not allowing full location services, for example). I had a crack this morning and I have the phone claiming it's connected, and reactor claiming it's connected (yay)
I need to get the entity installed but that's another day
C
-
Trying to follow the posting guidelines.....
- id: mqqt enabled: true implementation: MQTTController name: Mosquito config: source: "mqtt://192.168.70.249:8883/" username: xxxxx password: xxxxx entities: catman_iphone: name: "Catman Phone" topic: FFCEB043-B975-490E-B051-198473F6A504 uses_template: owntracks_in_region
Claims to be valid YAML in https://yamlchecker.com/
But when I add the last 4 lines to my reactor.yaml msr will not start:
Reactor log stops:
[latest-22274]2022-10-08T17:32:39.316Z <Engine:NOTICE> [Engine]Engine#1 has shut down. [latest-22274]2022-10-08T17:32:39.316Z <app:NOTICE> Closing Structure... [latest-22274]2022-10-08T17:32:39.317Z <Structure:INFO> Structure#1 Stopping controllers... [latest-22274]2022-10-08T17:32:39.317Z <VeraController:NOTICE> VeraController#vera stopping [latest-22274]2022-10-08T17:32:39.321Z <VeraController:ERR> Controller VeraController#vera is off-line! [latest-22274]2022-10-08T17:32:39.366Z <MQTTController:NOTICE> MQTTController#mqqt stopping, sending LWT [latest-22274]2022-10-08T17:32:39.366Z <DynamicGroupController:NOTICE> DynamicGroupController#groups stopping [latest-22274]2022-10-08T17:32:39.369Z <DynamicGroupController:ERR> Controller DynamicGroupController#groups is off-line! [latest-22274]2022-10-08T17:32:39.369Z <SystemController:NOTICE> SystemController#reactor_system stopping [latest-22274]2022-10-08T17:32:39.371Z <SystemController:ERR> Controller SystemController#reactor_system is off-line! [latest-22274]2022-10-08T17:32:39.372Z <Structure:INFO> Structure#1 Final data sync... [latest-22274]2022-10-08T17:32:39.379Z <Structure:NOTICE> Structure Structure#1 stopped [latest-22274]2022-10-08T17:32:39.379Z <app:NOTICE> Stopping timers... [latest-22274]2022-10-08T17:32:39.380Z <app:NOTICE> Shutdown complete, process ID 27723
As soon as I replace the original version of reactor.yaml
- id: mqqt enabled: true implementation: MQTTController name: Mosquito config: source: "mqtt://192.168.70.249:8883/" username: xxxx password: xxxx
Everything springs to life.
I can't see an error in my syntax. Do I need to have the region in there (although I've tried both with and without)
It's going to be something obvious / stupid but hopefully I'm learning at least a little
TIA
C
-
Thanks
Tried
entities: catman_iphone: name: "Catman Phone" topic: "FFCEB043-B975-490E-B051-198473F6A504" uses_template: owntracks_in_region regionName: Home
and
entities: "catman_iphone": name: "Catman Phone" topic: "FFCEB043-B975-490E-B051-198473F6A504" uses_template: owntracks_in_region regionName: Home
With no discernible difference
C