Multi-System Reactor

691 Topics 6.8k Posts
  • [solved] Ordering of global expressions

    Locked
    22
    0 Votes
    22 Posts
    495 Views

    @toggledbits can confirm that the fix is working (tested with 21297)

  • Reactor not starting on latest 21294

    Locked
    8
    0 Votes
    8 Posts
    209 Views

    just confirming 21297 working with original app.sh

  • Jungle telegraph - MQTT coming to MSR?

    Locked
    4
    0 Votes
    4 Posts
    139 Views

    Return of Lobo...?

  • Sorting arrays

    Locked
    8
    0 Votes
    8 Posts
    169 Views

    @toggledbits PERFECT!!!

    Well, now it's time to review everything I had before and put it in order 😁

    And best of all, remember that I did 3 steps:

    List of all devices; Applying the rule, like battery level; Generate a string to send by message putting the device name.

    Now, with the sort get the name, I can eliminate the third variable, and using format() generate the message directly, SHOW!!

    The game is getting fun.

    It's going to be a long night 🙂

  • 0 Votes
    2 Posts
    97 Views

    @talisker Backing up your configuration and storage are simply a matter of copying the entire directory in which the config, logs and storage (and possibly others) are kept. If you look at the container's volume configuration, this would be the directory mapped to /var/reactor within the container. Any method of copying will do, including GUI copy to another folder.

    Since I don't have a QNAP NAS, I can't advise on how to update the container. Perhaps a QNAP user can chime in on this with some definitive steps. This previous post covered one approach to the process. I don't know if that's the only way, or the best if there are more ways than this one. Please carry on any QNAP-specific upgrade discussion in that (linked) thread.

  • 0 Votes
    21 Posts
    1k Views

    It was noted in another thread covering a specific case of this topic that it's possible, on some hubs (ahem), for a device to flap its *failed" state quickly, and perhaps is even likely due to temporary network/mesh/device issues, or a simple choice that during restart of the hub devices are marked down until known up. All of this may cause quick, although likely uninteresting, transitions between failed and not-failed.

    It may therefore be advisable to use the "sustained for" option on any rule that reacts to a change in identified failed devices, to dampen the response to such potentially spurious state changes.

  • Added IP camera to Ezlo, what is causing this

    Locked
    5
    0 Votes
    5 Posts
    124 Views

    @toggledbits Sustained for is the way to go here, thank you for your advice.

    I can say that for Zigbee devices their firmware is a mess, a reboot of the controller marks all devices unreachable until they are physically toggled or reporting new sensor values, so rebooting means going around the house like a fool toggling lights and blowing on temp/humidity sensors, and if you don't do it fast enough you have to reboot again to give the devices a new chance to phone home in time. 🙂

  • Hubitat primary attribute

    Locked
    3
    0 Votes
    3 Posts
    122 Views

    @toggledbits Confirming Build 21292 fixed the issue. Thank You

  • [Solved] Date and time issue

    Locked
    5
    0 Votes
    5 Posts
    178 Views

    Hi,

    Install the new version and it is now working as expected.

    Thanks for looking into it.

  • Fun Stuff

    Locked
    7
    7 Votes
    7 Posts
    388 Views

    Too cool for school, sir! I've been in lurk mode lately due to life interrupting, but didn't want this genius move to go unnoticed.

    Next stop: Cause Ezlo firmware to be deleted from Ezlo boxes, leaving only the good stuff. Watching old Forum tells me they are still moving in many odd directions half a step at a time. Yawn. Should my Vera die, I will almost certainly jump to Hubitat + Reactor.

  • Reactor log timestamps

    Locked
    8
    0 Votes
    8 Posts
    221 Views
  • Sending a service request to Home Assistant

    Locked
    2
    0 Votes
    2 Posts
    149 Views

    One of the big gaps in the Home Assistant API is that it doesn't expose what services are available on every entity. I don't think it actually knows. But, you can tell MSR that an entity uses a particular service. You should have a file called local_hass_devices.yaml in your config subdirectory. If not, it's no trouble to just add it. There's also a default version in dist-config you can copy. To that file, in the entities section, just add entry for the entity using its canonical ID, and the services you want to add to it. Here's a sample file to give you the general idea:

    # This file has local definitions/overrides for HomeAssistant devices. --- entities: # Entry shows how an entity can have a service added and its name forced "hass>sensor_connected_clients": name: "WebSocket Clients" services: - homeassistant # This media player is a Sonos device, so it supports TTS "hass>media_player_portable": services: - tts # This media player is a Sonos device, so it supports TTS "hass>media_player_media_room": services: - tts # "hass>switch_power_switch": services: - zwave_js

    Or, to do it the simplest way possible, there's a call_service action on the system entity for the HassController instance.

    5336b43c-b13d-4561-b33f-1cd2e1b61838-image.png

  • Logic loop? Throttling...

    Locked
    11
    0 Votes
    11 Posts
    315 Views

    @toggledbits your suggestion worked perfectly!!

    With the version updated to 21286, moving all rules to the Global variable, the warnings ended, and I can see in the log that the action started to be invoked only at the given times, and the variable update as Global occurs only when there is an effective change in the device.

    Great knowledge exercise and one more lesson from you.

    Thanks @toggledbits !

  • The syntax of locale

    Locked
    4
    0 Votes
    4 Posts
    98 Views

    It decides what locale to use when you go to http://reactor-ip:8111/reactor with no language code after... it redirects at that point. If you're already on http://reactor-ip/reactor/en-US/ (with language code) and refreshing, you're going to keep getting en-US.

    Ideally, you should not use the override config. The documentation is pretty clear on this. The correct way is to configure both your browser and the host system for your correct locale.

  • Flapping device

    Locked
    8
    0 Votes
    8 Posts
    242 Views

    @toggledbits Coming back to this, eventually I was able to change the configuration (below), but still, whenever the washing machine is running, I keep getting the same alerts.

    Screenshot 2021-10-14 at 16.00.53.png

    These two rules that are mentioned in the alerts do not even trigger at the time of alerts, because not all conditions are true (see previous posts, where washing machine power switch state should be false for the rule to be triggered).

  • Trouble connecting Vera to MSR

    Locked
    17
    0 Votes
    17 Posts
    470 Views

    I just let it run with the 14.17

  • Localization

    Locked
    11
    4 Votes
    11 Posts
    322 Views

    OK. I'm updating the docs with all of this. Keep the discoveries and suggestions coming!

  • Array manipulation

    Locked
    2
    0 Votes
    2 Posts
    102 Views

    Just filter it out in the loop:

    each id in dynamic_array: "vera>device_235" == id ? null : ( getEntity( id ).attributes.x_vera_device.failed ? id : null )
  • How to monitor sensors that stop working?

    Locked
    31
    0 Votes
    31 Posts
    558 Views

    @toggledbits as always a master explanation, a class!

    You are absolutely right, the devices sleep, only communicate if they have an action or is time to communicate with the hub to update the status.

    So there is no sense Poll or Refresh commands that will not work, perfect!!

    In this case my devices are configured to communicate with the hub every 12 hours, I will decrease to 6 and have a more constant report.

    Well, exercise of the day closed, thanks again.

    The routine that I exposed at the beginning of testing CommFailure, I'll just change it to x_vera_device.failed that is more elegant 🙂

  • EzloController error

    Locked
    20
    0 Votes
    20 Posts
    484 Views

    Now it's working again after I powered off/on ezlo controller and restarted Reactor. The log is too long, no privileges to upload it. It's not the first time it happens upgrating the container.
    ezloplus Firmware: 2.0.19.1714.2
    Thanks anyway.

    [latest-21281]2021-10-08T21:55:33.176Z <Controller:INFO> EzloController#ezlo hub inventory complete/successful; 837ms [latest-21281]2021-10-08T21:55:33.179Z <Controller:NOTICE> Controller EzloController#ezlo is now online.

Recent Topics