@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
18481340-4d9c-4d0c-8027-49adfa28f32a-image.png
e0e1c895-a830-48d5-8346-cbae551b441d-image.png
This has been working flawlessly each year incl this year until... Tonight... nada.
Is this due to the holiday being late this year ie because today is the 22nd, not after the 22nd?
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)
Hi @toggledbits,
I have lots of logs with this:
<Engine:ERR> Assignment to alarm ignored -- expression-driven global cannot be set by assignmentAny hints to where look at to avoid this? Thanks.
Hi @toggledbits
I'd like to update my controllers with these new features, but I'm struggling to find any guidance in the docs - and in general to understand the context.
Could you please elaborate more? Thanks.
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!
In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
Thanks!
/Fanan
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
Unable to pull attributes into Global Expression (Hubitat)
-
I have begun my migration off of Vera and over to Hubitat. One device and one app at a time. I am working on my Netamo app/devices right now. The Netatmo Client App in Hubitat pulls all the information in and I can use the values within rules. However I am unable to use these value within an expression. Or at least a Global Expression. Honestly haven't tried a local one yet. In my screenshot below, the Global Expression as a value from the Vera Netatmo plugin, but when I try to change this to the Hubitat entity, there are no attributes to pull in. Below that is what I am able to see within the Rule itself.
-
What is shown in the Entities detail display for
hubitat>39?Regardless, that doesn't stop you from using them. That's just a tool to help make it easier to write the expression. You can still write it out:
getEntity( 'hubitat>39' ).attributes.humidity_sensor.value -
@toggledbits said in Unable to pull attributes into Global Expression (Hubitat):
What is shown in the Entities detail display for hubitat>39?
Ah. Good to know. I can write that out, or attempt to. Here is what is shown under the entity.
-
Strange. Have you done a hard refresh on the browser?
-
@toggledbits said in Unable to pull attributes into Global Expression (Hubitat):
Strange. Have you done a hard refresh on the browser?
Yes. And to add more to the confusion, in my Triggers, if the ==/<> option is changes, the Condition must be sustained for section is completely missing.
-
Actually. I think the changes is a bug. I tried to set my old Netatmo entity back in and even with that there is no Condition must be sustained option. Regardless of the entity, when the ==/<> (I forget what this is called) is set to changes, that field/option is missing. My original rule for this was imported from RfV.
EDIT: I have a work around. And steps to follow to see if you can reproduce it.
Set the operator to something other than changes and open the Conditions options
Change your operator to changes (BTW, the menu option is very small with the Conditions options open.)
Set your Condition must be sustained for xxxx value.
Close your Conditions options.
The work around works. This trigger must be sustained for 3 hours before being true.
Was running 21236-90dd714. Upgraded to 21237-e161aed and still seeing both issues. In fact my operators in general for any new rule are only showing me the above list now. Existing rules I get the full drop down list. I don't know what happened.
-
No, logically "changes" and "sustained for" cannot go together. "Changes" is an instantaneous at the moment the change occurs. It is therefore not capable of being "sustained" for any period of time. Also don't assume that just because Reactor for Vera allowed you to do something that (a) it was right, and (b) MSR will work the same. There are a lot of things in MSR that are fixed behaviors of things that should never have been in R4V.
Also, unless I'm certain what is causing a problem and can put in a fix, not every build is going to have a fix for every issue that may be being discussed. Your first issue doesn't happen for me, and I've never seen it, so in the absence of being able to reproduce it myself, I can't fix it, and that won't change until I can see it. The second issue is, I think, a misunderstanding, and also too new to make the build window even if it was a something to address/fix.
-
Oh I totally get it. Sorry if I came across as I was expecting it to be fixed in the newer build. That wasn't my intent. I just wanted to test a newer build JIC.
It makes sense that changes are immediate. What I'm doing is watching the internal temp reading from my Netatmo and if it hasn't changed in in 3 hours, then reboot the netatmo device. I suppose I could do this with a pulse and a expression. Setting the variable then compare the new reading to the previous reading every 3 hours. If they are == then reboot.
I'm happy to troubleshoot the Hubitat Expression issue with you. Is there anything I can run for you?
-
Something is definitely up with my Reactor. Any new rules that I create I only have a very short list of operator choices. I blew away my docker image and pulled a new one. I also tried going back to the generic 1.0.0. I tried via Incognito Mode and in a different browser in case it was a cookie issue. All had the same results, and it doesn't matter which hub I pull from.
What logs can/should I pull for you? Thinking back to the only changes I made yesterday. I installed the Netatmo Client app and drivers in my HE hub and presented them via the Maker API. I was changing my temperature related rules from the Vera device to the HE device. Outside of that, there weren't any real changes that I recall to Reactor. Oh. I upgraded from 21228 to 21236 earlier in the day. Then was presented with a 21236 again about an hour later. And then to 21237 late last night. But I don't think these are related.
-
@3rdstng Here's an approach:
Using the "delay reset" for 180 minutes (10,800 seconds) will hold the changes condition true for three hours. The group is set to NOT to invert the sense of the output.
When the temperature changes, and for three hours after, the condition will be true, so the rule will be false. If there are no changes for three consecutive hours, the condition goes false, so the rule will go true (set).
-
Thank you @toggledbits - There is something else going on too. I thought it was machine related, so I deleted my post. But after hard refreshing the browsers on my other machine, and testing on a 3rd machine, I'm still seeing the issue. I've restored my post, which is now a couple up from here. The operators list does not contain ==, <>, >=, etc. for brand new triggers. If I edit a trigger that is already there, I get all those operator choices. I cleared and reset all my settings in Chrome and still see it. Short of completely blowing away Reactor and creating a second/new instance, I'm not sure where to go. I have a feeling that if I went with the new Reactor docker, and I copy my config/rule files over, that the issue will come with it.
EDIT: Did the operators options code get an update? I was poking around and noticed that depending on what the triggers capability setting is set to, the operators are restricted to what is shown. I don't recall ever having this restriction/limitation before. For example I used to manually define the power_switch.state to T/F. Manually typing in the value to check again. But now my options are is TRUE, is FALSE, etc. Maybe my mind is just warped and I was used to seeing the full drop down list prior to now?
-
If you choose an attribute for which the data type is known, operators that do not apply to that datatype are removed. For example, if you choose a boolean attribute (like motion sensor state), the ==, <>, etc are removed, because you use is TRUE, is FALSE and is NULL to test that value type.
This is a change from the behavior of R4V, where all data was strings so you had to test for "0" or "1" on a boolean. MSR doesn't work that way.
Edit: to your other question, this was not a recent change. It happened around March 8.
-
@toggledbits said in Unable to pull attributes into Global Expression (Hubitat):
This is a change from the behavior of R4V, where all data was strings so you had to test for "0" or "1" on a boolean. MSR doesn't work that way.
THANK YOU! Everything had been imported from R4V, so my mind was still in the state of seeing everything. I thought I was having issues. Since I'm migrating off Vera and onto HE, I'm starting to see the changes between R4V and MSR. Glad I'm not having PC/browser/docker issues.
Getting back on topic. What can I provide you to get the Expressions drop down populated? If I choose a different entity, those options are presented. If I then switch back to the HE Netatmo entity, I still see the options from the other device. It appears to only be these Netatmo entities. Not sure if this will help, but here is where/how I installed the client and drivers.
[RELEASE] HubConnect Netatmo Weather Station Client (HubConnect not req'd)
![[RELEASE] HubConnect Netatmo Weather Station Client (HubConnect not req'd)](https://community.hubitat.com/uploads/default/optimized/3X/f/b/fb906f37c7e27f5b375b5fac65cd859edbc87ee6_2_1024x644.png)
I am pleased to announce the release of a brand new, Netatmo integration to Hubitat. This is NOT a ported app.. It is a brand-new integration, written nearly from the ground up. It features driver support for the Base Station, Outdoor Module, Wind Gauge, Rain Gauge, and Indoor Modules. Despite...
-
T toggledbits locked this topic on
