I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).

Anyway, here's my reactor-mqtt-contrib package:

GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor

Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.

Simply download yaml files (everything or just the ones you need) and you're good to go.

I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.

The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.

Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests 🙂

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 recent thread on supporting the ZRC-90 Z-Wave scene controller got me to wonder, what does everybody use and like?

I'll start... oh, and no dashboards. I want to hear from you all about dedicated scene controller devices. Dashboards and apps are great to a point, but my experience is that higher WAF is achieved with (a) a dedicated device (b) in a known location (c) with predictable functions and (d) no extra steps to operate (just walk up to it and push a button -- same effort as a light switch/dimmer). She's not wrong. It's a pain to unlock the phone, find the app, open the app, find the device, tap the device, when you can just walk across the room and push a button. Bonus points for something that can be labeled readably (low WAF for stuck-on tape/thermal labels).

I have a ZRC-90 and it's great, but it was temperamental to get working on Vera, and wasn't smooth sailing when it made the move to Z-Wave JS either. A couple of include/exclude cycles were needed to get it fully working on both. Since then, I've done a battery change, and while the buttons work as reliably as ever, the device continues to report the old battery level despite having a measurably fresh battery for over a year now. But I would still recommend it.

I have a Hank 4-button that is probably the best and most reliable battery-operated scene controller I have ever used. It's small and unobtrusive, so it lives on a lamp base in our living room and controls the room's mood lighting. I'm not sure they're still available. RIP.

I just ran across the Minoston MR40Z on Amazon, and I may try one of those. It looks like an installed (in-wall) Decora switch, but the buttons are actually a removable remote that you can pull off the wall and take to the couch. No line power required. Kinda cool. Maybe a good Hank replacement. But, I've never heard of this manufacturer before, and the concern is always "will I be able to buy more/replacements in one/two/five years?"

Among the wired controllers, the Zooz ZEN32 seems to be the most popular modern unit. I like it, but the LEDs are too small for my aging eyes to discern their color in daylight -- they are pin-head sized. Four of the five buttons are too small to label, so low WAF.

When I started my Z-Wave network, I used the Leviton four-button scene/zone controllers (VRCS4 and VRCZ4), and these are still all over my house. They're glitchy first-gen Z-Wave stuff (Vizia RF+ actually, so compatible but with proprietary features that aren't usable). They're now discontinued for Z-Wave. Leviton's newer units are WiFi, so if I go that route, it's HomeKit via Home Assistant for those.

During the pandemic lock-downs, I built a touch-screen scene controller using an Adafruit PyPortal. It had screens with 1 to 8 labeled, colorable soft buttons that could either perform a device function (i.e. publish to MQTT) or take you to another screen, so it was the love-child of scene controller and dashboard. Wife found it agreeable. But it was just a prototype. Memory limitation of the device was an issue because the PyPortal is really an inexpensive teaching device with a big load of Circuit Python overhead, and the graphic display needs a lot of RAM, so it was severely limited. I'm sure it could work out with the right micro and programming closer to the bare metal. Packaging and powering would also need to be addressed. And, at the end of the day, while "cute," it doesn't seem like something I would want to sell with the house if we ended up moving some day.

So, I'm interested in what others are doing and using, or more specifically, what your significant others are comfortable with and willing to use.

I've been using Vera Plus for nearly 10 years now but it's time to move on. On top of that we've moved from the previous house whereupon I took all the Z-wave door sensors, locks and switches with me and reverted the pool to manual control, grabbing the Autelis which I won't use now since the new pool we built has Pentair IntelliCenter.

I have the Vera Plus connected and have it controlling a couple of Honeywell Z-Wave thermostats and a couple of lights but It seems to just be slower and slower as it ages. I have an intel i3 NUC that is probably 6 years old but figure it's probably powerful enough to control HA going forward. I also dabbled with HomeSeer but it seems to cost a fortune for plugins. I have HS4 and a G3 Z-Wave Plus dongle from them.

