@toggledbits yes that was the problem, thanks on the fix.
Best regards
E
eonnet
@eonnet
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?
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.
Posts
-
Issue with HTTP API -
Issue with HTTP API@toggledbits here is the log
[latest-22328]2022-11-30T19:58:30.832Z httpapi:ERR httpapi: perform hvac_heating_unit.set_setpoint on Thermostat#hass>climate_vivax failed: [TypeError]Typ>
[latest-22328]2022-11-30T19:58:30.834Z httpapi:CRIT TypeError: Type mismatch on config reactor.engine.monitored_entities, expecting array, got object
TypeError: Type mismatch on config reactor.engine.monitored_entities, expecting array, got object
at Configuration.getConfig (/opt/reactor/server/lib/Configuration.js:163:23)
at Function.getConfig (/opt/reactor/server/lib/Configuration.js:151:82)
at HTTPAPI._handlePerformRequest (/opt/reactor/server/lib/httpapi.js:834:56)
at /opt/reactor/server/lib/httpapi.js:396:61
at Layer.handle [as handle_request] (/opt/reactor/node_modules/express/lib/router/layer.js:95:5)
at next (/opt/reactor/node_modules/express/lib/router/route.js:144:13)
at Route.dispatch (/opt/reactor/node_modules/express/lib/router/route.js:114:3)
at Layer.handle [as handle_request] (/opt/reactor/node_modules/express/lib/router/layer.js:95:5)
at /opt/reactor/node_modules/express/lib/router/index.js:284:15
at param (/opt/reactor/node_modules/express/lib/router/index.js:365:14)and another on with different request
[latest-22328]2022-11-30T20:02:22.335Z httpapi:ERR httpapi: perform hvac_control.set_mode on Thermostat#hass>climate_vivax failed: [TypeError]TypeError: T>
[latest-22328]2022-11-30T20:02:22.336Z httpapi:CRIT TypeError: Type mismatch on config reactor.engine.monitored_entities, expecting array, got object
TypeError: Type mismatch on config reactor.engine.monitored_entities, expecting array, got object
at Configuration.getConfig (/opt/reactor/server/lib/Configuration.js:163:23)
at Function.getConfig (/opt/reactor/server/lib/Configuration.js:151:82)
at HTTPAPI._handlePerformRequest (/opt/reactor/server/lib/httpapi.js:834:56)
at /opt/reactor/server/lib/httpapi.js:396:61
at Layer.handle [as handle_request] (/opt/reactor/node_modules/express/lib/router/layer.js:95:5)
at next (/opt/reactor/node_modules/express/lib/router/route.js:144:13)
at Route.dispatch (/opt/reactor/node_modules/express/lib/router/route.js:114:3)
at Layer.handle [as handle_request] (/opt/reactor/node_modules/express/lib/router/layer.js:95:5)
at /opt/reactor/node_modules/express/lib/router/index.js:284:15
at param (/opt/reactor/node_modules/express/lib/router/index.js:365:14) -
Issue with HTTP APII tried tonight with curl and postman i get the same response
request failed
no further info.... this is only happening when i try to make a request to entity.I also tried to make a reaction with the http request to reactor and the response is:
Reaction "re-lb2sork5" (re-lb2sork5) step 1 http request failed
Error: HTTP request failed: 400 Bad RequestI hope this gives you more info
-
Issue with HTTP APIHello @toggledbits im trying to control reactor from external source, for this example i'm using web browser.
(this is example for the docker installation on ubuntu server)
When i hit a web page http://192.168.0.39:8111/api/v1/entity/hass_container>climate_vivax/perform/hvac_heating_unit.set_setpoint?setpoint=26
i get a response
'Request failed'
and the action is not executedWhen i hit a web page http://192.168.0.39:8111/api/v1/reaction/re-lb1bejbo/run
i get response
{"status":true,"message":"Vivax Off started"}
and the action is executedOn the unraid server docker installation when i hit http://192.168.0.81:8111/api/v1/entity/hass>climate_vivax/perform/hvac_heating_unit.set_setpoint?setpoint=26
i recieve a response
{"status":true,"message":"Performed hvac_heating_unit.set_setpoint on Thermostat#hass>climate_vivax"}
and the action is executedwhen i hit http://eonnet.duckdns.org:8112/api/v1/entity/hass>climate_vivax/perform/hvac_control.set_mode?mode=off
i recieve a response
{"status":true,"message":"Performed hvac_control.set_mode on Thermostat#hass>climate_vivax"}
and the action is executed.Best regards
-
Issue with HTTP APIHello @toggledbits I have a strange issue with the HTTP request that i send to Reactor.
I have two reactors one on a Unraid server and one on Ubuntu server installed as a docker, when i send http get request to the Unraid server to control home assistant entity everything is going ok, but when i send the same request to the ubuntu modified accordingly it says "Request failed" but when i try to run reaction via http request it works.When i go to entities and try to control the entity manually its working.
Any idea's?
Best regards
-
Who are my Home Assistant + ZWave-JS users?@vezinpi yes hassos
-
Who are my Home Assistant + ZWave-JS users?@vezinpi in addon settings add 3000 port to the host.
And than you can access the zwavejs2mqtt addon via ws://ip:3000 -
Who are my Home Assistant + ZWave-JS users?Hello, i managed to connect the HA add on to reactor. The first thing i noticed is that mappings for fan on ZXT-600 and ZXT-120 IR extender for AC are incorrect, on reactor are as follows: 0-off, 1 - auto, 2 - continuous, 3 - periodic, 4 - low, 5 - medium, 6 - high, in zwavejs web console are 0 - Auto low, 1- Low, 3 - High, 5 - Medium
-
Who are my Home Assistant + ZWave-JS users?Hello, i'm running zwavejs2mqtt addon on Home Assistant and the addon don't allow to connect to the addon via IP address. Is there a solution for this or i'm out of luck?
I'm running my Reactor on a docker on Unraid, and home assistant os as a VM on the unraid, i can't install docker zwavejs2mqtt because for some unknown reason my zwave stick loses a connection with the docker after couple of days and cant find the solution for that.
cheers
-
Who are my Home Assistant + ZWave-JS users?I’m using HA with zwavejs2mqtt addon
-
Considering changing to HA - but what installation method?@perh The addon menu is just a docker containers, you have all of them as a separate docker which you can install.
-
ezmqtt switch control questions/issuesThanks, found the problem updated and its working, in your instruction for installation the container is named toggledbits/ezmqtt:latest-generic-amd64 and in the docker hub latest version is toggledbits/ezmqtt:latest-amd64, that is why it didnt update.
cheers
-
ezmqtt switch control questions/issuesHello @toggledbits i run ezmqtt in a docker, updated to the latest version and still have the same issue:
here is the error in the log that i recieveat EzloClient.handle_message (/opt/ezmqtt/lib/ezlo.js:664:25)
at /opt/ezmqtt/lib/wsclient.js:233:29
at new Promise (<anonymous>)
at WSClient.trigger (/opt/ezmqtt/lib/wsclient.js:229:16)
at WebSocket.<anonymous> (/opt/ezmqtt/lib/wsclient.js:76:30)
at WebSocket.emit (node:events:390:28)
at Receiver.receiverOnMessage (/opt/ezmqtt/node_modules/ws/lib/websocket.js:1008:20)
at Receiver.emit (node:events:390:28)
at Receiver.dataMessage (/opt/ezmqtt/node_modules/ws/lib/receiver.js:517:14)
at Receiver.getData (/opt/ezmqtt/node_modules/ws/lib/receiver.js:435:17) {
code: -32602,
reason:Unexpected Json format for value type 'bool': ["true","true"]
}
mqtt: <ezmqtt/set/device/61e8937e124c35129921171d/item/switch true> failed; Wrong field of object (-32602): Unexpected Json format for value type 'bool': ["true","true"]I send plain payload true on topic ezmqtt/set/device/61e8937e124c35129921171d/item/switch.
version that is shown in the log file is Version 21357
cheers
-
ezmqtt switch control questions/issuesHi @toggledbits,
i tried the ezmqtt today, i have some issues most likely that i'm doing something wrong.
i have on my ezlo hub 3 switches, 1 dimmer and 1 motion sensor
i can control the dimmer via ezmqtt/set/device/<device-id>/item/<item-name>
but i can't control the switches.i receive on ezmqtt/tele/device/61e8937e124c35129921171d/item/switch payload true or false depending on the state of the switch, but when i send on ezmqtt/set/device/61e8937e124c35129921171d/item/switch payload true or false nothing happens, its the same for all switches.
what i'm doing wrong?
Cheers
-
New toys to play with@crille i haven’t tried it wit ezmqtt i intend to try it today, but have tried it with zwavejs2mqtt and its pretty smooth.
-
New toys to play with@crille you can use the mqttthing plugin on homebridge
-
Sustained condition is missing from MSRThanks both @toggledbits and @Elcid. I will use the @toggledbits idea because i dont need instantaneous feedback from ezlo.
Did anybody tested ezlo with higher number of devices how it compares with Vera? i have around 50 zwave devices and when i turn on scene with multiple devices sometimes it takes 1 minute scene to complete, i get a lot of retries especially with the dimmers, the zwave network is good because the 50 devices are in 60 sqm apartment on 2 floors so 50 devices make excellent mesh
90% of the devices are mains powered.My idea is to use Ezlo hub for zwave devices and transfer them to Control4 via HTTP calls. that is why i will use @toggledbits solution because ezlo -> Control4 is just for feedback i dont need instantaneous response, from C4 -> Ezlo i will use direct http call so that will be instant
-
Sustained condition is missing from MSR@toggledbits said in Sustained condition is missing from MSR:
So, you want to do something when it has not changed for 3 seconds... think about how to structure that.
What i'm trying to do is to import ezlo dimmer in vera and have 2 way communication. If i do action on change without sustain sometimes it goes in a loop, so i want to make sure that dimmer has reached the level and stayed on that level for couple of seconds before i send the information back to vera. In vera i'm using your virtual dimmer. But for some reason when you turn on ezlo the dimmers make a short stop for couple of hundred milliseconds somewhere in between causes a race between the two dimmers.
-
Sustained condition is missing from MSRWhat should i choose, what i'm trying to achieve is that when dimmer level changes and stays for example 35% for 3 seconds pass the dimmer level to a http call