All good - much appreciated.
P
powisquare
@powisquare
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.
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page.
Once logged back in I can no longer remove errant panes nor is the + available to add new ones.
Brave Browser v1.80.122 (Jul 16, 2025)
What have I done?!
Will check other browsers on my M1.
UPDATE: Safari exhibits same behaviour.
I've tried both sans last-four public key entry and with - no change.
Use case:
When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled.
To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work.
Then another situation: the water pump system and garden irrigation, another switch.
In short, I had to create several virtual switches in Hubitat to disable rules in MSR.
Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR.
If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR.
Would it be possible to do something like this? Any recommendations from the experts?
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of.
Thanks.
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?
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
Posts
-
Z-way token Expiration -
openLuup: MQTT serverSorry - my bad. Device that's working does not have a password. I'll have another go.
Boom - all working
-
openLuup: MQTT serverYes I have - on all of them. I seem to recall, when setting up the first one, that openLuup recognised a button press. Perhaps that's how it worked. These sensors wake up on an hourly basis, but when you wake them up manually they are awake for a minute or so (it seems).
-
openLuup: MQTT serverShould have looked first ! Red highlights a win here; am seeing this ... (is there a proper way of copying and pasting?)
2021-06-12 11:10:01.904 openLuup.server:: GET /data_request?id=lu_status2&output_format=json&DataVersion=492370363&Timeout=60&MinimumDelay=1500&_=1623492371898 HTTP/1.1 tcp{client}: 0x1e96db0
2021-06-12 11:10:19.108 openLuup.io.server:: MQTT:1883 connection from 192.168.1.156 tcp{client}: 0x1d97790
2021-06-12 11:10:19.152 openLuup.mqtt:: shellyht-E01A8B SUBSCRIBE to shellies/command tcp{client}: 0x1d97790
2021-06-12 11:10:19.153 openLuup.mqtt:: shellyht-E01A8B SUBSCRIBE to shellies/shellyht-E01A8B/command tcp{client}: 0x1d97790
2021-06-12 11:10:19.156 luup.shelly:83: New Shelly announced: shellyht-E01A8B
2021-06-12 11:10:19.279 openLuup.context_switch:: ERROR: [dev #83] ./openLuup/client.lua:96: missing realm or nonce in received WWW-Authenticate header
2021-06-12 11:10:19.280 openLuup.mqtt:: ERROR publishing application message for mqtt:shellies/announce : ./openLuup/client.lua:96: missing realm or nonce in received WWW-Authenticate header
2021-06-12 11:10:19.393 openLuup.server:: request completed (1891 bytes, 1 chunks, 17488 ms) tcp{client}: 0x1e96db0 -
Z-way token ExpirationUpdated openLuup to v. 21.6.8 yesterday. I notice the z-way bridge has lost connection. and requires login. When I go to device/actions there is no way to enter credentials - only a login button.
-
openLuup: MQTT serverThe first Shelly I tried worked with the bridge created and device created in the Shellies room. The next ones also appear in openLuup/Servers/Received Connections list but don't appear as devices. Have I missed a step?
-
openLuup: MQTT serverOMG. Genius. Many thanks indeed! Note to self - for Shelly .. Internet & Security/Advanced - Developer Settings/Enable MQTT
-
openLuup: MQTT serverWill I need to set ports or do anything in Lua Startup still?
-
openLuup: MQTT serverHi guys - just received some Shelly H & Ts. Is there any documentation on how to connect these to mqtt (in novice speak
)? Have read the thread but am getting slightly confused - do I need just the openluup mqtt server or another plugin also? -
ubiquiti breachDid you ever get a certificate on to your controller? Would love to get Let's Encrypt on but I wonder if they are making it difficult so people go for their cloud solution.
-
Secure/Horstmann thermostat/zwayNot using the button - don't really know what it does.
-
Secure/Horstmann thermostat/zwayThanks, only difference is Brand; I have Horstman (Secure), all versions and command classes are the same. I get the same error using openLuup interface too. Think this is the part where setpoint is accepted. Do you use the button for anything?
[2021-03-22 09:05:40.517] [D] [zway] SETDATA devices.42.data.lastReceived = 0 (0x00000000)
[2021-03-22 09:05:40.517] [I] [zway] Node 42:0 CC Wakeup: Wakeup notification
[2021-03-22 09:05:40.517] [D] [zway] SETDATA devices.42.instances.0.commandClasses.132.data.lastWakeup = 1616403940 (0x60585de4)
[2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.data.isAwake = True
[2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.data.lastSendInternal = **********
[2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.data.lastNonceGet = 47091702 (0x02ce8ff6)
[2021-03-22 09:05:40.518] [D] [zway] Running wakeup handler for node 42
[2021-03-22 09:05:40.518] [D] [zway] SETDATA devices.42.instances.0.commandClasses.132.data.lastSleep = 1616403940 (0x60585de4)
[2021-03-22 09:05:40.518] [I] [zway] Node 42:0 CC Wakeup: Send node to sleep
[2021-03-22 09:05:40.518] [I] [zway] Adding job: Wakeup Sleep
[2021-03-22 09:05:40.518] [D] [zway] SENDING (cb 0xfc): ( 01 0D 00 13 2A 06 43 01 01 22 00 6E 05 FC 3B )
[2021-03-22 09:05:40.525] [D] [zway] RECEIVED ACK
[2021-03-22 09:05:40.527] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2021-03-22 09:05:40.528] [D] [zway] SENT ACK
[2021-03-22 09:05:40.528] [D] [zway] Delivered to Z-Wave stack
[2021-03-22 09:05:40.548] [D] [zway] RECEIVED: ( 01 18 00 13 FC 00 00 02 00 B0 7F 7F 7F 7F 01 01 03 00 00 00 00 02 01 00 00 BA )
[2021-03-22 09:05:40.548] [D] [zway] SENT ACK
[2021-03-22 09:05:40.548] [I] [zway] Job 0x13 (ThermostatSetPoint Set): Delivered
[2021-03-22 09:05:40.549] [D] [zway] SendData Response with callback 0xfc received: received by recipient
[2021-03-22 09:05:40.549] [D] [zway] SETDATA devices.42.data.lastSendInternal = **********
[2021-03-22 09:05:40.549] [D] [zway] SETDATA devices.42.data.lastSend = 47092706 (0x02ce93e2)
[2021-03-22 09:05:40.549] [D] [zway] Job 0x13 (ThermostatSetPoint Set): success
[2021-03-22 09:05:40.549] [I] [zway] Removing job: ThermostatSetPoint Set -
Secure/Horstmann thermostat/zwayThanks - yes from zway basic interface.
-
Secure/Horstmann thermostat/zwaySeems to be working fine except I get an error notification via email 'Error during perform command execution: Error: Invalid argument' every time setpoint is changed from controller. Also does anyone know if the 'Button' child is useful?
[2021-03-22 09:00:03.113] [I] [core] --- ZWayVDev_zway_42-0-67-1 performCommand processing: {"0":"exact","1":{"level":"11"}}
[2021-03-22 09:00:03.113] [D] [zway] SETDATA devices.42.instances.0.commandClasses.67.data.1.setVal = 11.000000
[2021-03-22 09:00:03.114] [I] [zway] Adding job: ThermostatSetPoint Set
[2021-03-22 09:00:03.114] [I] [zway] Adding job: ThermostatSetPoint Get
[2021-03-22 09:00:03.114] [I] [zway] Node 42:0 CC ThermostatMode: Thermostat Mode 1 is not supported by device (modemask 0x0)
[2021-03-22 09:00:03.117] [I] [core] Notification: error (module): Error during perform command execution: Error: Invalid argument
[2021-03-22 09:00:03.125] [I] [core] Error: Invalid argument
at Error (native)
at t_vDev.(anonymous function).self.controller.devices.create.handler (automation/modules/ZWave/index.js:5540:62)
at .extend.performCommand (automation/classes/VirtualDevice.js:365:25)
at ZAutomationAPIWebRequest..extend.performVDevCommandFunc (automation/ZAutomationAPIProvider.js:442:51)
at ZAutomationAPIWebRequest.handlerFunc (automation/ZAutomationAPIProvider.js:3976:30)
at ZAutomationAPIWebRequest.ZAutomationWebRequest.handleRequest (automation/WebserverRequestRouter.js:250:35)
at automation/WebserverRequestRouter.js:32:29
at WebServer.document_root (automation/Webserver.js:40:31)
[2021-03-22 09:00:03.130] [I] [core] HK: updated ZWayVDev_zway_42-0-67-1
[2021-03-22 09:00:03.137] [D] [zway] RECEIVED: ( 01 18 00 13 F0 00 00 05 01 C4 7F 7F 7F 7F 00 00 03 2E 00 00 00 03 01 00 00 EB ) -
Why Migrate to Z-way from vera and how?+1 for zway
-
altUIMay well be different machines, differing firmwares. Frustrating nevertheless. Here's a stab at displaying variables.
-
altUIThanks - will have to try tomorrow - can't risk sending vera in to a tiz with guests staying.
-
altUICan i set them to (0,0) as the (5,1) misbehaves?
-
altUISorry I was conflating issues. I have (a) two thermostats on separate veras that have different jsons and (b) one of those thermostats is shown above has the same json as another thermostat (on zway) but different functionality. Kinda got that muddled.
-
altUISeems odd that it's two different jsons for the same thermostat on separate veras. Perhaps the issue is inherently an altui one anyway. When I use the up down arrows for temp setpoint it starts from the cooling setting ie in this case 0 so its a lot of clicking to get to 20.
The same model thermostat paired to zway displays and behaves correctly with no cooling temps.
But they have the same json?