How do I get started? I'm thinking I'll just unpair all my devices from the Vera Plus and add them to HA and then set up Reactor to do the logic but is there a way to migrate? Should I use Open LUA instead?

Lots of questions but I'm ready to get started an any help would be appreciated.

I currently have an HVAC system in the attic - for heating and A/C. 120v is supplied to the unit to run the gas heating. A/C uses 240v. I have an ecobee thermostat...which sometimes goes offline....not often. When it goes offline, I need to turn the 120v power to the HVAC system off and then back on (the ecobee gets its power from the HVAC system). That resets the ecobee and all is fine. I spend the summer away from this house and if the ecobee goes offine..I have no current method to reset the HVAC 120v power remotely. My idea is to replace the current 120v plug in the attic with a smart plug...then I can remotely turn the 120v power off and the ecobee will reset and come back online. I use Wyze and Lutron Casita in the house currently and was hoping I could find an in-wall smart plug from Wyze or Lutron. Obviously, I don't need diming, etc...just the ability to turn the plug power on/off. I've seen some options...but one problem I have is the attic can reach up to 135F in the summer...many of the smart plugs I've seen are not rated for that temperature. Might any of you have any thoughts on a smart plug I might want to look at? I don't want to invest in anything that would require a new hub - so either WiFi based or Casita HUB based. I need 120v and 15amp ratings. Thanks in advance.

Hi @toggledbits.

After a couple of weeks, I noticed that my Remotec zrc90 isn't working as expected.

Scenes are working in ZWaveJS, but this device has a strange behavior: the scene change, but then it's set again to null. In Reactor, this remains null:

