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.0Hi!
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
HomeAsssistant Weather changed.... Global expression no longer functioning
-
Good morning,
So Home Assistant decided to change the default weather home format that I've been using for the past year and a half. I had two Global Expressions set up to pull the high and low temp forecast for the day. Now it's pulling null values.In the dev tools, it now uses a new service (Weather. get forecasts), plural, where the old Weather.get forecast is depreciated and now longer functions.
It shows a templow field, and a temperature field, which I presume is the forecast high.
When I head back over to MSR, I'm having a hard time finding those values in the Entities tab.
wx.asoftime=null wx.ceiling=null wx.ceiling_unit=null wx.cloud_cover=null wx.condition_code=null wx.description="partlycloudy" wx.feels_like=null wx.humidity=57 wx.humidity_unit="%" wx.icon=null wx.location=null wx.precipitation_1hr=null wx.precipitation_24hr=null wx.precipitation_other=null wx.precipitation_type=null wx.precipitation_unit="in" wx.pressure=30 wx.pressure_unit="inHg" wx.temperature=55 wx.temperature_unit="°F" wx.visibility=null wx.visibility_unit="mi" wx.wind_compass=210.3 wx.wind_conditions=null wx.wind_direction="SSW" wx.wind_gust=null wx.wind_speed=6.28 wx.wind_speed_unit="mph" x_hass.domain="weather" x_hass.entity_id="weather.forecast_home" x_hass.services=["weather"] x_hass.state="partlycloudy" x_hass_attr.attribution="Weather forecast from met.no, delivered by the Norwegian Meteorological Institute." x_hass_attr.cloud_coverage=85.9 x_hass_attr.dew_point=40 x_hass_attr.friendly_name="New Windsor Weather" x_hass_attr.humidity=57 x_hass_attr.precipitation_unit="in" x_hass_attr.pressure=30 x_hass_attr.pressure_unit="inHg" x_hass_attr.supported_features=3 x_hass_attr.temperature=55 x_hass_attr.temperature_unit="°F" x_hass_attr.visibility_unit="mi" x_hass_attr.wind_bearing=210.3 x_hass_attr.wind_speed=6.28 x_hass_attr.wind_speed_unit="mph"
There is a x_hass_attr.temperature, but that appears to be the current temperature, not the high that I found on the dev tools screenshot.
Any ideas?
Running:
Core
2024.4.3
Supervisor
2024.04.0
Operating System
12.2
Frontend
20240404.2MSR: latest-24057-e9add9f5
-
Chalk it up to Home Assistant's legacy of breaking changes. The whole matter of service calls being able to return data came about in 2023.7 but didn't work until 2023.12 for the websocket API, and didn't apply to anything anyone seemed to care about until now. So current Reactor doesn't store that response anywhere, and in fact doesn't know to ask for it, and the service you're calling requires it, so you're probably getting an error in the log that you haven't spotted (always look at the logs when things don't work as expected!).
Until I get a fix for this into HassController, the only remedy right now is to downgrade your Hass back to 2024.3 or earlier.
P.S. This is why I say in the documentation and have HassController complain bitterly when you're running a Hass version that isn't yet supported/verified. I assume you got a warning about that, too.
-
@toggledbits said in HomeAsssistant Weather changed.... Global expression no longer functioning:
Chalk it up to Home Assistant's legacy of breaking changes. The whole matter of service calls being able to return data came about in 2023.7 but didn't work until 2023.12 for the websocket API, and didn't apply to anything anyone seemed to care about until now. So current Reactor doesn't store that response anywhere, and in fact doesn't know to ask for it, and the service you're calling requires it, so you're probably getting an error in the log that you haven't spotted (always look at the logs when things don't work as expected!).
Until I get a fix for this into HassController, the only remedy right now is to downgrade your Hass back to 2024.3 or earlier.
P.S. This is why I say in the documentation and have HassController complain bitterly when you're running a Hass version that isn't yet supported/verified. I assume you got a warning about that, too.
Thanks Patrick, that's pretty much what I had figured. It wouldn't be the first time that HAAS has changed something 6 months ago and broke my setup.
I did see the notice yes, however, I think there was another notice I got from HAAS that told me if I didn't upgrade that something else would stop functioning. Always a balancing act unfortunatley.
Let me know when you come out with a version of HaasController that addresses this, and I'll gladly test it out for you.
-
I had the same problem and moved to a rule with openweathermap.
I capture the response in a global variable and use it in my automation. I even have a couple of virtual devices to remap it. Less dependent on HASS and OWM has better forecast for me. Free API keys if you make two separate calls for current and forecast.
-
@therealdb said in HomeAsssistant Weather changed.... Global expression no longer functioning:
I had the same problem and moved to a rule with openweathermap.
I capture the response in a global variable and use it in my automation. I even have a couple of virtual devices to remap it. Less dependent on HASS and OWM has better forecast for me. Free API keys if you make two separate calls for current and forecast.
I tried that, and you're right, in theory it should work, however, OWM shows "null" for forecast low for me.
-
@tamorgen are you installed bare-metal, or running in docker?
-
-
Service responses are addressed in build 24115 (just released)
-
it's cnt. Since I just want the next forecast, I'm limiting it to 5.
https://api.openweathermap.org/data/2.5/forecast?lat=X&lon=X&units=metric&appid=X&lang=en&cnt=5
@gwp1 is right, but if you don't want to use onecall (very helpful to be honest) and want to make two calls, you'll be good with the free one. As I said, I just want forecast (for cloud, rain and min/max temp), so it's just one call for me.
Initially I wanted to make a dedicated controller for OWM (using the native weather station capability), but it's just one call, so it's easier this way.
-
I'm installed bare-metal.
-
So it does appear to call the service now. Now I have to figure out how to get it into my expression.
This output was from going into the Entities tab, and running the service manually. If I want to get the forecast and get the high/low temps, will i need to run an action daily to call the service, or will the expression do it for me? I don't see any documentation yet on the Reactor installation instructions for Service responses.
wx.asoftime=null
wx.ceiling=null
wx.ceiling_unit=null
wx.cloud_cover=null
wx.condition_code=null
wx.description="cloudy"
wx.feels_like=null
wx.humidity=60
wx.humidity_unit="%"
wx.icon=null
wx.location=null
wx.precipitation_1hr=null
wx.precipitation_24hr=null
wx.precipitation_other=null
wx.precipitation_type=null
wx.precipitation_unit="in"
wx.pressure=30.26
wx.pressure_unit="inHg"
wx.temperature=41
wx.temperature_unit="°F"
wx.visibility=null
wx.visibility_unit="mi"
wx.wind_compass=13.7
wx.wind_conditions=null
wx.wind_direction="N"
wx.wind_gust=null
wx.wind_speed=8.26
wx.wind_speed_unit="mph"
x_hass.domain="weather"
x_hass.entity_id="weather.forecast_home"
x_hass.services=["weather"]
x_hass.state="cloudy"
x_hass_attr.attribution="Weather forecast from met.no, delivered by the Norwegian Meteorological Institute."
x_hass_attr.cloud_coverage=89.8
x_hass_attr.dew_point=28
x_hass_attr.friendly_name="New Windsor Weather"
x_hass_attr.humidity=60
x_hass_attr.precipitation_unit="in"
x_hass_attr.pressure=30.26
x_hass_attr.pressure_unit="inHg"
x_hass_attr.supported_features=3
x_hass_attr.temperature=41
x_hass_attr.temperature_unit="°F"
x_hass_attr.visibility_unit="mi"
x_hass_attr.wind_bearing=13.7
x_hass_attr.wind_speed=8.26
x_hass_attr.wind_speed_unit="mph"
x_hass.last_response={"service":"weather.get_forecasts","since":1714043894115,"response":{"weather.forecast_home":{"forecast":[{"condition":"partlycloudy","datetime":"2024-04-25T16:00:00+00:00","wind_bearing":24,"temperature":57,"templow":41,"wind_speed":8.26,"precipitation":0,"humidity":51},{"condition":"sunny","datetime":"2024-04-26T16:00:00+00:00","wind_bearing":130.1,"temperature":61,"templow":41,"wind_speed":10.5,"precipitation":0,"humidity":30},{"condition":"cloudy","datetime":"2024-04-27T16:00:00+00:00","wind_bearing":142.8,"temperature":56,"templow":42,"wind_speed":10.31,"precipitation":0,"humidity":59},{"condition":"sunny","datetime":"2024-04-28T16:00:00+00:00","wind_bearing":234.2,"temperature":78,"templow":47,"wind_speed":7.15,"precipitation":0,"humidity":49},{"condition":"partlycloudy","datetime":"2024-04-29T16:00:00+00:00","wind_bearing":239.6,"temperature":86,"templow":62,"wind_speed":6.28,"precipitation":0,"humidity":42},{"condition":"cloudy","datetime":"2024-04-30T16:00:00+00:00","wind_bearing":257.4,"temperature":85,"templow":67,"wind_speed":8.08,"precipitation":0.02,"humidity":39}]}}}My call was for daily, so it shows a forecast for 5 days. Somehow I need to distinguish just today's forecast.
-
The response is stored on the target Reactor entity (that's entity from which you make the service call, unless you are using
call_service
from the system entity, in which case you have to specify a target). Thex_hass.last_response
attribute is used to store the returned response. It is not processed in any way, it is stored as it is received(so it will always be a string).I think the rest of the work is pretty much the same as how you'd handle a response from an HTTP request, and you've probably done it all before, but I'll spell it out for the benefit of other future readers.
If you copy-paste the response into a beautifier like jsonlint.com it will pretty-print the object so it's easier to discern its structure. The forecast lives in an array called
forecast
, and the array seems to have the current day's forecast as the first element (i.e. it's sorted by date, ascending). An unfortunate choice on the API's part is that they chose to name a key in their responseweather.forecast_home
— the dot in the key name will make it just a little harder to navigate through the object, because dot is a special syntax character in the expression language for accessing elements in object. We'll have to use an alternate syntax, which I'll illustrate with the example expression below that brings everything together up to this point. I break it into two parts to keep it more readable and easy to follow:r = getEntity( 'entity-canonical-id' ).attributes.x_hass.last_response, forecast_today = r.response['weather.forecast_home'].forecast[0]
Although this is two lines, it is implemented in one (probably global) expression. In the first line, we use an expression local variable
r
to fetch the response data from the entity. In the second line, we traverse the data inr
to get to the forecast data. We use['name']
syntax instead of.name
syntax to access the property with keyweather.forecast_home
. The[0]
at the end simply gets the first element (they are numbered from 0 in our expression language) of theforecast
array.At this point, the expression result would be an object containing the first forecast. You can add a further line to this expression to return one value from the forecast if you only need one, or create multiple new expressions that use the result of this expression if you need more than one value.
condition = forecast_today.condition templow = forecast_today.tempLow
Overall, I'd make one rule to periodically call the service and fetch the weather, with whatever frequency suits you (i.e. it only does the fetch). I'd make
forecast_today
above a global expression. The parts of the forecast you need could be drawn out fromforecast_today
using other global expressions or in rule expressions. When the query rule causes an update tox_hass.last_response
, the engine will re-evaluate theforecast_today
expression to parse the result to the single forecast object. Other expression evaluations will be triggered by a change in that object, and that, of course, will cause evaluation of rules' triggers that involve those variables. -
Looks like I may be missing something....
I tried it as you showed it, putting my cannonical ID in place.
It's giving me a response error "Last value: (error) Unexpected token o in JSON at position 1"
I then tried splitting up the lines, but that doesn't seem to work either.
It's giving me an error about an unexpected token o in JSON at position 1 as well, however, for the second one, it gives me "Last value: (error) Invalid scope in reference to member response of (object)null". I suspect the first method is the correct one, but I must have something incorrect in the format.
-
-