I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.
Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.
( *Drag & drop of rule conditions have never worked on a mobile)
Hi @toggledbits,
I have lots of logs with this:
<Engine:ERR> Assignment to alarm ignored -- expression-driven global cannot be set by assignmentAny hints to where look at to avoid this? Thanks.
Hi @toggledbits
I'd like to update my controllers with these new features, but I'm struggling to find any guidance in the docs - and in general to understand the context.
Could you please elaborate more? Thanks.
I have the following ACL defined:
groups: admin: users: - admin applications: true api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: trueAnd I have authenticated to MSR as "admin" user. However, I'm getting "access denied" when trying to access http://*******:8111/api/v1/log
So what I'm missing, is my ACL incorrectly defined?
Using build 24302 on Docker.
Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.
Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce
A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.
Hi!
In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
Thanks!
/Fanan
Hi
I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.
They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.
This is how that device looks in the Ezlo API.
Devices Info:
_id: "10696001" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "level_sensor" subcategory: "" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Digital" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696001" deviceId: "10696001" hasGetter: true hasSetter: false name: "smoke_density" show: true valueType: "substance_amount" scale: "parts_per_million" value: 2.7472610473632812 valueFormatted: "2.75" status: "idle"There is also an Analog Gas sensor that one did import in to MSR OK.
68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png
Devices Info:
_id: "10696000" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "security_sensor" subcategory: "gas" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Analog" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696000" deviceId: "10696000" hasGetter: true hasSetter: false name: "gas_alarm" show: true valueType: "token" enum: 0: "no_gas" 1: "combustible_gas_detected" 2: "toxic_gas_detected" 3: "unknown" valueFormatted: "no_gas" value: "no_gas" status: "idle"And this is how this MQ2 Gas Sensor looks like on their dashboard:
Digital
cb77dfa3-4af5-4d06-9635-89207a716a89-image.png
Analog
4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png
They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!
And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.
THANKS.
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.A couple of things for you @toggledbits, since you mentioned that this release has new features and some tweaks are expected.
Local expressions cannot be deleted. Pushing the X button has no effect for me.
When cloning an entity action, the result is strange (first is cloned one, second is the original action):
a92ea094-9e2c-4aaa-bf47-2d07a6ffdbd0-image.png
When changing the action on the cloned element, the params are added to the original one. See screenshot:
92ac3011-83c8-466b-bd23-47d483ad7a52-image.png
Dark theme has a couple of strange contrasts. One is visible in the previous screenshots (white text on yellow background). Another one is in groups (blue text on blue background):
9b3c4988-53ef-44e6-9672-30e744cacb75-image.png
Overall, I found blue, yellow, red and green (in buttons and forms) to be too bright.
On the bright side:
I love the new script action: thank you! The dark theme is a great start to avoid getting blinded at night I promise I'll try very soon the new features around actions. Thanks!@toggledbits
I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:
I followed the new directions about npm
npm i --no-save --no-package-lock --omit dev
Any idea what the issue is?
Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)
Things I have tried:
Hard refresh
Different browser
Different computer
Restarting Reactor
Failed troubleshooting attempts:
No errors in Chrome console
No relevant errors in Reactor log (can still PM the full log file)
Reactor version: latest-24293-ea42a81d
Hardware: Odroid N2+
Linux version: Ubuntu 24.04.1 LTS
3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled
ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled
Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.
What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?
Running:
Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]HAAS:
RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0Hi!
Is it possible to generate two additional log files, the first being the replica of what is displayed on screen by the Rule History widgets and the other with Recently Changed Entities?
And could I configure the generation of one file per day, and delete the older ones? For example, store the last 5 days?
And being more ambitious, does Windget have an icon to open these TXT files in the navigated?
Well, we're approaching Christmas, so here's my request to Santa Claus @toggledbits 🙂
Hi @toggledbits
I'm working on a controller to generate llm response from a prompt in reactor. I have http response coming thru an http request action at the moment, capturing the response inside a local variable. So, it's practically sync.
I want to create a controller, so I don't have to rely on a proxy (and have a simpler architecture), and duplicate absurd http actions, but AFAIK in the current implementation, actions are async only. But if I have multiple requests going on, I cannot be sure what it's really inside an attribute. I also thought that something like a correlation id when sending the request could be used to identity multiple responses, but I wanted to double check with you before starting with something too complicated. I also noticed that some actions in home assistant (ie forecast) are sync and I'm wondering if you have any plan or hint to address this situation. Thanks.
Thanks.
@togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.
Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.
Thanks in advance.
Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3
@toggledbits I have noticed after upgrading both Reactor and ZWaveJSController to version 24257 that two of my devices/entities, TILT-ZWAVE2.5-ECO and Zooz ZSE18, had their entity re-named in an unusual way and also appears to be duplicated.
Reactor version 24257
ZWaveJSController version 24257
Z-Wave JS UI version 9.18.1
zwave-js version 13.2.0
Vestibule Motion Sensor State attributes/partial screenshot of entities it created. All entities have the same attributes.
motion_sensor.state=true x_zwave_values.Notification_Home_Security_Motion_sensor_status=8 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=23 zwave_device.valueId=[113,"Notification","Home Security","Home Security","Motion sensor status","Motion sensor status"] zwave_device.version_info=nullTilt Sensor Door State and Tilt Sensor Door State Simple attributes/partial screenshot of entities it created. All entities have similar attributes with exception of x_zwave_values.Notification_Access_Control_Door_State = 22 or 23.
tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state_simple=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state_simple=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=nullI'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests 🙂
Reactor (Multi-System/Multi-Hub) Announcements
-
Build 21277
- HubitatController: Fix a problem with setting RGB color.
- Fix an issue causing "Object not found" exceptions when evaluating a
getEntity()
call in a subcontext of a rule-based expression (e.g. within aneach
loop). - Fix a number of issues required for localization (thank you, @Crille ).
-
-
Build 21281
- In prior versions, a reference to a variable (rule or global) that does not exist would cause an alert and "fail soft" by returning null. This (old) behavior actually hides such errors and makes them more difficult to locate, and generally speaking, you shouldn't be referring to things that don't exist. The new behavior is to throw an exception during the evaluation, which will more clearly highlight the error and make it easier to find and correct. If for some reason you still need the old behavior, you can set
deprecated_undefined_global_soft_fail
to true in theengine
section ofreactor.yaml
, and such errors will soft-fail as before. The old behavior is deprecated, however, and will be removed in a few months. - PR 0000260: Fix failure of HTTP Request (really underlying variable handling) to notice change in array of objects returned by request.
- PR 0000259: Need to more clearly highlight variables with errors in the expression editor. Failing expressions now receive orange highlight bars.
- Add
typeof()
expression function. - Additional localization changes.
- New HTTP API additions: add alert, dismiss alert
- Bless Home Assistant to 2021.10.0
- In prior versions, a reference to a variable (rule or global) that does not exist would cause an alert and "fail soft" by returning null. This (old) behavior actually hides such errors and makes them more difficult to locate, and generally speaking, you shouldn't be referring to things that don't exist. The new behavior is to throw an exception during the evaluation, which will more clearly highlight the error and make it easier to find and correct. If for some reason you still need the old behavior, you can set
-
Build 21286
- InfluxFeed now supports InfluxDB version 1.8+ and 2.0. InfluxDB versions prior to 1.8 are no longer supported. Please see the documentation for configuration details, as the configuration requirements for 1.x and 2.0 are different. Users of InfluxFeed also need to
npm update --nosave
if they are bare-metal installed. - The behavior of rules when throttled has been improved. Note, however, that any time a rule is throttled, events could be missed (e.g. if a light that is a dependency of a rule is turned on and back off quickly when throttled, the rule may not "see" the on event).
- Ongoing documentation updates.
- Bless Hass to 2021.10.4
- First version to contain a foreign language translation, Swedish! Thank you @Crille for your work on the translation and helping me get localization working.
- Address possible evaluation loop while using SetVariable in a rule reaction on a rule variable, where the value is an expression that contains a
getEntity()
reference. - Documentation updates
- Further i18n fixes (thank you @Crille)
- InfluxFeed now supports InfluxDB version 1.8+ and 2.0. InfluxDB versions prior to 1.8 are no longer supported. Please see the documentation for configuration details, as the configuration requirements for 1.x and 2.0 are different. Users of InfluxFeed also need to
-
Build 21292
- PR 0000262: Fix an error in handling date/time conditions with M/D across new year boundary.
- PR 0000261: HubitatController: Resolve an order of operations issue preventing extended attributes from being assigned as primary in local config.
- PR 0000258: (i18n) Fix string reference for condition option
- HassController: treat controller reporting NOT_RUNNING as an error and disconnect/retry
- Bless Hass to 2021.10.6
-
Build 21294
- PR 000263: Fix spurious log messages after deleting a global expression that contained a
getEntity()
. - Fixed a UI issue with an expression being sorted to the top of the list then ending up at the bottom.
- The expression function
strftime()
is now locale-aware. - Docker containers are now running on nodejs version 16.
- PR 000263: Fix spurious log messages after deleting a global expression that contained a
-
Build 21297
- PR 0000264: Fix an error in the rule editor on a particular value test used in several places that could cause the entered value of a condition option to not be saved (most notable on the "repeats within" field, but also found in two other locations).
- Update to lexpjs 21296 to get
sort()
function for arrays, and user-definable functions from expressions. Default sort in Reactor Engine for the implemention of expressionsort()
function is (host) locale-aware. Please refer to the documentation for details.
-
Build 21306
Note: this release includes changes to package dependencies. Bare-metal users please run
npm update --no-save
to resolve.- HTTP Request action now has explicit control over HTTP auth, with type selection (none, Basic, Digest) and credential fields (username and password).
- PR 0000265: Correct a string that is not translated in the alerts status panel.
- i18n: Found an additional string that was not localizable.
- The HTTP Request action will now suppress all alerts for any error it encounters, not just HTTP errors, if the "no error alerts" option is checked.
- Update lexpjs to get new array set functions:
arrayIntersection()
,arrayUnion()
,arrayDifference()
,arrayExclusive()
andarrayConcat()
.
-
Build 21307
- PR 0000266: An issue introduced at 21306 saves certain substitutions with the wrong data type.
- HubitatController: Resolve (hopefully) a race condition at startup.
-
Build 21313
- Bless Home Assistant to version 2021.11.2
- New system capability
button
to express state of a single button or contact closure. - PR 0000268: Sun condition shows "not between" as "between" in rule detail card.
- Add
/alert/:tag
HTTP API endpoint (DELETE method); this deprecates/alert/:tag/dismiss
.
-
Build 21321
- HassController: Additional updates for event handling (
init
support). - HubitatController: Map additional capabilities.
- Internal support additionals for MQTTController
MQTTController - Build 21321
- Fix incorrect scope reference is tasmota_generic_relay payload.
- Additional helpful debug.
Upgrading MQTTController, which is a standalone/add-on component, is the same procedure as initial installation.
- HassController: Additional updates for event handling (
-
Build 21331
Please note that Hubitat has released version 2.30 of its firmware, but it has not yet been tested with HubitatController and is not yet supported.
- DynamicGroupController: new controller to build dynamic groups. Refer to the docs for configuration information.
- Logger: new
recycle
flag, when true, each startup rotates the log file so the new run starts in a fresh file (makes some debugging easier); the file mode of the logs created can now be set by setting themode
key. - Bump recommended nodejs version to 16.13.0; versions 14 and 15 will continue to be supported through March 31, 2022; docker containers are built with recommended versions, and require no user action, but bare-metal users should check their node version (
node -v
) and if necessary make a plan to upgrade before 3/31. - Update to lexpjs 31330; adds built-in
median( array )
function; provides extendedfirst...in
syntax with (new) optional result expression; refer to docs. - PR 0000270: [HubitatController] Apparently Hubitat needs action pacing like VeraController (that is, it can be overwhelmed if too many actions are sent at once). Pacing is now enabled with a default of 25ms delay between actions.
- PR 0000269: [UI] Rename Reaction dialog for global reactions prepopulates name from start of editor session rather than most recent name given if rename is used several times within one session.
- Bless Home Assistant to version 2021.11.5
MQTTController - Build 21331
- More carefully guard sensors (in templates) from payloads that don't contain the sensor data (i.e. avoid setting null value if an update is published with data missing).
- Additional templates for Tasmota and Shelly.
- Documentation updates and clarifications.
-
Build 21332
- DynamicGroupController: Fix missing initialization in preload for some selectors (blocking bug, no PR in Mantis).
- Documentation build fix so all documents receive correct left navigation.
- Condition operator is [not] EMPTY has been added to ease checking of group member arrays and other values for emptiness; see the docs Entity Attribute conditions for details on what "empty" means in this context.
-
Build 21336
If you have been with Reactor since before 21075 (March 15, 2021), your
logging.yaml
configuration may have a relative path in thename
keys of the default streams (e.g../logs/reactor.log
). These must be changed to just a simple filename (e.g.reactor.log
). Reactor has been warning you at startup (in the log file) about this since 21075, if it applies to you (i.e. your logging config uses a relative path), but if you haven't seen it, you may not have changed it. The time to check it/change it is now, because the next version of Reactor that is released will not allow pathnames (relative or absolute) in this key, and will not run if it finds one.- DynamicGroupController: map actions in known capabilities of selected objects, so that groups can perform actions on their members. For example, performing the
power_switch.off
action on a group will do so on all of its members that support that action. - Logging: Fix support of log streams so that subsystems declaring their own log streams operate correctly; fix a number of long-standing annoyances in the configuration and handling (no changes to user configuration requirements except as noted above); improved "panic mode" (used when no configured stream is writable).
- Dashboard: improved layout for
string_sensor
capability objects. - HubitatController: Bless firmware 2.3.0.113
- HubitatController: extend recent additions to capabilities (
string_sensor
) to the mode and HSM entities. Reduce reliance on the custom/hub-specific extension capability. - HubitatController: New "type guessing", experimental, to try to reduce effort for this hub in particular in determining device types and primary attributes. This is a work in progress (but then, what isn't?).
- PR 0000271: Fix a missing localization in rule detail panel, operator in group titles (reported by @Crille).
- Improvements to
rpi-install.sh
script to handle upgrade of systemd script when upgrading nodejs. - A number of internal fixes related to linting of the code.
- As always, a number of documentation updates.
- DynamicGroupController: map actions in known capabilities of selected objects, so that groups can perform actions on their members. For example, performing the
-
Build 21337
- Document additional keys for logging in the
dist-config
template. There is also existing, but not well-organized, docs on the Logging page of the manual (which at the moment lives under Troubleshooting). - HubitatController: ensure
x_hubitat
andx_hubitat_extra_attribute
capabilites are declared and extended so their attributes can be assigned as primary. - PR 0000272: Localization issue in input fields for date/time condition.
- PR 0000273: Pulse after sustained for delay is shortened by the delay.
- Document additional keys for logging in the
-
Build 21338
This is a hotfix build for users of Hubitat only, and specifically for users of Hubitat Modes. If you do not use Hubitat Modes, or Hubitat at all, you do not need to upgrade to this version.
- HubitatController: Fix handling of mode query response (injection from additional changes in 21336).
-
Build 21342
- PR 0000275: Fix sun angle not updating in
reactor_system>sun
(Sun Information) entity. - PR 0000274: Fix missing localization of condition operand labels in rule editor.
- HassController: More tightly map reported service_data field types into Reactor types (to improve UI experience on Hass-native actions).
- Support "object" data type in action data more universally, not just in controllers that need it.
- PR 0000275: Fix sun angle not updating in
-
Build 21349
If you grabbed this release before 06:00 on 16-Dec-2021 UTC, please grab it again and reinstall. There was an issue with the next-day rollover computing sunset times that I fixed in-line.
- Make sure client API uses port for WebSocket connection, so the UI works when on a proxy or tunnel.
- Global reactions now support action groups with constraints.
- EzloController: Additional energy capabilities on certain devices/items.
- InfluxFeed: Fix an error in parsing the configuration for
select_capability
with attributes listed. - The
suninfo
capability (used by the Sun Information entityreactor_system>sun
) has been expanded to include theelevation
andazimuth
of the sun's current position. Theelevation
is given in degrees above the horizon. Theazimuth
is given in degrees clockwise from North (compass direction). - The
suninfo
attributesun_angle
is now deprecated and will be removed from a future release. If you are using it in conditions, please switch to usingelevation
, which is a better representation of the sun's position. - A bug in the computation of
day_length
(in hours) in the extreme latitudes (i.e. where the sun does not cross the horizon at certain times of year) is fixed. During periods during in which the sun never rises, day length will be 0; during periods in which the sun never sets, it will be 24. Similarly,period
could give incorrect results and will now report correctly or the conditions.
-
Build 21351
Users are advised only to upgrade to this release if they are affected by an issue related to the changes below; specifically, if you are not a user of Hubitat and you do not use constraints in rules or reactions, there is no need to upgrade to this release.
- HubitatController: Aggressive management of the event websocket connection, with additional diagnostic output by default.
- HubitatController: Fix error in setup of task queue (part of attempt to control pace of outgoing actions).
- Constraints: Loosen rules on condition options for constraints in rules (a stateful context), as opposed to those in global reactions (which are stateless).
- Docs: Improve description of the
time()
function so that it's clear it can convert time strings (in ISO 8601 format).
-
Build 21356
- PR 0000278: Fix an untranslated string in rule reaction name generator.
- SystemController: publish alert data on entity, making it available for use in conditions.
- EzloController: Fix bug where cancelling a house mode change causes the mode name to get the ID rather than the name.
- EzloController: support for additional items (power-related and seismicity).
- EzloController: remove
power_switch
as automatic capability on dimmable lights; not all Ezlo dimmable lights publishswitch
items, so use the presence of theswitch
item on a device as the trigger to extendpower_switch
. - EzloController: Fix an error thrown when handling certain extension items (e.g.
electric_meter_kwh
, only on some devices). - HubitatController: Fix handling of TamperAlert capability.
- HubitatController: Add config
warn_unresponsive
(boolean) to turn off (when set false) warnings for quiet channel reconnects. - HubitatController: Support for extension capabilities where an attribute like
current
is provided without a matching capability. - VeraController: Log slow responses from hub (helps troubleshooting bottlenecks).
- Engine: Fix error in restore of running tasks across a reboot.
- PR 0000279: Fix an error that leaves Variable Value conditions in global reaction constraints with no variable list from which to choose (should list global variables).
HubitatController - Additional Notes
The connection health probes have some new settings, described in the docs, to make the health checks as reliable as possible and eliminate false positives in the quiet channel checks. Primary among these is recognition of a device under control of the Hub Information (community) driver. I recommend that Hubitat users install this driver (and create a device that uses the driver, and publish that device through Maker API), as it has some predictable behaviors that make it perfect for health checks, and it gives you access to other information about the hub you may find useful in Reactor. This is not required; just recommended.
-
Build 21360
- PR 0000282: DynamicGroupController: fix an error that could cause preloading of entities to fail (started in 21356).
- Updated lexpjs to 21360 to correctly handle assignment to object/array members.