battery_power.level=0.7 battery_power.since=1725817957361 x_debug.dt={"description":"Scene master 8 button remote","model":"BW8510/ZRC-90US","default_name":"Scene master 8 button remote","manufacturerId":21076,"productType":0,"productId":34064} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=70 x_zwave_values.Central_Scene_scene_001=null x_zwave_values.Central_Scene_scene_002=null x_zwave_values.Central_Scene_scene_003=null x_zwave_values.Central_Scene_scene_004=null x_zwave_values.Central_Scene_scene_005=null x_zwave_values.Central_Scene_scene_006=null x_zwave_values.Central_Scene_scene_007=null x_zwave_values.Central_Scene_scene_008=null x_zwave_values.Central_Scene_slowRefresh=null x_zwave_values.Manufacturer_Specific_manufacturerId=21076 x_zwave_values.Manufacturer_Specific_productId=34064 x_zwave_values.Manufacturer_Specific_productType=1 x_zwave_values.Version_firmwareVersions=["1.1","1.1"] x_zwave_values.Version_hardwareVersion=3 x_zwave_values.Version_libraryType=2 x_zwave_values.Version_protocolVersion="4.5" x_zwave_values.Wake_Up_controllerNodeId=1 x_zwave_values.Wake_Up_wakeUpInterval=0 zwave_device.capabilities=[91,114,128,132,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Remote Controller" zwave_device.impl_sig="24242:1:22315:1" zwave_device.is_beaming=false zwave_device.is_listening=false zwave_device.is_routing=false zwave_device.is_secure=false zwave_device.manufacturer_info=[21076,1,34064] zwave_device.max_data_rate=null zwave_device.node_id=154 zwave_device.specific_class="Simple Remote Control" zwave_device.status=2 zwave_device.status_text="awake" zwave_device.version_info=[null,"1.1"] zwave_device.wakeup_interval=0

Anything I could look at? Thanks.

I have set up HA in a VM Box Virtual Machine and am progressing along.

I got new Kwikset Connect 620 door locks and got one connected to HA via Z-Wave JS and automated via Keymaster which is quite convoluted but I got it done.

I went to install the second lock and got it connected to HA via Z-Wave JS but am not being successful getting it to work properly in Keymaster.

Screenshot 2024-08-28 084902.png

Screenshot above is the second lock for the laundry room. It shows it is set up but the codes don't seem to be working.

I have not installed the lock yet and have not set the handing either. Maybe this is the issue but IDK.

Anyone have experience setting up locks in HA using Keymaster that can help would be great!

I am trying to run a reaction that turns on lights if a sensor has not been tripped for 2 minutes. Basically, when a garage door is open, turn on inside lights if nothing has been sensed for 2 minutes. My question has to do with the expression/variable for "Last Seen". The variable never gets updated over time since the last seen event never changes.

Screenshot 2024-09-02 191632.png

In the screenshot above, the reaction checks for any garage door as well as the variable called "GarageLastEntry". The expression for this variable is displayed below:

Screenshot 2024-09-02 191651.png

The problem that I am experiencing is that the variable never changes over time. I understand that this is because the "last seen" variable does not change over time when there is no activity. In this screenshot, the value shows 0.029... This can also be seen as the current value in the original reaction screenshot above. After 10 minutes, this value should be 10. However, when a garage door is opened, the variable does not get updated and thus the rule does not become true since .029 is less than 2.

When I go to the variable and click on the > icon, the variable then gets updated as expected as seen below:
Screenshot 2024-09-02 191711.png

So the ultimate question is, how do I use a rule that can use a variable such as "last seen"? Do I need to create another variable or reaction that multiplies this by 1 every minute? From what I read in the manual, a variable is evaluated every time it is included in a reaction. But this is not what I am seeing.

I also want to ask another question related to this variable. It seems like Reactor continuously deletes this variable and I have to keep recreating it? I have never experienced this with MSR so wanted to ask if this is a common problem or if my definition is causing this.

Any info is appreciated!!!

Hi, @toggledbits!

I have a question about the execution behavior. See the code below, and I'll explain the situation.

12957c3e-ff06-46c9-929d-b53f936665df-image.png

This is a routine that, at a certain point, determines that the desktop on which the VM hosting the Reactor is located receives an instruction to perform a shutdown (Shell Command).

When this happens, the desktop is turned off, and then Hubitat detects by a "ping" that the VM has been down, waits 15 seconds, turns off the power to this desktop, and then 15 seconds later turns on the desktop with the Reactor VM again.

After restarting the desktop, the VM is loaded, and the Reactor is triggered. Still, the following problem occurs: I expected that when the rule was continued to be executed again, the next step would be executed, that of the 900-second delay after shutdown, but the Shell command is executed again, and then it goes into a loop, the rule does not advance.

To break the loop, I first have to make the VM not load, change the desktop password, and then start the VM. In this case, Reactor generates an error when trying to execute the Shell Command because of the invalid password and then finishes the routine following the 900 delay step.

b58b0d4a-d6c1-4fe3-bab7-4222acea9607-image.png

Is my interpretation that when it returns, the routine should continue to the next step that has not yet been executed incorrectly? Or does Reactor, through the shutdown command, interpret that it hasn't finished this step and keep trying, which is the correct reaction?

Thanks for clarifying.

So, it was time for me to move from Vera to something modern. It served me well, but I have new devices I want to add and old that I want to fully use. I have 3 weeks off in August, so plenty of times to tweak things.

Long story short, I moved and turned off my two Veras (one prod, one dev).

Hardware:

Zwave.me controller, updated to FW 5.39, SDK 6.28.1 (it is necessary, since my Veras have the latest FW available). I opted for a 500 controller because of all the drama with 700/800 and the need to stay on something stable.

I have 60 Zwave devices, so starting from scratch was a big no for me.
I started from this famous guide, after taking a backup from the Vera Prod to the Vera Dev:

GitHub - rafale77/Z-Way: Zway plugin for openLuup GitHub - rafale77/Z-Way: Zway plugin for openLuup

Zway plugin for openLuup . Contribute to rafale77/Z-Way development by creating an account on GitHub.

But it was not working. So, the route I went is:

Go the Vera UI and go under Settings/Z-wave settings, take a screenshot (HouseId in particular). take a backup from the prod system extract the file /etc/cmh/user_data.json.lzo from the backup move the file to the /tmp directory of your dev system execute pluto-lzo d /tmp/user_data.json.lzo /tmp/user_data.json open and edit the file, looking for a port node with something like /dev.. and put /dev/ttyACM0 inside. save the file. run pluto-lzo c /tmp/user_data.json /tmp/user_data.json.lzo copy the .lzo file to the backup, in the same position insert the Zwave key into the USB of your dev Vera reboot the dev Vera wait a lot for it to finish ⚠️ it will probably say that it cannot start ZWave, don't worry Go the Vera UI and go under Settings/Z-wave settings, you should see the old HouseId. Anyway, double check with the screenshot you took previously: if it matches, you've moved your Zwave Network to the new controller! 🎉

Shutdown the Veras, take the USB Key with your ZWave network and move it to ZwaveJS!
I've installed it via Docker, very easy. Go for ZwaveJS UI, so you got the UI as well.
Interview the nodes, have patience. Some battery nodes will need wake-ups, others will complete automatically. I had to re-pair a couple of devices because of incorrect pairing with Vera (security and non-security mixed together). In this case, pro tip: reset the device, and then use the replace function from ZWave JS, to have the same node id.

Now, if you're already running under Reactor, you'll need to rewrite all your logic. I asked ChatGPT to write me a Powershell script to get the device from the Veras and build the new naming convention. The logic is that AltId in Vera is in fact the ZWave Node ID, and on Reactor you'll get device like zwavejs>nodeid-endpoint (ie: 95-0, 95-1, etc). So, I built a script that replaced all the occurrences from the storage of Reactor (did I mentioned to do a lot of backups?) and set the name via ZwaveJS MQTT apis. Then, I build an Excel file (thanks ChatGPT!) and renamed all the endpoints in Reactor (manually, no APIs to do so). It took me about an hour.

Now, no more trip/untrip lost along the radios, and a blazing fast ZWave network to enjoy.

Since a couple of devices are recognized in a different way, I had to re-write a couple of rules (and wait a couple of fix here and there by @toggledbits for devices not properly recognized, thanks!), but I was OK in a couple of days, and ready to run by the first afternoon, so I maintained an high WAF.

Now, I could experiment the joy of SmartStart and proprietary commands. 🎉

Thanks to the people that moved before me, inspired me and to @toggledbits for the incredible platform that has built in the latest years! Feel free to ask question if you need help.

I made a video here on how I use Python to store temperature readings from sensors in a database!

As our family grows and life gets busier, I've been thinking about upgrading to smart door locks. With kids often forgetting keys and elderly parents needing easier access, the idea of fingerprint and facial recognition seems like the perfect solution. I also love the idea of being able to lock and unlock the doors remotely, especially when we're away. Has anyone else implemented smart locks in a similar situation? How has it impacted your daily routine and overall home security?

If you’re like me and still running HABridge to control your devices locally via Alexa, you might need to tweak your endpoints to call Reactor via HTTP. Here’s the best way to do it, IMO:

Insert the Reactor Canonical ID (e.g., zwavejs>71-1) into the MapID field, but make sure it’s URL-encoded like this: zwavejs%3E71-1.

Then, configure these endpoints as needed:

On: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.on Off: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.off Dim: For lights: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/dimming.set?level=${intensity.decimal_percent} For roller shutters: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/position.set?value=${intensity.decimal_percent} Color: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/rgb_color.set_rgb?r=${color.r}&g=${color.g}&b=${color.b}

Just replace [ReactorIP] with your actual IP address. By using these placeholders, you can standardize your endpoints across all devices, making maintenance easier.

This setup works with any device mapped under MSR, regardless of the controller (ZWaveJS, Vera, HASS, OpenSprinkler, virtual, MQTT, DynamicEntities, etc.). If you need different calls, just go to the entities, get the action and parameters, and adjust accordingly. Enjoy super fast access to your devices via Alexa!

If you're migrating from Vera, the endpoints are (URL-encoded) in a file called device.db, in JSON format, under your config. You'd write a script to align the new endpoints to the new one, if you prefer to do it automatically. YMMV.

Hi all, I'm looking for a 20 amp (minimum) smart switch (physical, so as to either tap switch or remote/Alexa/HomeKit/etc) so that I can control several outdoor Infratech heaters (220V). If they're outdoor rated, even better. Thanks.

Hi @toggledbits ,
I'm slowly moving my ZWave network from Vera to ZWaveJS. I successfully cloned my ZWave network using a spare Vera Edge (a new post for the community later when I'll be fully back from vacation) and I'm testing a couple of things before moving everything to ZWaveJS.

