He is very sensitive if anyone criticizes his baby, I'm with @akbooer but believe the wheels have already fallen off as there are few devs left on the forum.
It will be at least 2 years before there is a viable marketable product let alone any plugins to replace what will be lost when Vera goes EOL.
B
Black Cat
@Black Cat
Using build 25328 and having the following users.yaml configuration:
users:
# This section defines your valid users.
admin: *******
groups:
# This section defines your user groups. Optionally, it defines application
# and API access restrictions (ACLs) for the group. Users may belong to
# more than one group. Again, no required or special groups here.
admin_group:
users:
- admin
applications: true # special form allows access to ALL applications
guests:
users: "*"
applications:
- dashboard
api_acls:
# This ACL allows users in the "admin" group to access the API
- url: "/api"
group: admin_group
allow: true
log: true
# This ACL allows anyone/thing to access the /api/v1/alive API endpoint
- url: "/api/v1/alive"
allow: true
session:
timeout: 7200 # (seconds)
rolling: true # activity extends timeout when true
# If log_acls is true, the selected ACL for every API access is logged.
log_acls: true
# If debug_acls is true, even more information about ACL selection is logged.
debug_acls: true
My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules.
I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds).
Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off?
With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches.
Thanks
Reactor (Multi-hub) latest-26011-c621bbc7
VirtualEntityController v25356
Synology Docker
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future.
In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level.
Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way.
I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption.
A few other things to know:
If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc.
Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy).
The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON.
You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach).
The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case.
This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change.
This thread is open for any questions or concerns.
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks.
Any chance of a 'bulk delete' option?
No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices
Cheers
C
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.
Just for the record, in case anyone is following, I'm really rather impressed.
I have installed one of these:
https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1
That's connected (physically) to the VM running on my Synology, with a 2m USB extension.
The same host also runs Openluup, Mosquito, HA Bridge.
Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions.
Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor
I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA.
https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title
The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so...
https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title
Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt.
And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one).
A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....)
Commended to the house. Thanks for everyone that got me on the right lines.
C
If you’re like me and still running HABridge to control your devices locally via Alexa, you might need to tweak your endpoints to call Reactor via HTTP. Here’s the best way to do it, IMO:
Insert the Reactor Canonical ID (e.g., zwavejs>71-1) into the MapID field, but make sure it’s URL-encoded like this: zwavejs%3E71-1.
Then, configure these endpoints as needed:
On: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.on
Off: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.off
Dim:
For lights: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/dimming.set?level=${intensity.decimal_percent}
For roller shutters: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/position.set?value=${intensity.decimal_percent}
Color: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/rgb_color.set_rgb?red=${color.r}&green=${color.g}&blue=${color.b}
Just replace [ReactorIP] with your actual IP address. By using these placeholders, you can standardize your endpoints across all devices, making maintenance easier.
This setup works with any device mapped under MSR, regardless of the controller (ZWaveJS, Vera, HASS, OpenSprinkler, virtual, MQTT, DynamicEntities, etc.). If you need different calls, just go to the entities, get the action and parameters, and adjust accordingly. Enjoy super fast access to your devices via Alexa!
If you're migrating from Vera, the endpoints are (URL-encoded) in a file called device.db, in JSON format, under your config. You'd write a script to align the new endpoints to the new one, if you prefer to do it automatically. YMMV.
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Good evening all,
For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time.
Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed.
Thanks.
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations.
Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction?
Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for.
I guess it's something of an edge case so no huge issue.
TIA!
C
I'm sure this has been asked, and answered, but damned if I can figure it out
Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage.
Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts.
After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!)
What I would like is for the 3 minute delay until the lights go off to start from the latest door open event.
That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity.
I've tried 'hacking' with a virtual switch, but can't seem to stop the delay.
Any pointers?
TIA
C
Hello oh great ones.
After a couple of hours messing with ports and permissions I have Zigbee2mqtt installed and running on my virtual pi
Can connect to the front end and everything
Odd one though, simply cannot get systemctl to work and the error is, well, unhelpful. The service file is this:
[Unit]
Description=zigbee2mqtt
After=network.target
[Service]
Environment=NODE_ENV=production
Type=notify
ExecStart=/usr/local/bin/node index.js
WorkingDirectory=/opt/zigbee2mqtt
StandardOutput=inherit
# Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5)
StandardError=inherit
WatchdogSec=10s
Restart=always
RestartSec=10s
User=pi
[Install]
WantedBy=multi-user.target
Straight out of the docs with the change to point to my local node install (which we know works as it's the same as the very fine Reactor is using.
Running manually pnpm start
in /opt/zigbee2mqtt works fine
However:
catman@openluup:/etc/systemd/system$ sudo systemctl start zigbee2mqtt.service
Job for zigbee2mqtt.service failed because the control process exited with error code.
See "systemctl status zigbee2mqtt.service" and "journalctl -xe" for details.
Which I have
catman@openluup:/etc/systemd/system$ sudo systemctl status zigbee2mqtt.service
● zigbee2mqtt.service - zigbee2mqtt
Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2025-12-16 12:32:42 GMT; 4s ago
Process: 3093 ExecStart=/usr/local/bin/node index.js (code=exited, status=217/USER)
Main PID: 3093 (code=exited, status=217/USER)
and
-- A start job for unit zigbee2mqtt.service has begun execution.
--
-- The job identifier is 17477.
Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed to determine user credentials: No such process
Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed at step USER spawning /usr/local/bin/node: No such process
-- Subject: Process /usr/local/bin/node could not be executed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The process /usr/local/bin/node could not be executed and failed.
--
-- The error number returned by this process is ERRNO.
Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=217/USER
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit zigbee2mqtt.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 217.
Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit zigbee2mqtt.service has entered the 'failed' state with result 'exit-code'.
Dec 16 12:35:16 openluup systemd[1]: Failed to start zigbee2mqtt.
-- Subject: A start job for unit zigbee2mqtt.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit zigbee2mqtt.service has finished with a failure.
Which strikes me as very odd.
Any blindingly obvious things I'm missing?
TIA!
C
Posts
-
Vera account suspended for a 1000 years -
First post to say helloThere is a new member who seems to be a little shy to say hello.
Let's give Sorin a big welcome...... -
Vera account suspended for a 1000 yearsThere is nothing on that forum that is of interest now. Before it was a joy to open it and read what others had achieved, look at it now, just full of beta comments of possible new FW.
Commercially, I've opted for Homeseer and have never looked back especially as HS4 now supports node-red natively, but always read this forum first as it has many old friends on board advancing Home Management Automation. Keep up the good work guy's and don;t look back. -
SilLabs Virtual Meeting - looks at Hub that failed........General Information - I thought some of the regulars would like to register. Links down the bottom,Interesting that they are looking into the failures....wonder if there will be any mention of you know what.....
Z-Wave Works With Amazon, Google, Samsung, Apple, Comcast Virtual Conference
by DrZWave
Silicon Labs is hosting what was intended to be an in-person conference in Austin Texas but is now a virtual online conference on IoT ecosystems - the Works With Smart Home Developer Event September 9-10. The best part is it is now FREE to attend any of the in-depth technical sessions and you don't have to wear a mask. The downside is that we don't get to experience all that great music down in Austin - well, there's always next year!Virtual IoT Works With EcoSystems from Google, Amazon, Apple for Z-Wave development engineers
https://workswith.silabs.com/
I am hosting the Z-Wave track and will be making several presentations including a detailed look at Silicon Labs latest release of Simplicity Studio V5 which just came out yesterday. We'll also have presentations on developing Z-Wave Smart Hubs and Z-Wave Certification. I'll also be describing some IoT failures - you learn more from your failures than your successes. We have speakers and engineers from all of the ecosystem partners, not just Silicon Labs folks. Learn from the experts from across the industry!What is Works With 2020? The smart home developer’s virtual event where you will have the opportunity to interact with our ecosystem partners from Amazon, Google, Samsung, and Z-Wave to connect devices, platforms and protocols and be able to immerse yourself in keynotes, a panel discussion on Project CHIP, hands-on, and technical sessions led by smart home engineers who are building the latest advanced IoT devices. The Works With event is live, all-online, free of charge, and you can join from anywhere around the world.
Works With Z-Wave Apple, Google, Amazon, Samsung IoT SmartHome conference 2020
Click here to Register Today and feel free to forward to the rest of your team.Here’s an overview of what you won’t want to miss:
Specialized Engineer-Led Tracks – Educational sessions and technical training designed for engineers, executives, developers, business development and product managers.
Hands-On Workshops More than 12 workshops and hands-on sessions to give you experience, knowledge and confidence to develop and accelerate smart home development.
One-on-One Developer Meetings – Schedule a meeting with Silicon Labs or an ecosystem partner to get 1:1 technical guidance.
Join me in September and learn how to smoothly get your IoT device plugged into any and all of the ecosystem partners. Register today, it's totally free and you can join from anywhere in the world. See you September!
DrZWave | July 30, 2020 at 8:22 pm | Tags: WorksWith | Categories: 700 series, Best Practice, Coding Guides, News, Presentations, Summit, Z-Wave Controllers, Z-Wave Developers, Z-Wave Mesh, Z-Wave Network, Z-Wave Slaves, Z-Wave Users | URL: https://wp.me/p6tsK6-o5
Comment See all comments
Unsubscribe to no longer receive posts from DrZWave.
Change your email settings at Manage Subscriptions.Trouble clicking? Copy and paste this URL into your browser:
Z-Wave Works With Amazon, Google, Samsung, Apple, Comcast Virtual Conference
Works With Amazon, Google, Apple and more Smart Home EcoSystem vendors. Learn how to design your product to work with these 800 pound gorillas
-
Is there a projected date for the release of v 1.0 of MSR?Is there a release date for MSR v1.0?
-
First post to say helloThanks for changing to white, now it's all readable..... I really struggle with dark backgrounds.
-
Cheapest platform on which to run MSRWith the new Raspberry Pi Imager you can configure the boot sequence and user when you download (format) the card or SSD.
Click on the settings Icon (lower righthand side) that will give you access to setting User Names, SSH and more..
Make sure you use the Rasp Pi downloader for this and its a breeze.I suggest you just throw caution to the wind and buy a SSD, they aren't that much more expensive than a SD Card.
The Pi4 makes it all worth while -
CORE by Oh-La LABSSeems reminiscent to something that happened on another forum recently?
It's a long path to success, just the battle to get regional certifications puts many great ideas in the "too hard basket".
It's also scant on hardware support.
For my money I'd be heading in the software direction and allow users to choose their own Hardware.
Anyway, good luck to them, judging by their road map they will have system up. running and be market ready head of EZLO. -
Advances made in Presence Detection?OK, the price differences are because of the different systems that they can be used with.
The E276 is for Dali - that is a very professional lighting system. I agree, I would just wave my hands about however for installations in large buildings it's a very clever way to control lighting intensity - Building Management Systems are a very different animal.
E79 for Wifi or Zigbee isn't a deal breaker and in fact can be a a very clever way of light control in a Smart House without the complication of additional systems.
Looking forward to unwrapping the box when it arrives....watch this space. -
HVAC ControlI'm using Broadlink's, both the RM Pro and Mini, inexpensive and easy to use. I have 2 Pros and 1 Mini, they have been rock solid for years.
Still using the old Broadlink Vera PlugIn (you all know the one that the author had a dummy spit and took his bat and ball with him after patrick pointed out some problems with his code
)
There is/was a problem with the latest RM4 in so much that the existing Plugins didn't work with it, not sure if that ever got sorted out.
The work around now is to use Node-Red with the RM4's
As for controlling sensors, I just got an old Remotec for OAT positioned under the eaves cobbled together with Reactor and Site Sensor (for local AP Weather). -
Sunset with offset didn't runStop thinking PLEG......It will only frustrate you especially if you are trying to test the status of a device.
I'm not sure if you can actually do it as you would in PLEG, yes, I know it's frustrating but to move forward you need to unlearn what you already know. -
3D Printers - What to get in your opinion?I'm surprised there is no love either, guess the time that Vera takes to maintain doesn't allow for other activities.........:)
-
Dumb question about bulbsIf space is an issue you can also fit the module at the light fitting. It's a common method when there isn't a Neutral at the switch and a Neutral optional relay isn't on hand.
I won't comment any further on wiring rules as I'm quoting AUS/NZ not UK which will be different and may confuse.
I'll moov to the next topic now...... -
Moving MSR to DockerIt indents correctly, just the way the it copied over.
I'm planning on reinstalling this over the weekend there must be 'hidden" characters that somehow have been transposed.
Better to start with a clean sheet. -
I'm bored :DI invested in a 3D Printer...eventually.
Turns out there not that expensive after all. +1 to a Ender V2. Easy to put together and great youtube support.
The hardest part has been learning CAD- Autodesk, probably should say the most frustrating part, but now fairly conversant and can design complex designs.
That was my winter, now we are looking at Spring & Summer and the end of lockdown.
The EnderV2 is turning out adapters and wall brackets, quality is better than good and is merchantable. -
Nest thermostat alternative...@akbooer said in Nest thermostat alternative...:
I’m not so much besotted by the fact that they use WiFi, it’s just the ease of setup, integration within the system, and general ‘fit and forget’... it just couldn’t be further from Zwave in that regard.
@akbooer
I was very skeptical about Shelly when they first came out; WiFi --phutt why bother, it has to be Z-Wave I thought - How wrong could I be.
After using the Dimmer 2 I couldn't get enough of them.
How is it that Z-Wave could be so convoluted in setting up when a relative new comer to the market makes it so simple?
My thoughts - FWIW - Z-wave has become over complicated that even professional installers baulk at the mention of Z-Wave and are turning to KNX systems because they know they won't get phone calls or call outs about latency - realistically KNX does not cost that much more than Z-Wave and you can sleep at night knowing the system works instantly.
Best of all is that there are KNX plugins for most systems and you can take advantage of all protocols - after all it is IOT :} -
Cheapest platform on which to run MSR@toggledbits said in Cheapest platform on which to run MSR:
I want to add that I've been using a (Raspberry Pi) Compute Module 4 with 8GB EMMC on board
Way to go, unfortunately for me, the CM4 I/O board is the only part available. The Compute Module 4 is OOS (all versions), sigh.....
BTW, I love the case.....makes it all look very professional. -
Incrementing an outside awning with Reactor/MSR@librasun said in Incrementing an outside awning with Reactor/MSR:
I hope this helps
It certainly does ( and implemented), any idea how to tie this in with my original idea of following the sun's position?
-
Vera account suspended for a 1000 years -
Quality of Life Request: Update Button
