Hi everybody!
I was following this web site as non-member. Finally I have a new Synology Nas to try the new @toggledbits 's reactor project and this post is first of all to thank @toggledbits for his effort and passion to share his projects and to make them accessible even for those who are not a programmer. I know many of you reading the posts from the vera community and would like to express my gratitude for the advice you give to understand things. So a big Thanks and congratulations to Patrick for this new project !!!
I just installed MSR and I am excited to try it out!
N
noelab
@noelab
Edit: Solved in latest-26221.
Bare-metal latest-26193
I have this group:
"OKforLarm":
name: OK för Larm
select:
- include_controller: vera
- include_capability: door_sensor
filter_expression: entity.attributes.door_sensor.state
It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
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.
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group.
First of all, I think I found a typo in the doc:
primary_attribute: "binary_sensor.state"
primary_attribute_value: |
d = false;
each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d,
d
I think the correct code snippet is d = false,
All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
Love openLuup - it just keeps working perfectly.
I started looking at trying to add a gen4 Shelly device to the Shelly plugin via L_ShellyBridge.lua. The plugin is a little uncooked (no rudeness intended), so a bit of a rabbit hole for me.
All of a sudden no console pages available in either Firefox or Chrome. AltUI works perfectly and all the log files indicate no errors. openLuup still running everything works as it should - just no console pages.
I possibly screwed something up but any recently changes files show no problems. The original/ backup of L_ShellyBridge.lua was reinstated but still no console.
Bit stumped on this one. Not sure how to debug. Any ideas?
Hey @toggledbits
One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets.
#1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth.
Both will be appreciated, but I understand the technical challenges. Thanks!
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch.
# Multi-System Reactor template docker-compose.yml (version 22160)
#
# Change the lines indicated by "DO"...
#
services:
reactor:
container_name: reactor
environment:
# DO change the TZ: line to set your local time zone.
# See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
TZ: GB
#
# DO NOT change this path. Your directory location is in "source" below.
REACTOR_DATA_PREFIX: /var/reactor
# DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4)
image: toggledbits/reactor:latest-aarch64
restart: "always"
expose:
- 8111
ports:
- 8111:8111
volumes:
# DO change the /home/username/reactor below to the directory you created for
# your local data; DO NOT change the /var/reactor part
- /home/pi/docker/reactor:/var/reactor
- /etc/localtime:/etc/localtime:ro
tmpfs: /tmp
It appears that Ezlo is going to new levels of paid subscription for cloud services supporting Vera hubs. I have to congratulate them. It will soon be 8 years since Ezlo acquired Vera, and despite their purported financial and "intellectual" capital, they have to date not produced a viable full replacement for Vera. Now they are going to charge extra for services for a platform that they stopped updating years ago.
If you know anyone who hasn't yet fully moved on from Captain Ahab's White Whale Chase, please remind them that my Decouple project is still up on Github to decouple a Vera Plus/Secure/Edge from Vera/Ezlo's cloud services. Veras have been said to misbehave when they can't reach the mother ship.
I have also written my first new Vera plugin in... six years? more?... the AlertPushover project will send Vera hub alerts to Pushover, so you can still get messages generated by your Vera hub without paying for Ezlo's cloud service. It's crude but functional (i.e. better than nothing/worth every penny paid).
These two projects won't replace the functionality of their cloud service and app for those who need those things. But any that don't, this may help bridge the gap. Hopefully these stragglers who have waited so long and been disappointed so often will get the idea that it's time to move on.
Posts
-
Release 1.0.0 -
Dashboard extended to guests with visible/hidden icons - an idea?Hi, I like a lot the MSR Dashboard: it's quick and easy without an authentication system and this is great.
Not really a good idea if I give this possibility to my wife to power off all switches included the nas with MSR or to a guest to power off the light in my room.
Is it scheduled to have a main dashboard and a guest dashboard? as a sub-dashboard
Maybe from the main dashboard, using a built-in GUI editors that can set icons as visible or hidden and automatically reflect on a guest dashboard with a different ip
Just an idea
for MSR -
Merry Christmas/Happy HolidaysHappy Holidays and very best wishes for a wonderfull and reactor New Year!
-
Synology Docker installation@librasun yes, of course I agree with you. In Vera I based my logic using a virtual dimmer (Switchboard Plugin) per room to interact with Alexa commands behind conditions/rules in a Reactorsensor per room and only some global reactor for the house. In this way it is possible to have until 100 voice commands per room associated to 100 preset rules per dimmer, controlling them in web gui, in mobile app or alexa. So at the moment trying to understand if there is a new approach in MSR to emulate virtual devices or to find another way.
-
Plugin InfluxFeed - Selecting Capabilities for Export - how toThanks to you!
The fix is working.
Now I can truck energy consuption on Influxdb. The idea is to try to make in MSR what in HA is doing with utility_meter, Trend and Lovelace UI togheter. Maybe in future we will see a standard MSR energy plugin too.
-
Power_switch.state - no change state - EzloPlus - Msr v. 21351-a3aef - Synology DockerHi, it seems working ok. Thanks! If you need more infos to test, just tell me how I can produce them.
L Bulb FibaroDimmer2 ezlo>device_61425874129e29124dfcd75e 0.65 7:30:07 PM dimming.level=0.65 dimming.step=0.1 energy_sensor.units="KWh" energy_sensor.value=11.3400001525879 power_sensor.units="W" power_sensor.value=6.90000009536743 power_switch.state=true x_ezlo_device.battery_powered=false x_ezlo_device.category="dimmable_light" x_ezlo_device.manufacturer="Fibaro" x_ezlo_device.model="FGD-212" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2024129e2912114c093b" x_ezlo_device.status="idle" x_ezlo_device.subcategory="dimmable_in_wall" x_ezlo_device.type_id="271_258_4096" x_ezlo_item.dimmer=65 x_ezlo_item.dimmer_down=0 x_ezlo_item.dimmer_stop=0 x_ezlo_item.dimmer_up=0 x_ezlo_item.electric_meter_kwh=11.3400001525879 x_ezlo_item.electric_meter_watt=6.90000009536743 x_ezlo_item.hw_state="hardware_failure" x_ezlo_item.load_error_state="unknown" x_ezlo_item.meter_reset=0 x_ezlo_item.over_current_state="unknown" x_ezlo_item.over_load_state="unknown" x_ezlo_item.power_surge_state="no_surge" x_ezlo_item.switch=true x_ezlo_item.voltage_drop_drift_state="unknown" x_ezlo_object.id="61425874129e29124dfcd75e" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Fibaro","FGD-212",null] zwave_device.node_id=27 zwave_device.version_info=null Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighborsanother
K Bulb Domitech ezlo>device_61423589129e29124dfcd756 0.65 7:35:42 PM dimming.level=0.65 dimming.step=0.1 power_switch.state=true x_ezlo_device.battery_powered=false x_ezlo_device.category="dimmable_light" x_ezlo_device.manufacturer="Domitech" x_ezlo_device.model="ZE27EU" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2020129e2912114c093a" x_ezlo_device.status="idle" x_ezlo_device.subcategory="dimmable_bulb" x_ezlo_device.type_id="526_19522_12596" x_ezlo_item.dimmer=65 x_ezlo_item.dimmer_down=0 x_ezlo_item.dimmer_stop=0 x_ezlo_item.dimmer_up=0 x_ezlo_item.switch=true x_ezlo_object.id="61423589129e29124dfcd756" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Domitech","ZE27EU",null] zwave_device.node_id=26 zwave_device.version_info=null Capabilities: dimming, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighborsanother
H Bulb Widom dimmer ezlo>device_6147578c129e29124dfcd814 1 7:36:56 PM dimming.level=1 dimming.step=0.1 energy_sensor.units="KWh" energy_sensor.value=0.651000022888184 power_sensor.units="W" power_sensor.value=2.47000002861023 power_switch.state=true x_ezlo_device.battery_powered=false x_ezlo_device.category="dimmable_light" x_ezlo_device.manufacturer="Unknown" x_ezlo_device.model="Unknown" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2012129e2912114c0938" x_ezlo_device.status="idle" x_ezlo_device.subcategory="dimmable_in_wall" x_ezlo_device.type_id="329_4628_2560" x_ezlo_item.dimmer=100 x_ezlo_item.dimmer_down=0 x_ezlo_item.dimmer_stop=0 x_ezlo_item.dimmer_up=0 x_ezlo_item.electric_meter_kwh=0.651000022888184 x_ezlo_item.electric_meter_watt=2.47000002861023 x_ezlo_item.meter_reset=0 x_ezlo_item.switch=true x_ezlo_object.id="6147578c129e29124dfcd814" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Unknown","Unknown",null] zwave_device.node_id=41 zwave_device.version_info=null Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors -
Need Testers@toggledbits happy to help!
I'm running Reactor>Docker>Synology NAS
-
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.040 = L Bulb Ball 1 Z-RGBW2
036 = R3 Bulb Roof 1 HKZW-RGB01
033 = R3 Bulb Wall 1 A-ZWA002
Utility Meter
