Hey Patrick, this is probably a rather large request but it would be nice to be able to download a back-up of MSR through the UI similar to how we could do it with R4V. Beyond that maybe even having the ability to create a rule set that auto backups to a NAS would be even more useful! Currently I know you can just copy the complete reactor file from the machine MSR is running on but using the UI would make backing possible from anywhere and much simpler and quicker!

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've got myself a nice Ecovacs Deebot 950, because one of the Roombas is getting really old (12 years and still going strong). It's my first one connected to WiFi, since the others are legacy. I've found a nice mqtt library and it's already pushing to my broker in real time, but I'm wondering if there's a generic device template and/or service, otherwise I'll start building one and I'll try to keep it as much generic as possible.

Maybe a dumb question if I'm missing something obvious, but I checked the manual and searched the forum without finding anything relevant...

Can the Rule Sets on the left side of the MSR web UI be re-sorted? I just realized that it seems to be sorted with the newest ones at the top and I would prefer to have them alphabetical... and to have a multi-level tree with nested rulesets... but I'll settle for alphabetical for now if there's a way to do it 🙂

MSR latest-22266 / Raspberry Pi 4 / Docker

Hi,

I’m sure this is not a unique question about Vera (& Lua 5.1) and I’ve seen this reference in place,, but I can’t seem to find a fix to make an https download request work..

To give you an example, the code below aims to download 2 different files, the http call works fine, returning a 200 code, but the https one doesn’t, it doesn’t return anything ?

Please could some highlight what I’m missing?

print("--------DOWNLOAD http---------") local http = require("socket.http") local body, code = http.request("http://pbs.twimg.com/media/CCROQ8vUEAEgFke.jpg") print(code) if not body then error(code) end local f = assert(io.open('mnt/nas/webtest1.jpg', 'wb')) -- open in "binary" mode f:write(body) f:close() print("--------DOWNLOAD https---------") local https = require "ssl.https" --luasec local body, code = https.request("https://u.cubeupload.com/jbcooper/16146313918060.jpg") print(code) if not body then error(code) end local f = assert(io.open('mnt/nas/webtest2.jpg', 'wb')) -- open in "binary" mode f:write(body) f:close()

@akbooer said in

The only thing left on Vera is now electricity meter readers, and I simply can't find any suitable WiFi replacement.

My hem stopped reporting this august and I’ve replaced it with a Shelly EM. I’m using another one on my solar and they’re amazing fast to report and quite precise. They’re WiFi, and mqtt based. Recommended!

Hubitat C7 = 2.3.2.141 AND 2.3.3.123
MSR in a docker = latest-22264-93bf3814 and latest-22266-88868fc0

I'm curious if this is a bug or expected behavior. Unfortunately I don't know exactly when this began either. I have renamed a few devices over the course of the last few MSR builds, but never really brought it up before. Plus I don't rename devices too often. But I have a motion sensor right now that I renamed in Hubitat from "Office Motion" to "Living Room Motion" over 2 weeks week ago. Probably closer to 3 or 4 weeks now. I have restarted MSR several times since the rename, hard refreshed the browser, tried a different machine and different browser, and even an updated version of MSR. MSR is still showing the old name within the Entities section. I know I could rename it within MSR, but I would prefer to only have to rename devices in one location. I don't recall how long ago I started noticing this, which I know does not help at all.

5f97eb06-aa1d-4f25-ba08-1212aa28f4bb-image.png

Good morning all,
I've got a stable Home Assistant running on a RPI 4 with a Aeotec Z-Stick 7 Plus, and of course the Z-wave JS integration. I've manually moved a handful of devices, and I'm overall much happier with the HA z-wave capability than I am with Vera. There are still some things I'm trying to figure out that I have in Vera that I'm not sure how they'll work in HA, but no deal breakers.

I've got all of my automation on MSR and off of luup Reactor, so really the only thing left for me is to migrate my Z-wave network. I saw @rafale77's post about using a Zwave.me UZB1 to Zway, but of course that's not what I'm using.

Is there a similar method that I can use my Aeotec Z-Stick 7 plus to Home Assistant? I have around 70 Z-wave devices (give or take devices that generate multiple instances in Vera), so manual unpairing, including, etc, would be quite a chore.

Finally, I’ve found an adequate replacement for my beloved MiniMote four-button remotes (I’ve had nine of them for the last 10 years or so!). I should have realised this earlier, but with four buttons and approximately the same form factor, the Philips Hue remotes are viable replacements…

