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!
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
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
If you are using the armv7l docker image, the OpenJS Foundation that publishes node is no longer producing 32-bit builds as of v24. That means the last supported LTS version of node for armv7l is v22, which will go End-of-Life in May 2027.
Therefore, the Reactor armv7l image is now deprecated and will only be produced until node v22 goes EOL, and I will not publish armv7l images beyond that date.
If you are running an RPi 3 or earlier with Reactor, you are on this image, and will need to upgrade hardware to a 64-bit model and use the arm64 image. If you need help getting it done, ask in this category.
Home Assistant Service Call - JSON/Formatting Question
-
Hello -
As the subject implies, I'm trying to make a Service Call to Home Assistant and having formatting issues. I struggle with JSON so hoping someone can provide me direction.
Here's an example of working YAML in Home Assistant:
service: rinnai.start_recirculation data: recirculation_minutes: 5 target: entity_id: water_heater.bully_house_water_heater -
Hello -
As the subject implies, I'm trying to make a Service Call to Home Assistant and having formatting issues. I struggle with JSON so hoping someone can provide me direction.
Here's an example of working YAML in Home Assistant:
service: rinnai.start_recirculation data: recirculation_minutes: 5 target: entity_id: water_heater.bully_house_water_heaterUpdated version was able to get past the parser but then get the below error from HASS.
[stable-22168]2022-08-22T21:54:52.506Z <HassController:null> HassController#hass: sending payload for x_hass_system.call_service on System#hass>system action: [Object]{ "type": "call_service", "service_data": { "data": "recirculation_minutes: 5", "target": { "entity_id": "water_heater.bully_house_water_heater" } }, "domain": "rinnai", "service": "start_recirculation" } [stable-22168]2022-08-22T21:54:52.511Z <HassController:ERR> HassController#hass request 1661205292508<2022-08-22, 5:54:52 p.m.> (call_service) failed: [Object]{ "id": 1661205292508, "type": "result", "success": false, "error": { "code": "invalid_format", "message": "extra keys not allowed @ data['data']" } }Clearly doesn't like "data" being sent again. But I'm unclear how to send the "recirculation_minutes" and then the following "target" / "entity_id" parameter.
-
this is a total shot in the dark but try this. Still figuring out calling services via MSR myself
{ "recirculation_minutes": "5", "target": {"entity_id": "water_heater.bully_house_water_heater"} }@pabla Closer! Passes the parser and now a new error... I will play with this a bit later after meetings...
[stable-22168]2022-08-23T12:27:07.386Z <HassController:null> HassController#hass: sending payload for x_hass_system.call_service on System#hass>system action: [Object]{ "type": "call_service", "service_data": { "recirculation_minutes": "5", "target": { "entity_id": "water_heater.bully_house_water_heater" } }, "domain": "rinnai", "service": "start_recirculation" } [stable-22168]2022-08-23T12:27:07.391Z <HassController:ERR> HassController#hass request 1661257627388<2022-08-23, 8:27:07 a.m.> (call_service) failed: [Object]{ "id": 1661257627388, "type": "result", "success": false, "error": { "code": "invalid_format", "message": "value must be one of [5, 15, 30, 45, 60, 75, 90, 105, 120, 135, 150, 165, 180, 195, 210, 225, 240, 255, 270, 285, 300] for dictionary value @ data['recirculation_minutes']" } } -
@pabla Closer! Passes the parser and now a new error... I will play with this a bit later after meetings...
[stable-22168]2022-08-23T12:27:07.386Z <HassController:null> HassController#hass: sending payload for x_hass_system.call_service on System#hass>system action: [Object]{ "type": "call_service", "service_data": { "recirculation_minutes": "5", "target": { "entity_id": "water_heater.bully_house_water_heater" } }, "domain": "rinnai", "service": "start_recirculation" } [stable-22168]2022-08-23T12:27:07.391Z <HassController:ERR> HassController#hass request 1661257627388<2022-08-23, 8:27:07 a.m.> (call_service) failed: [Object]{ "id": 1661257627388, "type": "result", "success": false, "error": { "code": "invalid_format", "message": "value must be one of [5, 15, 30, 45, 60, 75, 90, 105, 120, 135, 150, 165, 180, 195, 210, 225, 240, 255, 270, 285, 300] for dictionary value @ data['recirculation_minutes']" } } -
@Pabla - Thanks again for your help. This was finally the answer (for anyone searching later)....
{ "recirculation_minutes" : 5, "entity_id": "water_heater.bully_house_water_heater" } -
T toggledbits locked this topic on
