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.
S

SweetGenius

@SweetGenius
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Wiring Samotech SM308-S into light fitting
F
Hi Smart Home Community. I have used a Sonos inline WiFi switch to make one of my light fittings smart, but it requires a hard reset for WiFi changes, plus it isn't zigbee compatible, which means I can't use the Hue app to control it with the rest of the lights. To that end I bought a Samotech SM308-S as it is recommended as the better than the Sonos equivalent. I am however not exactly sure how to wire it in. The manual is available here Can anyone help me by clarifying which ports I need to use, and whether I should be using the live or switched live line for live etc. I will be keeping using standard switches for a while, although hope to upgrade to tap dials once I have all the fittings upgraded. Thanks
Hardware
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
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
Z-Wave Future....
DesTD
https://forum.z-wave.me/viewtopic.php?f=3417&t=36140 That's not a good thing I think Time to switch again?
Z-Wave.me
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Disaster recovery and virtualisation
CatmanV2C
Following on from my last thread, some progress has been made over the weekend. With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system. Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic. Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work. Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic. Once that hurdle is sorted I'm torn between: Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.) Decisions, decisions. C
General Discussion
Remote access of Zwave stick from Z-wave server
CatmanV2C
Topic thumbnail image
Software
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
About
Posts
90
Topics
21
Shares
0
Groups
0
Followers
0
Following
1

Posts