In the meanwhile, I have a couple of venetian blinds connected to Fibaro Roller Shutters 2 (FGR222) and I'm using some proprietary ZWave commands to control the tilt position, that right now I'm sending via Vera (with some code from the old place, messing with this):

af7f883c-f49e-419c-a2fe-8669572e3792-image.png

The ZWaveJS values are reported via this:

x_zwave_values.Manufacturer_Proprietary_fibaro_venetianBlindsPosition=0 x_zwave_values.Manufacturer_Proprietary_fibaro_venetianBlindsTilt=0

I hope there's a way to expose a separate device to control the tilt position directly, without doing the mess I'm doing now. Let me know if you need some files. Thanks.

As per @toggledbits request, new topic.

Position and cover commands not working and position/cover attributes are incorrect. Dimming is OK.

cover.state=null dimming.level=1 dimming.step=0.1 energy_sensor.units="kWh" energy_sensor.value=0.41 position.value=null power_sensor.units="W" power_sensor.value=0 power_switch.state=true x_debug.dt={"entity_class":"Cover","match":"deviceClass.generic.key=17;deviceClass.specific.key=6","capabilities":["cover","toggle","position"],"primary_attribute":"cover.state"} x_zwave_values.Meter_reset=null x_zwave_values.Meter_value_65537=0.41 x_zwave_values.Meter_value_66049=0 x_zwave_values.Multilevel_Switch_Down=null x_zwave_values.Multilevel_Switch_Up=null x_zwave_values.Multilevel_Switch_currentValue=99 x_zwave_values.Multilevel_Switch_duration="unknown" x_zwave_values.Multilevel_Switch_restorePrevious=null x_zwave_values.Multilevel_Switch_targetValue=99 x_zwave_values.Notification_Power_Management_Over_current_status=0 x_zwave_values.Notification_System_Hardware_status=0 x_zwave_values.Notification_alarmLevel=null x_zwave_values.Notification_alarmType=null zwave_device.capabilities=[38,50,113] zwave_device.endpoint=1 zwave_device.failed=null zwave_device.impl_sig="24225:1:22315:1" zwave_device.manufacturer_info=null zwave_device.node_id=148 zwave_device.version_info=null

