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=nullHow to shutdown a Windows 10 PC ?
-
Hi
I am setting up a Windows 10 gaming PC for my daughter.
I would like to be able to shutdown the PC via an MSR ruleset or by using a global reaction.
I can wake up the PC via WOL in Vera and thus also within an MSR rule, but not sure how I might shutdown the PC any ideas?
MSR is running on a Linux Debian box if that makes any difference.
Thanks
-
I have set this up so far. As there is no IR receiver on this Intel i3 Mini-PC I can't really control it with my Harmony Hub and remote.
I just created a Harmony activity to turn on the TV and the AVR amp and set them to the right inputs etc.
Then in my MSR rule my trigger is detecting from Vera when this particular Harmony activity has been started and in my action I am turning ON the WOL switch in Vera, that will send the magic packet to the Mini-PC to wake it up etc.
But for the reset reaction this is where I need some way to send a shutdown command to the Windows Mini-PC.
-
Also are there any PC gaming experts on here? Not related to MSR but if you have a HDMI PC monitor with no speakers, how do you split out the audio to a set of stand alone PC speakers? My daughter wants a PC gaming setup in her room for playing Steam games and such.
Currently I've got it running in my lounge though my AVR and 5.1 speakers, but I will be moving the PC upstairs in to her bedroom at some point, when I have bought a monitor and speakers and gaming keyboard and mouse etc which I haven't got yet.
Thanks
-
@cw-kid said in How to shutdown a Windows 10 PC ?:
Also are there any PC gaming experts on here? Not related to MSR but if you have a HDMI PC monitor with no speakers, how do you split out the audio to a set of stand alone PC speakers? My daughter wants a PC gaming setup in her room for playing Steam games and such.
Currently I've got it running in my lounge though my AVR and 5.1 speakers, but I will be moving the PC upstairs in to her bedroom at some point, when I have bought a monitor and speakers and gaming keyboard and mouse etc which I haven't got yet.
Thanks
Does the PC not have a separate audio out port?
If not, you can get HDMI audio extractors off Amazon which give you an Optical and RCA output. Not sure if this will negatively affect user input lag though.
-
@cw-kid I have a small utility running on my PC for the very same reason, that's receiving MQTT messages to shutdown automatically. HASS has a similar 3rd party app to accomplish the same: https://github.com/LAB02-Research/HASS.Agent
Easy to integrate under MSR.
-
Thanks for the replies !
I am not using Home Assistant or MQTT however.
Regarding the audio I just had a look at the back of the Mini-PC and I cannot see any other audio output ports. I will have to find its user manual not even sure what make and model it is.
The sticker on it says SEI10-G might be the same as this one here on Amazon.
-
@cw-kid said in How to shutdown a Windows 10 PC ?:
Thanks for the replies !
I am not using Home Assistant or MQTT however.HASS is not really needed, but MQTT is mandatory because it's used to exchange messages. The alternative is something running an HTTP endpoint on the PC, but from a security point of view that's bad, but doable.
-
OK turns out it's comparatively trivial to do it from Linux (was pretty sure it was. So you should be able to execute this. Bit of a faff for set up but...
Shutdown Windows machine from linux terminal
I am running an application on linux machine. By giving the ip address of a windows machine as input, the application must shutdown the windows machine. If the machines run the same OS it is very e...
Actually reading further, looks like there's some simpler options installing Cygwin or an SSH server and just SSHing in
C
-
I updated this PC to Windows 11 and installed OpenSSH Server on it. I was then able to login to it directly via Putty on my other Windows 10 laptop, I was prompted for the username and password and I could then issue a
shutdown /pcommand and it did then shutdown the Mini-PC.I then tried to add my Vera Plus public key on to the Windows 11 PC so that Vera can ssh directly to it with no username and password prompt etc. However its not working I get this error every time.
ecdsa-sha2-nistp256 host key mismatch for 192.168.1.47 !192.168.1.47 being the Windows 11 OpenSSH Server
I created an authorized_keys file on the Windows 11 PC in this location:
C:\Users\myusername\.sshAnd in the authorised_keys file I pasted in the Vera Plus pubic key.
I also followed the instructions on this article here to enable "Public key authentication" on the OpenSSH Server on the Windows 11 PC.
Then reading this Microsoft article it suggested if my windows user is in the administrators group I need to instead create a
administrators_authorized_keysfile in C:\ProgramData\ssh\So I tried that but I still get the host key mismatch error when I connect to the Vera Plus via putty and then tried to ssh to the Windows 11 PC.
-
I think you need your public key stored on the Vera. Or possibly a public key that matches the username you're using.
There's also an sshd-copy-id command which I found way more reliable than trying to edit authorised keys files. I'd probably use that, then rename the file if needed.
C
-
If the Windows PC was previously known to the Vera before your upgrade, it's likely that the SSH key was regenerated on the Windows PC side when you did the upgrade, so the Vera SSH has the old host key. You can remove it from the
known_hostsfile on the Vera side.That may not be the only problem you run into, though. Of late, many newer SSH clients have removed weaker host key algorithms and key exchange algorithms, so connecting to the ancient, rotting carcasses of these old Veras presents the SSH peer with a set of options it doesn't want to use, and the key exchange fails. That's a bit more complicated to fix...
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
I always struggle with this type of stuff. Patrick helped me in the past on this Vera forum thread here.
On that old post I wanted my Vera Plus to be able to ssh into my Raspberry Pi with no password prompt.
I could then create MSR rules that instruct Vera to run a command like this to say reboot the Raspberry Pi etc.
os.execute("ssh pi@192.168.1.101 sudo reboot") -
@toggledbits said in How to shutdown a Windows 10 PC ?:
If the Windows PC was previously known to the Vera before your upgrade, it's likely that the SSH key was regenerated on the Windows PC side when you did the upgrade, so the Vera SSH has the old host key. You can remove it from the known_hosts file on the Vera side.
The Mini-PC was not known to the Vera before. I updated to Windows 11 and then install OpenSSH on the Windows 11 PC.
Before that I did nothing with Vera and the Mini-PC running Windows.
Oh I think I see what might be happening now. Looking in the known_hosts I already have an entry for the static LAN IP address of the Mini-PC but that is for Linux Debian on the Mini-PC.
Before when I was messing about with Ezlo Softhub I setup a dual boot on the Mini-PC for Windows 10 and Debian Linux.
Guess I can't have two known hosts for the same IP address but different OS's.
-
-
OK just setup the rest of my MSR rule now with a Reset reaction, that gets the Vera Plus to run a LUA / os.execute shutdown command sent to the Windows 11 PC.
So now when I start my Logitech Harmony activity for the Windows Games PC, MSR triggers the rule and gets Vera to send a WOL packet to the PC to wake it up.
And when I end the Harmony activity the reset reaction in the MSR rule gets Vera to shutdown the PC.
I even managed to get my Harmony Elite remote to launch RetroArch or Steam via buttons on the LCD screen and I also added a ALT+F4 button to exit the Windows apps.
Next thing to figure out is how to split out the HDMI audio to a pair of PC speakers.
Thanks.
