Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
H

HansW

@HansW
DynamicGroupController and attributes
therealdbT
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!
Multi-System Reactor
Bail out of failed reaction?
T
Topic thumbnail image
Multi-System Reactor
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
[Solved] DynamicGroupController updating members issue
CrilleC
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.
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
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.
Multi-System Reactor
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
[SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor
[SOLVED] Question regarding "in" vs "contains" vs contents of the string
G
Topic thumbnail image
Multi-System Reactor
openLuup console disappeared - 500 - Internal Server Error
A
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?
Plugins
Logon screen timeout
G
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen. Brave browser Brave 1.92.139 (Official Build) (arm64) Chromium: 150.0.7871.114
Multi-System Reactor
[MSR] Copy&past of actions and/or drag&drop between set/reset
therealdbT
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!
Multi-System Reactor
Upgrade advice - upgrade from aarch64 to ARM64 image
T
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
Multi-System Reactor
Alexa for MSR, any interest?
MikeReadingtonM
Topic thumbnail image
Multi-System Reactor
Ezlo Paid Subscription for Vera Cloud Services
toggledbitsT
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.
General Discussion
[RESOLVED] Telegram notification broke with latest update
3
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Phantom device, “INFO” appears
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Mode Status NULL
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] HTTP query failing after version 26177
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Question about the find function
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[Answered] OK to remove old json files?
3
Topic thumbnail image
Multi-System Reactor
About
Posts
21
Topics
4
Shares
0
Groups
0
Followers
0
Following
1

Posts

