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.
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
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.
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.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
Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.
What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?
Running:
Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]HAAS:
RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0
Hi!
Is it possible to generate two additional log files, the first being the replica of what is displayed on screen by the Rule History widgets and the other with Recently Changed Entities?
And could I configure the generation of one file per day, and delete the older ones? For example, store the last 5 days?
And being more ambitious, does Windget have an icon to open these TXT files in the navigated?
Well, we're approaching Christmas, so here's my request to Santa Claus @toggledbits 🙂
Hi @toggledbits
I'm working on a controller to generate llm response from a prompt in reactor. I have http response coming thru an http request action at the moment, capturing the response inside a local variable. So, it's practically sync.
I want to create a controller, so I don't have to rely on a proxy (and have a simpler architecture), and duplicate absurd http actions, but AFAIK in the current implementation, actions are async only. But if I have multiple requests going on, I cannot be sure what it's really inside an attribute. I also thought that something like a correlation id when sending the request could be used to identity multiple responses, but I wanted to double check with you before starting with something too complicated. I also noticed that some actions in home assistant (ie forecast) are sync and I'm wondering if you have any plan or hint to address this situation. Thanks.
Thanks.
@togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.
Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.
Thanks in advance.
Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3
[MSR] reactor-mqtt-contrib package for additional MQTT templates
-
@toggledbits said in [MSR] reactor-mqtt-contrib package for additional MQTT templates:
@therealdb this may need a bit more documentation, since the relevance of
prefixandtopicaren't immediately clear (at least, not to me) without looking at the template itself and seeing how they are used, and likely the phone configuration as well (i.e. describe how configuration fields on the phone may appear in the final event topic).It’s in the readme. Maybe, when you’ll build an UI, we could provide descriptive text for parameters.
-
Version 22350 released.
What's new:- shelly_button1: for Shelly Button 1 (battery powered button) - all the button modes (short, long, double, triple) are supported.
- fullykiosk: to handle messages coming from FullyKiosk. You'll have battery and charging status, screen brightness and current app.
What's fixed:
- query for all shelly template
- owntracks: trying to better handle null values/spurious messages.
How to update: just replace the files and restart Reactor.
-
@therealdb I grabbed the latest
owntracks_sensorand dropped it on top of the existing. (Yes, being late and I'm exhausted I failed to backup the original template.)owntracks_iphone14p: #entity ID - must be unique name: "iPhone14p J2A" # friendly name prefix: "msrmqtt" topic: "iphone14p-j2a" uses_template: "owntracks_sensor" homeRegionName: "Home" # owntracks_iphone8: #entity ID - must be unique name: "iPhone8 location" # friendly name prefix: "msrmqtt" topic: "iphone8-j2a" uses_template: "owntracks_sensor" homeRegionName: "Home" # owntracks_iphone14jay: #entity ID - must be unique name: "iPhone14max Jay" # friendly name prefix: "msrmqtt" topic: "iphone14max-jay" uses_template: "owntracks_sensor" homeRegionName: "CoralBerry" # owntracks_iphone14jen: #entity ID - must be unique name: "iPhone14 Jen" # friendly name prefix: "msrmqtt" topic: "iphone14-jen" uses_template: "owntracks_sensor" homeRegionName: "CoralBerry" # owntracks_iphone14addie: #entity ID - must be unique name: "iPhone14 Addie" # friendly name prefix: "msrmqtt" topic: "iphone14-addie" uses_template: "owntracks_sensor" homeRegionName: "CoralBerry" # owntracks_iphone14bella: #entity ID - must be unique name: "iPhone14 Bella" # friendly name prefix: "msrmqtt" topic: "iphone14-bella" uses_template: "owntracks_sensor" homeRegionName: "CoralBerry"That's my config... and this is my log since replacing/restarting:
... le" content="{"groups": [], "environmentKey" ... ^ [-] [latest-22349]2022-12-19T04:51:40.735Z <MQTTController:CRIT> YAMLException: end of the stream or a document separator is expected at line 21, column 66: ... le" content="{"groups": [], "environmentKey" ... ^ [-] YAMLException: end of the stream or a document separator is expected at line 21, column 66: ... le" content="{"groups": [], "environmentKey" ... ^ at generateError (/home/reactor/Documents/reactor/node_modules/js-yaml/lib/js-yaml/loader.js:167:10) at throwError (/home/reactor/Documents/reactor/node_modules/js-yaml/lib/js-yaml/loader.js:173:9) at readDocument (/home/reactor/Documents/reactor/node_modules/js-yaml/lib/js-yaml/loader.js:1545:5) at loadDocuments (/home/reactor/Documents/reactor/node_modules/js-yaml/lib/js-yaml/loader.js:1588:5) at load (/home/reactor/Documents/reactor/node_modules/js-yaml/lib/js-yaml/loader.js:1614:19) at Object.safeLoad (/home/reactor/Documents/reactor/node_modules/js-yaml/lib/js-yaml/loader.js:1637:10) at MQTTController._load_implementation (/home/reactor/Documents/reactor/ext/MQTTController/MQTTController.js:753:38) at async MQTTController.start (/home/reactor/Documents/reactor/ext/MQTTController/MQTTController.js:81:13) [latest-22349]2022-12-19T04:51:40.744Z <MQTTController:ERR> MQTTController#mqtt2 can't read/load templates from /home/reactor/Documents/reactor/config/mqtt_templates/owntracks_sensor.yaml: [YAMLException] end of the stream or a document separator is expected at line 21, column 66: ... le" content="{"groups": [], "environmentKey" ... ^ [-] [latest-22349]2022-12-19T04:51:40.754Z <MQTTController:CRIT> YAMLException: end of the stream or a document separator is expected at line 21, column 66: ... le" content="{"groups": [], "environmentKey" ... ^ [-] YAMLException: end of the stream or a document separator is expected at line 21, column 66: ... le" content="{"groups": [], "environmentKey" ... ^ at generateError (/home/reactor/Documents/reactor/node_modules/js-yaml/lib/js-yaml/loader.js:167:10) at throwError (/home/reactor/Documents/reactor/node_modules/js-yaml/lib/js-yaml/loader.js:173:9) at readDocument (/home/reactor/Documents/reactor/node_modules/js-yaml/lib/js-yaml/loader.js:1545:5) at loadDocuments (/home/reactor/Documents/reactor/node_modules/js-yaml/lib/js-yaml/loader.js:1588:5) at load (/home/reactor/Documents/reactor/node_modules/js-yaml/lib/js-yaml/loader.js:1614:19) at Object.safeLoad (/home/reactor/Documents/reactor/node_modules/js-yaml/lib/js-yaml/loader.js:1637:10) at MQTTController._load_implementation (/home/reactor/Documents/reactor/ext/MQTTController/MQTTController.js:753:38) at async MQTTController.start (/home/reactor/Documents/reactor/ext/MQTTController/MQTTController.js:81:13) [latest-22349]2022-12-19T04:51:40.759Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.198:8123/api/websocket [latest-22349]2022-12-19T04:51:40.766Z <MQTTController:INFO> MQTTController#mqtt instance topic ident is mqtt [latest-22349]2022-12-19T04:51:40.767Z <Controller:INFO> MQTTController#mqtt 0 dead entities older than 86400000s purged [latest-22349]2022-12-19T04:51:40.769Z <MQTTController:NOTICE> MQTTController#mqtt connecting to broker at mqtt://192.168.1.198:1883/ [latest-22349]2022-12-19T04:51:40.843Z <MQTTController:INFO> MQTTController#mqtt2 instance topic ident is mqtt2 [latest-22349]2022-12-19T04:51:40.844Z <MQTTController:ERR> MQTTController#mqtt2 entity owntracks_iphone14p uses_template=owntracks_sensor, template not defined [latest-22349]2022-12-19T04:51:40.853Z <MQTTController:ERR> MQTTController#mqtt2 entity owntracks_iphone8 uses_template=owntracks_sensor, template not defined [latest-22349]2022-12-19T04:51:40.890Z <MQTTController:ERR> MQTTController#mqtt2 entity owntracks_iphone14jay uses_template=owntracks_sensor, template not defined [latest-22349]2022-12-19T04:51:40.901Z <MQTTController:ERR> MQTTController#mqtt2 entity owntracks_iphone14jen uses_template=owntracks_sensor, template not defined [latest-22349]2022-12-19T04:51:40.914Z <MQTTController:ERR> MQTTController#mqtt2 entity owntracks_iphone14addie uses_template=owntracks_sensor, template not defined [latest-22349]2022-12-19T04:51:40.923Z <MQTTController:ERR> MQTTController#mqtt2 entity owntracks_iphone14bella uses_template=owntracks_sensor, template not defined [latest-22349]2022-12-19T04:51:40.944Z <MQTTController:NOTICE> MQTTController#mqtt2 device owntracks_iphone14addie no longer available, marking BinarySensor#mqtt2>owntracks_iphone14addie for removal [latest-22349]2022-12-19T04:51:40.952Z <MQTTController:NOTICE> MQTTController#mqtt2 device owntracks_iphone14bella no longer available, marking BinarySensor#mqtt2>owntracks_iphone14bella for removal [latest-22349]2022-12-19T04:51:40.960Z <MQTTController:NOTICE> MQTTController#mqtt2 device owntracks_iphone14jay no longer available, marking BinarySensor#mqtt2>owntracks_iphone14jay for removal [latest-22349]2022-12-19T04:51:40.967Z <MQTTController:NOTICE> MQTTController#mqtt2 device owntracks_iphone14jen no longer available, marking BinarySensor#mqtt2>owntracks_iphone14jen for removal [latest-22349]2022-12-19T04:51:40.974Z <MQTTController:NOTICE> MQTTController#mqtt2 device owntracks_iphone14p no longer available, marking BinarySensor#mqtt2>owntracks_iphone14p for removal [latest-22349]2022-12-19T04:51:40.980Z <MQTTController:NOTICE> MQTTController#mqtt2 device owntracks_iphone8 no longer available, marking BinarySensor#mqtt2>owntracks_iphone8 for removal [latest-22349]2022-12-19T04:51:40.987Z <Controller:INFO> MQTTController#mqtt2 0 dead entities older than 86400000s purged [latest-22349]2022-12-19T04:51:40.988Z <MQTTController:NOTICE> MQTTController#mqtt2 connecting to broker at mqtts://7ef71f0117fe40d28c2df12205c4a0d0.s2.eu.hivemq.cloud:8883 -
@therealdb Stand down - I refetched the template file and replaced and everything is fine.
Bad download, perhaps?
Hubitat C-7 2.3.9.193
Home Assistant 2024.10.4
running ZST10-700 fw 7.18.3
MSR on RPi4 bare metal Model B 2GBs, SSD
MSR: latest-24302-751a06b6
MQTTController: 24257
ZWave Controller: 23257 -
@gwp1 said in [MSR] reactor-mqtt-contrib package for additional MQTT templates:
Bad download, perhaps?
Maybe. I'll start packing them in zip files very soon, since MQTTController has the ability to get them from a compressed zip file. I'll do a proper release and things should be easier going on.
-
@therealdb Many thanks to you and @toggledbits for the combined efforts on this specific app.
I've convinced a friend to join us here in the world of MSR. I'd originally written up a
reactor.yamlthat included his Hubitat and VeraSecure controllers so he could just drop it in and go. I updated that file with multiple entities for each member of his family, had him install MQTTController, and drop the updated version of the config file into his MSR.Created an accompanying install doc for the iOS app customized to their setup and it's working brilliantly. His phone is connected to my HiveMQ cluster which connects his household and mine together so we can do shared presence automations across homes.
Love this stuff!
EDIT: took it a step further and offloaded my OwnTracks config file, edited a couple details (UserID, etc) and sent it to all members of his family. He added it to OwnTracks and everyone is identical in setup as far as Regions goes and everything is working smashingly.
STILL love this stuff
-
I've pushed a new version of my templates, with small fixes everywhere, plus notHomeRegionName to configure the "not home" state (ie: be consistent with Home Assistant, that's using "not_home", if you want) and better handling in general of events. Thanks to @CatmanV2 for the samples!
-
T toggledbits locked this topic on
-
I've just updated a bunch of templates, and added:
- shelly_relay_simple: you know, a simple template for a shelly relay
- shelly_scenecontroller: to map Shellies as scene controllers/buttons
- shelly_uni_adc: to map Shelly Uni's capabilities to measure ADC.
GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
-
v 24111 with support for wifi_status just posted to https://github.com/dbochicchio/reactor-mqtt-contrib.
My system is stable at the moment and I'm not throwing new things at it, so there is no need for new templates. Let me know if you need a particular template or feel free to contribute.
-
v 24146 is out.
Mainly refactoring, with the addition of the first Shelly Gen 3 device (a relay).
GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
-
I got a tons of new Gen3 devices, so expect lots of new templates!
In the meanwhile, v 24210 is online https://github.com/dbochicchio/reactor-mqtt-contrib/releases/tag/24210
New shelly_relay_power_gen3 to get power meters via Gen3 devices and a couple of fixes here and there.
-
New 24258 released today:
Release 24258 · dbochicchio/reactor-mqtt-contrib
Requires Reactor 24257. New templates for HomeKey-ESP32. power_source capability for Fully Kiosk
Requires Reactor 24257.
- New template for HomeKey-ESP32 (more on that very soon)
- power_source capability for Fully Kiosk
-
T therealdb unlocked this topic on
