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
@toggledbits I have noticed after upgrading both Reactor and ZWaveJSController to version 24257 that two of my devices/entities, TILT-ZWAVE2.5-ECO and Zooz ZSE18, had their entity re-named in an unusual way and also appears to be duplicated.
Reactor version 24257
ZWaveJSController version 24257
Z-Wave JS UI version 9.18.1
zwave-js version 13.2.0
Vestibule Motion Sensor State attributes/partial screenshot of entities it created. All entities have the same attributes.
motion_sensor.state=true x_zwave_values.Notification_Home_Security_Motion_sensor_status=8 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=23 zwave_device.valueId=[113,"Notification","Home Security","Home Security","Motion sensor status","Motion sensor status"] zwave_device.version_info=nullTilt Sensor Door State and Tilt Sensor Door State Simple attributes/partial screenshot of entities it created. All entities have similar attributes with exception of x_zwave_values.Notification_Access_Control_Door_State = 22 or 23.
tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state_simple=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state_simple=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=nullMulti-System Reactor Developer Preview AVAILABLE
-
And 21051 is now available.
-
I will look into that!
Edit: It looks like the
jobsobject is dropped on Vera Luup when it's empty, but is always present on openLuup. Since the comparison to see if a value changes doesn't "go deep" on objects and arrays, it sees two empty objects as different every time they are presented (using JS's comparison operator), and the scene is being presented on each update even though outwardly there don't appear to be any changes. So two small diffs between Vera Luup and openLuup contributing.I'm just going to suppress anything that isn't a primitive and leave it at that. Deep inspection of objects and arrays isn't likely to be valuable or necessary.
-
@toggledbits said in Multi-System Reactor Developer Preview AVAILABLE:
I'm getting ready to assemble today's build (21051). I think I have everything urgent covered, with some PRs left open for confirmation. There's one more I want to try to address before I roll it up and out for the day.
This build also includes:
- Fix for condition trigger repeating when a sustained-for delay applies (#30);
- Fix an error on import (#29);
- Fix an error on Hass caused by an unhandled attribute (#27);
- New units configuration value "uk" (#31), as well as more granular control over units (if imperial, metric, or uk isn't enough, you can now set units by use class; per device/attribute is planned and part of the architecture as well);
- Fix elevation computation problem in sunrise/set data (mangles angles if elev configured <> 0) (#34);
- Now with working SMTP, Prowl, Pushover and Syslog notifications;
- Notification forwarding for Hubitat (see docs for configuration details);
- many documentation fixes and upgrades.
Looking good, squashing those bugs. I will keep reporting anything I find. Just set up SMTP. Works great!
-
For being a "Developer preview" it is quite solid. After some minor issues yesterday and have been solved with 21051, I have re-built most of my Reactor-sensors in Vera in the MSR and it is working fine. They are now disabled in the Vera and let's see how it goes in the coming days
-
Hi! I have really looking forward to this, MSR is the sole reason I have been trying to wrap my head around Home Assistant.
For now I am running Hassio on a VM at my Win10 "home server"
If I read the information right, I can't run MSR on Windows at the moment? -
I'm close. I think by tomorrow or Wednesday I'll have the cross-platform issues nailed down.
-
Version 21054 now available.
- Fix 0000020: Play button doesn't run cover action (Fibaro-specific issue)
- Fix 0000034: Sunrise/sunset conditions over midnight don't trigger in the morning
- Fix 0000041: VeraController has no thermostat mapping (generic done; specific versions will almost surely be needed)
- Fix 0000044: Time conditions spanning midnight don't trigger in the morning
- Fix 0000045: Importer brings root group with options in, but root group options are not editable in MSR
- Fix 0000046: Hubitat configuration for URL needs to go deeper (IP and access token insufficient)
- Fix 0000047: VeraController rgb_color capability has attributes but no actions
- Fix 0000048: VeraController has no mapping for Harmony plugin
A couple of side notes:
- The API functions mentioned here are integrated in this version;
- This version runs on Windows, and there are draft instructions for how to get it installed.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@toggledbits said in Multi-System Reactor Developer Preview AVAILABLE:
- Fix 0000041: VeraController has no thermostat mapping (generic done; specific versions will almost surely be needed)
Is it possible to get thermostat (climate) mappings for HassController?
-
Version 21055 now available
- 0000048 - No support for Harmony plugin or devices (basic support); related PR 0000053 still open (details).
- 0000049 - Version 21054 missing SMTP
- 0000051 - Show reaction ID on (Global) Reactions detail card
- 0000054 - ALTHUE Vera plugin mapping (basic support); please comment on this PR with issues
- 0000055 - Telegram plugin mapping; please comment on this PR with issues
Resolved, but left open for confirmation/feedback (comment on PR as needed; will be closed if not further comments):
- 0000053 - Harmony device details
- 0000052 - Thermostat attributes and actions for Horstmann thermostat
- 0000045 - Importer will bring in options on trigger (root) group, but you can't edit them
- 0000005 - Set Variable action not yet implemented; now has completely untested implementation.
-
Pi4 (2GB RAM) arrived today. can't wait to join in the action.
Some advice please from the knowledgeable ones if I can.
I had intended to use a SATA HD instead of the SD Card, perhaps this isn't necessary and may be an overkill?
What does the collective think? -
No it’s not overkill. If you look at the HA forum, you will see legions of people migrating away from the rPI to intel NUC because of the SD card issue. These are very cheap, controller less (therefore cache less, garbage collection less, wear leveling less) NAND flash which have a relatively short lifetime (similar to what Ezio embedded in their updated/downgraded version of the vera). The rPi4 is a bit tricky to boot from SATA but it can be done and if you want a reliable system, you should definitely go down that route.
A big part of it of course will depend on how much storage writing you will be doing but regardless, mid-long term it’s a bit of a waste. The SSD cards are really designed for digital cameras where pictures are taken until the card is full, transferred and then erased again on a low frequency basis. They are not very good for computing storage use.
-
I'm on my second NUC. The first one was a Celeron, now on an i3 I found getting dust in our offices (it was used as front desk PC before the pandemic). This to say that probably eBay is your friend, and Amazon too. You could find a lot of deals (well under 100 USD/EUR) for used/reconditioned NUCs.
Mine with i3, 16GB ram (I added more) and 256 GB SSD is heavily used (openLuup, my own software, cams processing, mqtt server, a lot of mqtt clients, bluetooth for MiFlora and SwitchBot) and barely consuming more than 5% CPU.
-
They're good little boxes, although I wish they were a bit cheaper. My Hass runs on a NUC, and I also use a NUC as my on-LAN secondary DNS/NTP and a few other things (like Unifi management). I'm a big fan of the Jetson Nano, too. I think this board needs more attention.
-
Alternative here in the US: I just got an HP T640 for $90. It's a little big physically but all the memory is replaceable: 2 sodimm slots, one 16gb mmc which I replaced with an SSD and boom, that's my MSR box. CPU is a ryzen equivalent of the i3 8145U in the NUC. Runs circles around any rpi for a lot less when you add up all the storage and peripheral cost. Heck it adds up to be even cheaper than my mini pc celeron box I posted in this forum before and is 3x faster. (or 8-10x faster than any rpi)
More info here: https://forums.servethehome.com/index.php?threads/new-hp-t640-thin-client-ryzen-r1505g-4gb-16gf-no-kb-mouse-no-os-installed-109.31544/
Edit:
Added for reference comparison to rpi4... pretty hard to justify buying a raspberry honestly when they end up costing the same.or here
-
In the same tone of what I posted before but with an older slower 6W CPU if you want to dirt cheap, these are very good (as in more reliable, upgradable, cheaper) than rPIs
in the UK: https://www.ebay.com/itm/HP-Flexible-T520-Thin-Client/265062105722?
in the US: https://www.ebay.com/itm/HP-T520-Flexible-Thin-Client-4GB-DDR3-V2V45UA-ABA-No-Stand-SSD/313404749197?You just need to find an old HP laptop power supply for it. That won't break your scotch budget... and amazingly they come with a windows10 pro license in the BIOS.
-
Raspberry Pi 4 B (Broadcom BCM2711) vs AMD Ryzen Embedded R1505G Benchmark, comparison and differences