…however, they are, of course, Zigbee and not Zwave, but this doesn’t matter in my HA environment, which has now completely ditched Zwave and Vera for all lighting and control functions, and replaced them with Hue and Shelly devices. These are all brought together with a Homebridge installation running under Docker on Synology NAS with the Apple Home app as the UI. This gives, of course, both secure remote access and voice control.

The MiniMote buttons I had configured as scene triggers to do whatever I needed, most usually toggling lights. The same functionality is easily achieved within the Home app by appropriate shortcuts.

I’m still using openLuup as a secondary hub which mimics all the various devices using MQTT and the ALTHUE plug-in and logs all device and sensor data using the built-in Historian and viewed through Grafana.

Works for me!

AK

The reason for my question is a rather long story involving a virtual thermostat on my Hubitat and using InfluxDB and Grafana to graph the state of the thermostat.

The TL;DR version is that it would be helpful if I could send MSR expressions (variables) to InfluxDB. I don't currently see any way to do that, and if it isn't a current capability of MSR it might be useful as a future enhancement.

Long version: I have a rule in MSR that runs every minute to pull the thermostat information from my thermostat's cloud API. I parse the response into global variables, and then update a Hubitat virtual thermostat when those global variables change. I added the x_hubitat_Thermostat entity, along with selected capabilities, to my reactor.yaml in the InfluxDB section, 'default_capabilities', so the changes to the virtual thermostat get logged into the db.

It's working OK except when the API reports that the temperature has reached the setpoint but the system is still operating. For example, in the morning when the heat is turned up, the temp will climb until the setpoint == the temperature, but the system will continue heating for a while afterwards. It's a variable speed/heat system so it continues to run at very low output for quite a while after the temps match.

The issue I'm having is that when the temperature matches the setpoint, the Hubitat virtual thermostat switches to idle mode on it's own, despite the fact that the API is still reporting heating mode. When the virtual device sees that the setpoint has been reached, it automatically changes to idle, which makes sense as that's how you'd want a real thermostat to work .

I am working around this by having the rule that updates the temperature on the virtual device also update the operatingState. This fixes it, but for just a few milliseconds the virtual thermostat switches to idle before the rule sets it back to heat, and that state change shows up in Grafana.

If I could just directly log changes to the expressions to InfluxDB I could avoid the issue and get the same data into the database. Also I can see other applications for something like this with other APIs where MSR and InfluxDB could be used to log data without having any virtual device entities involved.

Just seen notification to Netatmo developers that the current password-based login is being disabled as from October.

Oath2 is now a requirement for apps needing access to Netatmo. This will require some changes to my venerable plug-in. I’m not sure how easy this will be with the current libraries in use.

Does anyone out there use the Netatmo plug-in?

Does anyone have any advice on using Oath2?

Hi all, I hope someone could drive me in the right direction.

I was setting up a new zware environment using a UZB stick I bought about 2 yeasr ago and never used.
This stick was using firmware 5.27 that sounded to me a bit old.
So I looked on the process of upgrading the device and I downloaded the ZMESerialUpdater, the I went on the z-wave.me site and look for the firmware and I found (on this awfull map) the firmware UPD_FIRMWARE_UZB_STATIC_2ch_ZME_05_1b_04000001_ZME_05_24_04000001.bin (that AFAIK should upgrade from version 5.27 to 5.36).
I run the update and it never finished....
8899ae1b-c9cc-488b-ba15-870bbf66c044-image.png After 2 hours waiting for nothing, I finally CTRL-C and removed and reinserted the USB stick that is not recognized anymore.

I really think I won a nice peace of plastic usb shaped, but in case someone has an idea, I would be pleased to read your coment.

Regards

Hey Patrick, had to switch over my HA VM from VirtualBox to VMware since VirtualBox stopped playing well. Anyways I updated the IP address to the new VM IP and deleted the Long Lived Access Token and created a new one just in case (copy pasted the new token into the config file). Tried rebooting both the HA machine and the MSR one too and MSR is still not connecting. The only thing I have not tried yet is creating another controller entry, but I am worried it may create all new entities for everything forcing me to redo all my logic. Here are some logs:

[latest-22258]2022-09-20T21:17:24.749Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:17:24.749Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:17:24.749Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:18:09.753Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket [latest-22258]2022-09-20T21:18:24.761Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:18:24.761Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:18:24.761Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:19:01.083Z <VeraController:INFO> VeraController#vera 0 dead entities older than 86400000s purged [latest-22258]2022-09-20T21:19:14.780Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket [latest-22258]2022-09-20T21:19:29.785Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:19:29.785Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:19:29.785Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:20:24.791Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.8.113:8123/api/websocket [latest-22258]2022-09-20T21:20:39.813Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error]Error: Opening handshake has timed out [latest-22258]2022-09-20T21:20:39.820Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.8.113:8123/api/websocket closed during open/negotiation [latest-22258]2022-09-20T21:20:39.820Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error]Error: Opening handshake has timed out