Recent Best Controversial

  • Move Reactor from Docker to Home assistant plugin
    H HansW

    @toggledbits I installed the reactor plugin on the advice in the manual,

    Could you please give me an advice here?

    Warm regards,

    Hans

    Multi-System Reactor

  • Move Reactor from Docker to Home assistant plugin
    H HansW

    I just installed the Reactor plugin for home assistant and tried to move my configuration by copying the reactor-data files to the same location in the home assistant files. Unfortunately this does not work.

    I tried rebooting, restarting but the reactor in home assistant stays clean. I tried adding some rules, they do stick but I soo no difference in the reactor-files.

    I guess I am missing something very obvious???

    No idea what however.... So I would appreciate some pointers.

    Warm regards

    Hans

    Multi-System Reactor

  • MSR UI not working on iPhone
    H HansW

    Aha, problem solved! Hitting the menu icon in the right top corner toggles the screen.

    Multi-System Reactor

  • MSR UI not working on iPhone
    H HansW

    Hey guys,

    is there a bug in the UI of MSR (and also in the history pane of HASS btw) or do I have an issue with my iPhone? Or am I the only iPhone 12 min user which seems unlikely.

    I cannot use MSR on my iPhone, the right pane does not show up on the screen, just the left pane. This is the same on chrome and safari, also when I hold the phone horizontally.

    I can simulate this on the MacBook when I crop the safari window.

    Multi-System Reactor

  • Device information in string or array
    H HansW

    Thanks a lot for your elaborate answer and explanation @toggledbits! I do appreciate this and it helps me further, also with other issues, to make better use of your wonderful tool! I was not aware of this ${{ }} construction and I have no idea from which language this syntax is but I guess it forces the bit in between to be evaluated.

    Anyway, it solved the problem! Thanks a lot!!

    Multi-System Reactor

  • Device information in string or array
    H HansW

    Thanks @toggledbits , the variables I showed you in my earlier post and I corrected them zo they evaluate properly now into a string DeviceTrackerMessage which holds the friendly name of the devices offline, separated with comma's. As a string it does not have "" around it.

    My rule has a lot of Entity Attribute checks of all devices checked on x_hass.state <> home and combined into an OR.

    Then as a constraint I check the Variable Value DeviceTrackerMessage <> ""

    And then the Set Reaction holds:

    Entity Action hass>system x_hass_system.call_service with service: notify.my_device and the data: holding
    { "title": "Some devices failed: ", "message": XXXXX }

    Where on the position of XXXX I tried all I could think of.

    I know the rule might not be perfect yet but just testing the Set Reaction should generate a message. When replacing the XXXX with "test" I get a message.

    Also I tried adding a variable called JSONString and populating that using to JSON but I cannot get the result to look like a JSON string nor to work.

    Hope this helps.....

    Multi-System Reactor

  • Device information in string or array
    H HansW

    Thanks again for your help @toggledbits. I had been looking at the wrong place (in HASS) for the entities but your pointer was a great help also for other uses of reactor. The expressions are working like a charm now.

    Still having trouble getting the JSON correct using the Variable though. I am using the x_hass_system.call_service and whatever I try it fails.

    The string looks like:
    { "title": "The following devices fail: ", "message": XXXX } Where at the location of the XXXX I probably need a trick to insert the DeviceTrackerMessage with surrounding double quotes but I don't have a clue.

    I even tried building the JSON into a global variable but it looks like the escape characters do not work or maybe I overlook something obvious.

    Multi-System Reactor

  • Device information in string or array
    H HansW

    Well, I have been trying to use the above example to get a message reporting LAN connectivity failure of devices in my network.

    So I have set up an array with devices the Global expressions named DeviceTrackerList:

    ['hass>device_tracker_airport_time_capsule_van_hw','hass>device_tracker_airport_time_capsule_van_hw','hass>device_tracker_akita','hass>device_tracker_altherma_lan_adapter','hass>device_tracker_ap_bijkeuken' etc] 
    

    Then I run into problems defining the loop into a variable DeviceTrackerNotHome:

    each id in DeviceTrackerList:getEntity( id).state == not_home ? id: null
    

    Which returns the entire list. I have tried a few dozen of other options but either the entire list or an empty list is returned. Obviously my .state does not do the trick but what is the correct syntax to use here? (And where could I have found that myself?...)

    Then the next step is to use the names of the failing devices in a message.

    My last global variable is named DeviceTrackerMessage and holds

    join(each id in DeviceTrackerNotHome:getEntity(id).name, ', ')
    

    which returns a nice list of friendly names but I have no idea how to use that in my message.

    I expected { "message": {DeviceTrackerMessage} } to work but it did not and all other attempts to construct something failed as well.

    So I do hope someone can help here to point out to me what is probably obvious but difficult for a novice user to see. 🙂

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    @toggledbits said in Sending HASS notifications from MSR:

    and sys_system from the capabilities

    Thanks, that did it!

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    @toggledbits Well, I have 21257 running now but still no hass>system entity... Only hass>controller. Should I enable something somewhere?

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    @toggledbits said in Sending HASS notifications from MSR:

    It should be 21257

    Thanks. It turns out that to upgrade a container on a QNAP you need to delete the old container first, than delete the image (which is locally stored as well) through the image menu and after that you can create a new image which will than all the real latest from the docker hub. Just specifying to get it from docker hub like I did the first time did not work, it used the locally stored image anyway.

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    @toggledbits And as an addition question on this new feature, is there any way to get for instance the friendly name of the trigger into the parameter section? I have for instance 9 doors which I would like to combine into one rule where, if one of them opens or closes, I get a message which tells me which door was opened/closed. It is not a big deal of course, I could easily have 9 rules but still would be nice also for other situations reporting temperatures and such.

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    @toggledbits, I tried but the hass>system entity is not there. I do have a hass>controller entity but no action to choose from. I am running your container on a qnap though so maybe selecting the latest build had no effect since you didn't rebuild that version? Or I did not manage to update the image in the right way. What I did was stopping the image, creating a new one using the latest-genereric-amd64 build and than starting that new image. It reports: Reactor (Multi-hub) latest-21243-a5028fc

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    @toggledbits holy cow, you are fast! I am going to try this out!

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    Yes I mean HASS native push messages to my iPhone. I would ;ike to stay with MSR for my automation instead of diving into the complexity of HASS automation, templates and blueprints but the notify action of MSR is limited to alert, email, prowl, pushover, syslog, callmebot and telegram. I would like to use the native messages and its different interruption levels

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    Hello anyone,

    is there a simple trick to send native HASS notifications from MSR? I guess I could call a scene or something with some parameters but I have little experience so would need some clear pointers on this. Thanks in advance!

    Multi-System Reactor

  • Error importing backup from vera
    H HansW

    Thank, I will give it a spin and see where it leads me too!

    Multi-System Reactor

  • Error importing backup from vera
    H HansW

    I am trying to get rid of my Vera and moving to HA on Qnap.

    It has been quite a challenge up to now especial since I have a NX584 so needed to set up a separate Pi for that but I keep on it.

    My NX584 used to set the house modes and your reactor took care of the lights and the heating.

    The house modes were nice although I would have preferred something more fancy like:

    At home daylight
    At home dark
    At home alarm on
    Away alarm on

    Multi-System Reactor

  • Error importing backup from vera
    H HansW

    Aha, I should have been able to figure that out myself but I had no idea that option existed. Thanks anyway, I just imported the file and it worked!

    Thanks for your excellent work, your software is very intuitive as compared to others.

    Is there any advice or good practice for replacing the vera house modes?

    Multi-System Reactor

  • Error importing backup from vera
    H HansW

    Aha, thanks for your swift response! Any pointer to which file(s) to use? There are a few hundred of them and multiple with Reactor in the name..

    Multi-System Reactor
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved