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
Hi Smart Home Community.
I have used a Sonos inline WiFi switch to make one of my light fittings smart, but it requires a hard reset for WiFi changes, plus it isn't zigbee compatible, which means I can't use the Hue app to control it with the rest of the lights.
To that end I bought a Samotech SM308-S as it is recommended as the better than the Sonos equivalent.
I am however not exactly sure how to wire it in.
The manual is available here
Can anyone help me by clarifying which ports I need to use, and whether I should be using the live or switched live line for live etc.
I will be keeping using standard switches for a while, although hope to upgrade to tap dials once I have all the fittings upgraded.
Thanks
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI:
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status
Last 11:20:37
My MQTT configuration (local_mqtt_devices.yaml) for the related entity is:
layzspa_message:
type: ValueSensor
capabilities: ["temperature_sensor", "value_sensor", "power_sensor"]
primary_attribute: power_sensor.value
events:
"layzspa/message":
"power_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.PWR )'
expr: "float(payload.PWR)"
"value_sensor.air":
json_payload: true
if_expr: '! isnull( payload?.AIR )'
expr: "float(payload.AIR)"
"value_sensor.pump":
json_payload: true
if_expr: '! isnull( payload?.FLT )'
expr: "float(payload.FLT)"
"value_sensor.god":
json_payload: true
if_expr: '! isnull( payload?.GOD )'
expr: "float(payload.GOD)"
"value_sensor.lock":
json_payload: true
if_expr: '! isnull( payload?.LCK )'
expr: "float(payload.LCK)"
"value_sensor.unit":
json_payload: true
if_expr: '! isnull( payload?.UNT )'
expr: "float(payload.UNT)"
"value_sensor.error":
json_payload: true
if_expr: '! isnull( payload?.ERR )'
expr: "float(payload.ERR)"
"temperature_sensor.green":
json_payload: true
if_expr: '! isnull( payload?.GRN )'
expr: "float(payload.GRN)"
"temperature_sensor.red":
json_payload: true
if_expr: '! isnull( payload?.RED )'
expr: "float(payload.RED)"
"temperature_sensor.target":
json_payload: true
if_expr: '! isnull( payload?.TGT )'
expr: "float(payload.TGT)"
"temperature_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.TMP )'
expr: "float(payload.TMP)"
"temperature_sensor.virtual":
json_payload: true
if_expr: '! isnull( payload?.VTM )'
expr: "round(float(payload.VTM), 1)"
"temperature_sensor.ambient":
json_payload: true
if_expr: '! isnull( payload?.AMB )'
expr: "float(payload.AMB)"
"layzspa/Status":
"value_sensor.status":
if_expr: '! isnull( payload )'
expr: "payload"
"layzspa/button":
"value_sensor.button":
if_expr: '! isnull( payload )'
expr: "payload"
and in reactor.yaml I have:
"layzspa_states":
name: "Lay-Z-Spa States"
friendly_name: 'Lay-Z-Spa States'
include: layzspa_message
I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded).
Get it at (install is similar to MQTTController and such):
https://github.com/dbochicchio/reactor-opensprinkler
Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty.
Since I've learnt a lot from this controller, I'll explore new controllers soon.
Good day all,
I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing.
I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container.
Has anyone done this? Any advice?
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.
Following on from my last thread, some progress has been made over the weekend.
With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system.
Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic.
Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work.
Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic.
Once that hurdle is sorted I'm torn between:
Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or
Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.)
Decisions, decisions.
C
Hi guys,
Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular.
Maybe there are better ways to organize my rule sets.
I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
I have the following yaml configuration in local_mqtt_devices file
x_mqtt_device:
set_speed:
arguments:
speed:
type: str
topic: "command/%friendly_name%"
payload:
type: json
expr: '{ "fan": parameters.speed }'
While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Hi!
I get this message when I'm on the status tab:
System Configuration Check
The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds.
I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6.
HA versions are:
Core 2025.3.4
Supervisor 2025.03.4
Operating System 15.1
I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version.
Do anyone know what I can try?
Thanks in advance!
Let's Be Careful Out There (Hill Street reference...)
/Fanan
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB.
While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed.
So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response.
While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits
Thanks!
Hi ,
I'm on
-Reactor (Multi-hub) latest-25067-62e21a2d
-Docker on Synology NAS
-ZWaveJSUI 9.31.0.6c80945
Problem with ZwaveJSUI:
When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white.
I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui.
I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb".
After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color.
This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite.
x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33}
The "cold white" and "warm white" settings interfer with the rgb color settings.
Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white
are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white.
So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have
x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33}
14/03/2025, 16:43:57 - value updated
Arg 0:
└─commandClassName: Color Switch
└─commandClass: 51
└─property: targetColor
└─endpoint: 0
└─newValue
└──red: 235
└──green: 33
└──blue: 33
└─prevValue
└──red: 235
└──green: 33
└──blue: 33
└─propertyName: targetColor
14/03/2025, 16:43:57 - value updated
Arg 0:
└─commandClassName: Color Switch
└─commandClass: 51
└─property: currentColor
└─endpoint: 0
└─newValue
└──warmWhite: 204
└──coldWhite: 0
└──red: 235
└──green: 33
└──blue: 33
└─prevValue
└──warmWhite: 204
└──coldWhite: 0
└──red: 235
└──green: 33
└──blue: 33
└─propertyName: currentColor
In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set.
x_zwave_values.Color_Switch_currentColor_0=204
x_zwave_values.Color_Switch_currentColor_1=0
x_zwave_values.Color_Switch_currentColor_2=235
x_zwave_values.Color_Switch_currentColor_3=33
x_zwave_values.Color_Switch_currentColor_4=33
Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this?
x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33}
Thanks in advance.
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