I've been trying to figure out Reactor but I'm not very good at programming.

I have two scenes in VERA.

One scene should only run during the DAY and then stop running.
One scene should only run during the NIGHT and then stop running.

My scenes start off at the right times, but they do not turn off. I created a Sunrise/Sunset Reactor trigger and added it as a condition to each of my scenes.

However, the Reactor trigger when tripping or untripping does not prevent my Vera scenes from running. It will start them correctly the first day, but after that, both scene stay running and fight with each other. What am I doing wrong?

Thanks for any help!

If you are interested, here are the actions I wish to perform with each scene.

FARM STAND - DAY (runs at Sunrise)

Turn ON a device called LETTUCE LAMP
2a) Every 60 min, turn ON a device called LETTUCE PUMP
2b) Wait 15 min then turn OFF a device called LETTUCE PUMP

FARM STAND - NIGHT (runs at Sunset)

Turn OFF a device called LETTUCE LAMP
2a) Every 135 min, turn ON a device called LETTUCE PUMP
2b) Wait 15 min then turn OFF a device called LETTUCE PUMP

This sounds simple, but I cannot figure out how to disable these scenes when the theyre not supposed to run.

I am no longer using any VERA scenes. I am only using a REACTOR trigger and activities.

Will my activities do what I need them to do? See below:

Here's what I am trying to accomplish:

AT SUNRISE

Turn ON a light called LETTUCE LAMP and keep it ON.
2a) Turn on a device called LETTUCE PUMP for 15 min each hour.
2b) Repeat the pump cycle all day long.

AT SUNSET

Turn OFF a light called LETTUCE LAMP and keep it OFF.
2a) Turn on a device called LETTUCE PUMP for 15 min then wait 2 hours..
2b) Repeat the pump cycle all night long.

TRUE.jpg FALSE.jpg

@toggledbits

Patrick,
I've just imported a large set of rules from Vera, and I had already played with creating rules in MSR that are mixed throughout the existing Vera rules. Is there any sort of way to "find/replace" in MSR, so I can find all matches to the old rules and replace them with the new ones?

@toggledbits

Patrick,
Yesterday I migrated a large luup Reactor group over from Vera to MSR, following the directions to importing it from Vera in the documentation. One of the odd things in the migration was the conditional rules for House Modes. Many of my rules had conditions such as "House Mode is any of Home, Night, or changes to Away.

The way the import did it was changes from 1,3 to null. This importation did not seem to trigger rules correctly.

I was able to fix all the instances by creating multiple triggers in a group:

Entity Attribute: House Mode (vera>housemode) x_vera_housemode.mode contains home
OR Entity Attribute: House Mode (vera>housemode) x_vera_housemode.mode contains night

Is this what you are expecting in importation?

Good morning all,
This weekend I've been playing around with Home Assistant as a replacement (long term) for my aging Vera platform. I'm pretty amazed how much more capability it has. On the other hand, the sheer amount of variables it pulls in from devices is massive.

In any case, I have added Google Calendar into Home Assistant for things like Federal Holidays and my daughter's school calendar. It connected to them without issue, which I had been having problems with in Vera an GCal3.

I connected MSR to Home Assistant, so I can start using some of the systems I've integrated into Home Assistant in MSR, and continue migrating my luup Reactor rules over to MSR. Now I'm trying to create a rule based on if today is a Federal Holiday or not. Reactor sees the calendar just fine, however, for whatever reason, it's not pulling data for today, but the next event, which in this case is Columbus day, three weeks away. The attribute that is pulling this is x_haas_attr.message.

I tested with my daughter's school calendar, and it did have an entry for today, and none of the other values seemed to be different, such as a "true" or something to tell me there is an entry.

a8478a6e-d8eb-4572-ac84-c94ff012a1ec-image.png

60632486-e80b-4f0f-aed9-dc67113689a4-image.png

ab04cd0f-f849-4e14-be7d-f4c00735da77-image.png

The only thing I've been able to come up with, is there is a start_time attribute, which shows the date as 2022-10-10 00:00:00

1cbe4526-7f63-4329-a088-b331f1d03376-image.png

The only thing I can think of is there might be a way to compare the current system date to that date, but I can't seem to figure that out in MSR.

Has anybody done this? Any suggestions?