Recent Best Controversial

  • [Solved] Runtime error when exiting global reaction that contains a group
    S SweetGenius

    Fixed in Reactor build 25067.
    Thank You!

    Multi-System Reactor

  • [Solved] Runtime error when exiting global reaction that contains a group
    S SweetGenius

    No hurry sir, Just reporting.

    Multi-System Reactor

  • [Solved] Runtime error when exiting global reaction that contains a group
    S SweetGenius

    I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved.

    The Runtime Error is different in the two browsers
    Safari v18.3

    @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44
    
    You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.
    

    Google Chrome 133.0.6943.142

    TypeError: self.editor.isModified is not a function
        at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34)
    
    You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.
    

    Steps to reproduce:
    Click the pencil to edit a global reaction with a group.
    Click the Exit button.
    Runtime error appears.
    or
    Click Create Reaction
    Click Add Action
    Select Group
    Add Condition such as Entity Attribute.
    Add an Action.
    Click Save
    Click Exit
    Runtime error appears.

    I don’t know how long the error has been there as I haven’t edited the global reaction in a long time.

    Reactor (Multi-hub) latest-25060-f32eaa46
    Docker
    Mac OS: 15.3.1
    Thanks

    Multi-System Reactor

  • Any interest in a Homebridge adapter for Reactor?
    S SweetGenius

    Yes, I would be interested.

    Multi-System Reactor

  • Have reactor shut off a light with no motion unless I turned it on manually
    S SweetGenius

    @sethlampman I use multiple rules and a global expression to hold the current state of the light that I set when different events happen. When motion triggers the light I set the global expression to “auto”. When the light comes on with no motion then it must of been turned on manually so that rule sets the expression to “man” I then have rules to to shut the light off for when motion happend and another rule for when it was turned on manually with different delays. When the light is off I set the global expression to idle. Does this give you any ideas for your situation?
    Screenshot 2023-12-05 at 7.07.05 PM.png Screenshot 2023-12-05 at 7.07.31 PM.png Screenshot 2023-12-05 at 7.07.58 PM.png Screenshot 2023-12-05 at 7.08.21 PM.png Screenshot 2023-12-05 at 7.10.59 PM.png

    Multi-System Reactor

  • Home Assistant push notification for Reactor version update possible?
    S SweetGenius

    @tamorgen If I understand what you are asking correctly, Look under the reactor_system for reactor_system.update_available=true and use that as a rule trigger to send a notification.

    Multi-System Reactor

  • [Solved] Hubitat Hub Information Driver v3 and probe device
    S SweetGenius

    Installation of Reactor build 23049 and configuring a virtual switch as a probe device appears to be working well.
    FYI, The "Manual" link in the Reactor UI doesn't have the updated docs that are linked to in the Release notes thread. Hubitat Controller, Other Configuration, probe_device section. I have tried a hard reset in safari and Firefox browsers but the documentation is not the updated instructions. Thank You.
    Synology Docker
    latest-23049

    Multi-System Reactor

  • [Solved] Hubitat Hub Information Driver v3 and probe device
    S SweetGenius

    With all due respect and I do mean that and without beating this to death, I am only seeing the attributes that update when MSR probes are the baseData attributes witch per the Hub information driver’s documentation are (attributes: firmwareVersionString, hardwareID, id, latitude, localIP, localSrvPortTCP, locationId, locationName, longitude, name, temperatureScale, timeZone, type, uptime, zigbeeChannel, zigbeeEui, zigbeeId, zigbeeStatus, zipCode). I can find these attributes updating in the logs every time. Some examples of attributes that are not updating are publicIP and hubUpdateVersion among others. I use those attributes in rules and they do not update. I can not find evidence of these being updated in the logs or driver unless you set the poll time for these to very fast interval as I tried to document in the previous post. I do believe the next scheduled poll time is accurate and the attributes associated with the polls will not update until that time. Probably the best thing to do is to revert to the v2 driver.

    Multi-System Reactor

  • [Solved] Hubitat Hub Information Driver v3 and probe device
    S SweetGenius

    It looks like when MSR probes the device, it then resets the next scheduled poll times to the time of the probe + whatever time you have set to poll in the device preferences. If you have small poll times then the polls might fire between MSR polls. Here is the filtered Hubitat log showing which polls run. lastPoll: baseData is when MSR does the probe. The first part of the log is with the poll:1 time is set at 9 minutes. If the time elapsed since a MSR probe > than 9 minutes then the poll:1 will run. It ran once at 06:45:15. I then changed the poll1 time from 9 mins to 3 mins at 8:00pm to test. You can see it ran more often but I don't know why the baseData slowed way down also.

    dev:4812023-02-13 08:39:50.352 PMinfolastPoll : baseData
    dev:4812023-02-13 08:37:48.478 PMinfolastPoll : poll1
    dev:4812023-02-13 08:34:48.349 PMinfolastPoll : poll1
    dev:4812023-02-13 08:31:48.207 PMinfolastPoll : poll1
    dev:4812023-02-13 08:28:48.062 PMinfolastPoll : poll1
    dev:4812023-02-13 08:25:48.076 PMinfolastPoll : baseData
    dev:4812023-02-13 08:23:46.117 PMinfolastPoll : poll1
    dev:4812023-02-13 08:20:45.974 PMinfolastPoll : poll1
    dev:4812023-02-13 08:17:45.811 PMinfolastPoll : poll1
    dev:4812023-02-13 08:14:45.676 PMinfolastPoll : poll1
    dev:4812023-02-13 08:11:45.509 PMinfolastPoll : poll1
    dev:4812023-02-13 08:08:45.408 PMinfolastPoll : poll1
    dev:4812023-02-13 08:05:45.460 PMinfolastPoll : baseData
    dev:4812023-02-13 08:03:43.698 PMinfolastPoll : poll1
    dev:4812023-02-13 08:00:43.644 PMinfolastPoll : baseData
    dev:4812023-02-13 07:56:18.977 PMinfolastPoll : baseData
    dev:4812023-02-13 07:54:17.207 PMinfolastPoll : baseData
    dev:4812023-02-13 07:50:52.589 PMinfolastPoll : baseData
    dev:4812023-02-13 07:44:17.322 PMinfolastPoll : baseData
    dev:4812023-02-13 07:39:17.057 PMinfolastPoll : baseData
    dev:4812023-02-13 07:36:18.474 PMinfolastPoll : baseData
    dev:4812023-02-13 07:34:16.720 PMinfolastPoll : baseData
    dev:4812023-02-13 07:26:27.444 PMinfolastPoll : baseData
    dev:4812023-02-13 07:24:16.188 PMinfolastPoll : baseData
    dev:4812023-02-13 07:21:27.225 PMinfolastPoll : baseData
    dev:4812023-02-13 07:14:58.542 PMinfolastPoll : baseData
    dev:4812023-02-13 07:09:15.465 PMinfolastPoll : baseData
    dev:4812023-02-13 07:04:15.275 PMinfolastPoll : baseData
    dev:4812023-02-13 07:01:16.758 PMinfolastPoll : baseData
    dev:4812023-02-13 06:59:14.981 PMinfolastPoll : baseData
    dev:4812023-02-13 06:54:14.847 PMinfolastPoll : baseData
    dev:4812023-02-13 06:45:15.886 PMinfolastPoll : poll1
    dev:4812023-02-13 06:36:15.792 PMinfolastPoll : baseData
    dev:4812023-02-13 06:34:14.031 PMinfolastPoll : baseData
    dev:4812023-02-13 06:29:52.364 PMinfolastPoll : baseData
    dev:4812023-02-13 06:26:15.479 PMinfolastPoll : baseData
    dev:4812023-02-13 06:24:13.706 PMinfolastPoll : baseData
    dev:4812023-02-13 06:19:41.211 PMinfolastPoll : poll1
    

    I am not looking for an immediate fix or change, Just trying to communicate to you what I am seeing.

    Would it be an option to write your own virtual device driver for Hubitat so you could probe that device and return the data you want for the health check?

    Multi-System Reactor

  • [Solved] Hubitat Hub Information Driver v3 and probe device
    S SweetGenius

    I am running the latest version of the driver: v3.0.14.
    It appears to me when MSR probes the device or if you press configure in the driver, all the new scheduled poll times increase causing them never to run. I have my poll times set as follows: poll1: 9 mins, poll2: 119 mins, poll3: 241 mins, poll4: 12 hours.
    Screen Shot 2023-02-12 at 2.31.24 PM.png Here is a screenshot showing the scheduled poll times to start:
    Screen Shot 2023-02-12 at 2.29.39 PM.png

    After MSR polls the scheduled poll times:
    Screen Shot 2023-02-12 at 2.40.38 PM.png

    Poll3 and poll2 are not running.
    Here is what I'm polling in the driver.
    Screen Shot 2023-02-12 at 3.13.54 PM.png

    I know this is not your driver but I'm encouraged if you are not seeing a problem. I must have something configured wrong. Would you mind checking your driver and see if your scheduled times increase also?

    Multi-System Reactor

  • [Solved] Hubitat Hub Information Driver v3 and probe device
    S SweetGenius

    I have upgraded my Hubitat Hub Information Driver to v3 and after the latest MSR update latest-23028 MSR is working ok. The problem is when MSR probes the device it appears to affect the polling in the new Hub Information Device and its data does not update the data fields in Hubitat. If I remove the Hub Information Device from Maker API so MSR can't see it, The Hub information driver updates the data as expected in Hubitat. I added the device back into Maker API the same problem returns in Hubitat. I have tried to have MSR probe a different device by adding a different probe device and probe action in the reactor.yaml per the documentation but it appears then it still uses the Hub Information Device as the probe device instead of the one specified in the reactor.yaml. See Logs below. Is this the intended behavior to always use the Hub Information Driver if found and not use the device in the reactor.yaml file? Any recommendations on how to get MSR and the v3 of the driver to work correctly or can you see what I am doing wrong?

    [latest-23028]2023-02-11T23:27:50.471Z <Controller:NOTICE> Controller HassController#hass is now online.
    [latest-23028]2023-02-11T23:27:50.471Z <Rule:INFO> Internet Check (rule-l44qss4f in Home) starting evaluation; because entity-changed System#reactor_system>system
    [latest-23028]2023-02-11T23:27:50.471Z <Rule:INFO> MSR Update Version Available (rule-labweim2 in Notify) starting evaluation; because entity-changed System#reactor_system>system
    [latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> Internet Check (rule-l44qss4f in Home) trigger evaluation result is false (previously false)
    [latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> Internet Check (rule-l44qss4f in Home) evaluated; trigger state unchanged (false); rule state remains RESET
    [latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> MSR Update Version Available (rule-labweim2 in Notify) trigger evaluation result is false (previously false)
    [latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> MSR Update Version Available (rule-labweim2 in Notify) evaluated; trigger state unchanged (false); rule state remains RESET
    [latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> Internet Check (rule-l44qss4f in Home) evaluation complete
    [latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> MSR Update Version Available (rule-labweim2 in Notify) evaluation complete
    [latest-23028]2023-02-11T23:27:50.673Z <HubitatController:INFO> HubitatController#hubitat Maker API responded with 91 devices
    [latest-23028]2023-02-11T23:27:50.766Z <HubitatController:INFO> HubitatController#hubitat found 'Hub Information Driver v3' device #"481"; using for probe/health checks.
    [latest-23028]2023-02-11T23:27:50.780Z <Controller:INFO> HubitatController#hubitat 0 dead entities older than 86400000s purged
    [latest-23028]2023-02-11T23:27:50.780Z <Rule:INFO> Roku Pause (rule-l3nlrzu9 in Home) starting evaluation; because entity-changed BinarySensor#hubitat>519
    [latest-23028]2023-02-11T23:27:50.780Z <Rule:INFO> Stairs Light Low Light (rule-kulslls9 in Living Room) starting evaluation; because entity-changed BinarySensor#hubitat>519
    [latest-23028]2023-02-11T23:27:50.780Z <Rule:INFO> Porch Motion Extended check (rule-l3kr45m8 in Porch) starting evaluation; because entity-changed BinarySensor#hubitat>519
    [latest-23028]2023-02-11T23:27:50.780Z <Rule:INFO> Porch Light Manual On (rule-kmtxw155 in Porch) starting evaluation; because entity-changed BinarySensor#hubitat>519
    

    Snippet from the reactor.yaml:

     # action_pace: 100
          # warn_unresponsive: true
          # probe_device: hubitat>132 (not needed if Hub Information app installed)
          probe_device: hubitat>2
          # probe_action: x_hubitat_Configuration.configure (not needed if Hub Information app installed)
          probe_action: x_hubitat_Configuration.configure
          # probe_action: x_hubitat_Refresh.refresh
    

    Synology Docker latest-23028
    Hubitat v2.3.4.139
    Hub Information Driver v3

    Multi-System Reactor

  • [Resolved] Determining if button is pushed
    S SweetGenius

    @3rdStng I do not have the same device but I had to overcome this with my minimotes. Have you tried to set the x_hubitat_pushableButton.push back to 0 after your intended reaction. I cannot post images either for some reason or I would post an image of my Rule.

    Multi-System Reactor

  • Quality of Life Request: Update Button
    S SweetGenius

    I personally do not think the update process on Synology docker is that bad. A few more clicks than an easy button but not horrible. All my other docker containers are updated the same way. I like the docker image though. I am not familiar with the other platforms so I can’t comment on those update processes.

    Multi-System Reactor

  • Extras Filename/versions do not match
    S SweetGenius

    In the download/extras folder, there appears to be new versions but after installing them the versions do not match file version.
    Installed MQTTController-22291 => Logs report version 22284
    Installed NUTTController-22291 => Logs report version 22283
    Installed ZwaveJSController-22291 => Logs report version 22283

    The CHANGELOG.MD file in the archives shows the log reported version not 22291.
    Is this intended ? Just wanted to make sure I have the latest versions.
    Thanks

    Synology Docker latest-22293

    Multi-System Reactor

  • Deleting widgets
    S SweetGenius

    @tunnus Drag the widget off to the left side and it will disappear.

    Multi-System Reactor

  • Feature Request: Widget for Condition sustained time
    S SweetGenius

    I would like to ask if this is possible and if others would find this useful.
    I have multiple rules that check if lights are turned on manually and then have “Condition must be sustained for” xxxx amount of seconds then use the set reaction to turn off the light if it has not been shutoff. I like the UI when the rule is expanded that shows sustained time. (See Screenshot Below) Could a “Widget” have this information on the status screen that would show which rules conditions are waiting to come true with the sustained time? Similar to the Running Reactions widget.
    Screen Shot 2022-10-04 at 7.44.09 PM.png Thanks
    latest-22274
    Synology Docker

    Multi-System Reactor

  • Mosquitto and Owntracks
    S SweetGenius

    @catmanv2 said in Mosquitto and Owntracks:

    Does the indenting really matter?

    Yes, indenting matters, like @therealdb said previously.
    Is port 8883 the correct port for your setup?

    Software

  • Mosquitto and Owntracks
    S SweetGenius

    @catmanv2 I am no expert but try this:
    Change user: to username: Also, I believe both username: and password: should be the same indenting as source.

    Software
  • Login

  • Don't have an account? Register

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