Thanks!

Another one for you, @toggledbits.

I have two water sensors (same device, NAS-WS01Z), but one is reporting leak_detector.state=true even if no alarm is detected (I double checked from ZWaveJS UI):

battery_power.level=0.86 battery_power.since=null leak_detector.state=true x_debug.dt={"entity_class":"Notification Sensor","match":"deviceClass.generic.key=7"} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=86 x_zwave_values.Binary_Sensor_Water=false x_zwave_values.Configuration_Alarm_Activity_Duration=5 x_zwave_values.Configuration_Alarm_Beep=1 x_zwave_values.Configuration_Alarm_Duration=120 x_zwave_values.Configuration_Alarm_Interval=null x_zwave_values.Configuration_Basic_Set_Level=255 x_zwave_values.Configuration_First_Alarm_Activity_Duration=null x_zwave_values.Configuration_Water_Detection=1 x_zwave_values.Manufacturer_Specific_manufacturerId=600 x_zwave_values.Manufacturer_Specific_productId=4229 x_zwave_values.Manufacturer_Specific_productType=3 x_zwave_values.Notification_Water_Alarm_Sensor_status=null x_zwave_values.Notification_alarmLevel=0 x_zwave_values.Notification_alarmType=0 x_zwave_values.Version_firmwareVersions=null x_zwave_values.Version_hardwareVersion=null x_zwave_values.Version_libraryType=null x_zwave_values.Version_protocolVersion=null x_zwave_values.Wake_Up_controllerNodeId=1 x_zwave_values.Wake_Up_wakeUpInterval=43200 zwave_device.capabilities=[48,112,113,114,128,132,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Notification Sensor" zwave_device.impl_sig="24225:1:22315:1" zwave_device.is_beaming=false zwave_device.is_listening=false zwave_device.is_routing=true zwave_device.is_secure=false zwave_device.last_wakeup=1724143899220 zwave_device.manufacturer_info=[600,3,4229] zwave_device.max_data_rate=null zwave_device.node_id=114 zwave_device.specific_class="Notification Sensor" zwave_device.status=1 zwave_device.status_text="asleep" zwave_device.version_info=[null,null] zwave_device.wakeup_interval=43200

here's the other one, correctly report the leak status:

battery_power.level=1 battery_power.since=null leak_detector.state=false x_debug.dt={"entity_class":"Notification Sensor","match":"deviceClass.generic.key=7"} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=100 x_zwave_values.Binary_Sensor_Water=false x_zwave_values.Configuration_Alarm_Activity_Duration=5 x_zwave_values.Configuration_Alarm_Beep=1 x_zwave_values.Configuration_Alarm_Duration=120 x_zwave_values.Configuration_Alarm_Interval=1 x_zwave_values.Configuration_Basic_Set_Level=255 x_zwave_values.Configuration_First_Alarm_Activity_Duration=60 x_zwave_values.Configuration_Water_Detection=1 x_zwave_values.Manufacturer_Specific_manufacturerId=600 x_zwave_values.Manufacturer_Specific_productId=4229 x_zwave_values.Manufacturer_Specific_productType=3 x_zwave_values.Notification_Water_Alarm_Sensor_status=0 x_zwave_values.Notification_alarmLevel=null x_zwave_values.Notification_alarmType=null x_zwave_values.Version_firmwareVersions=["2.54"] x_zwave_values.Version_hardwareVersion=48 x_zwave_values.Version_libraryType=6 x_zwave_values.Version_protocolVersion="4.5" x_zwave_values.Wake_Up_controllerNodeId=1 x_zwave_values.Wake_Up_wakeUpInterval=43200 zwave_device.capabilities=[48,112,113,114,128,132,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Notification Sensor" zwave_device.impl_sig="24225:1:22315:1" zwave_device.is_beaming=false zwave_device.is_listening=false zwave_device.is_routing=true zwave_device.is_secure=false zwave_device.last_wakeup=1724105239533 zwave_device.manufacturer_info=[600,3,4229] zwave_device.max_data_rate=null zwave_device.node_id=113 zwave_device.specific_class="Notification Sensor" zwave_device.status=1 zwave_device.status_text="asleep" zwave_device.version_info=[null,"2.54"] zwave_device.wakeup_interval=43200

Also, both seems to have no primary value. Thanks.

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

How to add MSR to Home Assistant?

Hi-

I have an android media player entity publishing from HA. I watch for changes in transport state and media title to trigger some actions.

Though those attributes report as expected, the set rule is being throttled for possible flapping.

There is an attribute for media position that continually updates, I suspect it is causing the evaluations to run constantly.

The workaround I am seeking is to ignore those attributes in HA or MSR. Anyone know how, or have a better idea??

Thx
Btw- this problem has spanned versions of HA and reactor, but I am current on both. Too current on HA for transparency, but the issue has survived several updates.