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.0
Hi!
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:
GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor
GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor
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 🙂
Can I use Dynamic Group Control for Triggers and Reactions?
-
@tamorgen So iBlinds are a funny beast. I'm running 11 of the v3's and my automations run the gamut from normal open/close to "tilt when the sun hits this side of the house", "tilt when I'm not home (for privacy)" - smashing the sun tilt together with the Away tilt... oh boy is that fun.
I use a Zooz ZWave stick connected to Home Assistant to run them. They're happy together but I also do run a ping rule hourly lest they lose sight of the stick. Hubitat runs the rest of the house for now.
To control them... oy. Here's a couple samples:
The
.refreshkeeps Home Assistant happy in keeping the two status' you have in your first screenshot in sync.I have fought long and hard over the past two years with many, many hours of trial and error with these and, even this morning, am still making adjustments. I am quite demanding of my automations with them, in all fairness to both the blinds themselves and MSR.
ProTip: if you're controlling multiple iBlinds in one automation, a five or so second delay between each blind's actions will help a LOT. I believe I actually got that advice from iBlinds Support (when they answer).
Yes - you will have a LOT of iBlinds rules and reactions to truly control these bad boys. No - you will never get them all to open/close simultaneously. I've settled on a nice routine where they start their actions at the front of the house and end at the back, each performing it's task sequentially after the other. Not quite as cool but it's still ok.
OH - I also do a weekly recalibration to keep the iBlinds "accurate" lest they drift a bit over time.
To your actual ask - I've installed the Dynamic Group Controller but not delved into it as yet. Hopefully the info above helps you as the iBlinds rabbithole can run deep and dark. MSR has been key in my ability to get the iBlinds to function the best of any integration I've tried.
-
Note that @gwp1 is using ZWaveJSController to interface with iBlinds, not HassController. So this is more direct control that circumvents HA's interpretation.
-
@gwp1 said in Can I use Dynamic Group Control for Triggers and Reactions?:
@tamorgen So iBlinds are a funny beast. I'm running 11 of the v3's and my automations run the gamut from normal open/close to "tilt when the sun hits this side of the house", "tilt when I'm not home (for privacy)" - smashing the sun tilt together with the Away tilt... oh boy is that fun.
I use a Zooz ZWave stick connected to Home Assistant to run them. They're happy together but I also do run a ping rule hourly lest they lose sight of the stick. Hubitat runs the rest of the house for now.
To control them... oy. Here's a couple samples:
The
.refreshkeeps Home Assistant happy in keeping the two status' you have in your first screenshot in sync.I have fought long and hard over the past two years with many, many hours of trial and error with these and, even this morning, am still making adjustments. I am quite demanding of my automations with them, in all fairness to both the blinds themselves and MSR.
ProTip: if you're controlling multiple iBlinds in one automation, a five or so second delay between each blind's actions will help a LOT. I believe I actually got that advice from iBlinds Support (when they answer).
Yes - you will have a LOT of iBlinds rules and reactions to truly control these bad boys. No - you will never get them all to open/close simultaneously. I've settled on a nice routine where they start their actions at the front of the house and end at the back, each performing it's task sequentially after the other. Not quite as cool but it's still ok.
OH - I also do a weekly recalibration to keep the iBlinds "accurate" lest they drift a bit over time.
To your actual ask - I've installed the Dynamic Group Controller but not delved into it as yet. Hopefully the info above helps you as the iBlinds rabbithole can run deep and dark. MSR has been key in my ability to get the iBlinds to function the best of any integration I've tried.
I've been running 14 iBlinds v2 since 2019, and I just replaced 2 of them with v3.1. I've always had issues with the units responding consistently. The answers I've gotten from their support is "try repairing it closer", or you need to have beaming repeaters. I have 75 Z-wave devices in my house, and every single device that is hard wired is beaming. I think they just have a script that assumes it's the users fault, and they really aren't interested in helping.
I could set up a ping hourly, and that may help with connectivity. I don't run them all at once. I have Reactor set to "wait for completion" on each of the reactions before moving on to the next one.
None of this unfortunately addresses the issue of the switch control and the cover control not being in sync. I don't seem to have a .refresh command in HA, or at least I'm not sure where it is. If that syncs them up, then I'll be happy. Where is that refresh command located?
-
T toggledbits forked this topic on
-
@gwp1 said in Can I use Dynamic Group Control for Triggers and Reactions?:
@tamorgen That sounds vaguely familiar!
Low and behold iBlinds support finally got back with me, and they actually acknowledged the original problem I was seeing was actually a problem.
Hi Timothy, Very sorry for the delayed response, we have been getting more reports of this issue and have been building up to a solution. We have determined this to be a driver issue within Home Assistant that will need to be addressed for each hub. We have never really sent battery report until battery level drops to the low battery alert threshold and this feature is required by zwave certification. We always had the hub poll the battery level since some hubs opted for polling the device independently of the device sending a report. We will need to add polling to the HA driver and other drivers of the same issue. Thank you for your patience. Thanks, Chance H. The iBlinds Teamand
Hi Timothy, To add to this, the polling will update the position as well as the battery to address your issue specifically. Thanks, Chance H. The iBlinds TeamFeeling some vindication, after their original emails were all to the tone of "you're doing it wrong, you need to exclude and pair your devices. You need beaming repeaters (I guess the 55 other devices that aren't battery powered and are beaming don't count)."
-
T toggledbits locked this topic on
-
T toggledbits unlocked this topic on
-
I've split this topic. This thread remains for discussion specific to iBlinds only; if you have further comments on your issue getting ZWaveJSController running, please make those in the new thread where that specific discussion takes place.
-
@toggledbits said in Can I use Dynamic Group Control for Triggers and Reactions?:
I've split this topic. This thread remains for discussion specific to iBlinds only; if you have further comments on your issue getting ZWaveJSController running, please make those in the new thread where that specific discussion takes place.
Thanks Patrick, that's fine. I knew it was going off on a bit of a tangent and asked you to fork it a bit ago.
Back to the original subject, now that I'm have ZWaveJSController working and I can use the refresh command, I still want to set up a rule based upon a state changing to poll the entity and force that refresh.
I set up the Dynamic Groups in my reactor.yaml using the zwavejs entities. I have three ones set up. One for the switch state, one for the position state, and one for the cover state. This way, I can run refresh if anyone of them changes. If there is a better way, please let me know.
"iblinds_switch": select: - include_entity: - 'zwavejs>63-0' - 'zwavejs>62-0' - 'zwavejs>64-0' - 'zwavejs>65-0' - 'zwavejs>79-0' - 'zwavejs>77-0' - 'zwavejs>78-0' - 'zwavejs>206-0' - 'zwavejs>205-0' - 'zwavejs>75-0' - 'zwavejs>74-0' - 'zwavejs>71-0' - 'zwavejs>16-0' - 'zwavejs>61-0' filter_expression: > entity.power_switch.state "iblinds_position": select: - include_entity: - 'zwavejs>63-0' - 'zwavejs>62-0' - 'zwavejs>64-0' - 'zwavejs>65-0' - 'zwavejs>79-0' - 'zwavejs>77-0' - 'zwavejs>78-0' - 'zwavejs>206-0' - 'zwavejs>205-0' - 'zwavejs>75-0' - 'zwavejs>74-0' - 'zwavejs>71-0' - 'zwavejs>16-0' - 'zwavejs>61-0' filter_expression: > entity.cover.position.value "iblinds_cover": select: - include_entity: - 'zwavejs>63-0' - 'zwavejs>62-0' - 'zwavejs>64-0' - 'zwavejs>65-0' - 'zwavejs>79-0' - 'zwavejs>77-0' - 'zwavejs>78-0' - 'zwavejs>206-0' - 'zwavejs>205-0' - 'zwavejs>75-0' - 'zwavejs>74-0' - 'zwavejs>71-0' - 'zwavejs>16-0' - 'zwavejs>61-0' filter_expression: > entity.cover.stateThe rule I'm trying to set up is to look for any change on those switches (on to off or off to on), and then set a reaction to refresh the cover (zwave_device.refresh)
In the set reaction, it doesn't appear to let my dig down any further once I put the group in. What do I need to do to make this work, if it's even possible.
-
@tamorgen said in Can I use Dynamic Group Control for Triggers and Reactions?:
In the set reaction, it doesn't appear to let my dig down any further once I put the group in. What do I need to do to make this work, if it's even possible.
Experimental, undocumented feature: add
group_actions: trueto your group's configuration:"iblinds_switch": select: - include_entity: - 'zwavejs>63-0' ... - 'zwavejs>61-0' filter_expression: "entity.power_switch.state" group_actions: true -
@toggledbits said in Can I use Dynamic Group Control for Triggers and Reactions?:
@tamorgen said in Can I use Dynamic Group Control for Triggers and Reactions?:
In the set reaction, it doesn't appear to let my dig down any further once I put the group in. What do I need to do to make this work, if it's even possible.
Experimental, undocumented feature: add
group_actions: trueto your group's configuration:"iblinds_switch": select: - include_entity: - 'zwavejs>63-0' ... - 'zwavejs>61-0' filter_expression: "entity.power_switch.state" group_actions: trueThanks Patrick. I'll give that a try.
-
@toggledbits said in Can I use Dynamic Group Control for Triggers and Reactions?:
@tamorgen said in Can I use Dynamic Group Control for Triggers and Reactions?:
In the set reaction, it doesn't appear to let my dig down any further once I put the group in. What do I need to do to make this work, if it's even possible.
Experimental, undocumented feature: add
group_actions: trueto your group's configuration:"iblinds_switch": select: - include_entity: - 'zwavejs>63-0' ... - 'zwavejs>61-0' filter_expression: "entity.power_switch.state" group_actions: trueYou said it was unsupported
Reactor doesn't seem to like my filter.
[latest-23078]2023-04-03T18:19:59.724Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.power_switch.state error with Light#zwavejs>63-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-]These are the values when I look at the Entities tab for one of the blind controllers.
-
Well that has nothing to do with group actions. It's specifically complaining about your filter. Hass is famous for giving null state when a device is unreachable or still initializing. If the DGC comes up faster than Hass, you get those messages. They usually don't stick.
And please remember the posting guidelines. When posting an error, don't just post the error message; you need to post several dozen lines from before it, for context.
-
@toggledbits said in Can I use Dynamic Group Control for Triggers and Reactions?:
Well that has nothing to do with group actions. It's specifically complaining about your filter. Hass is famous for giving null state when a device is unreachable or still initializing. If the DGC comes up faster than Hass, you get those messages. They usually don't stick.
And please remember the posting guidelines. When posting an error, don't just post the error message; you need to post several dozen lines from before it, for context.
Understood, however, the system has been back up for white a while, and it just keeps repeating those errors. The lines I'm seeing before are unrelated and appear to be just normal reactions in my system.
[latest-23078]2023-04-03T18:44:11.461Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.cover.state error with Light#zwavejs>63-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T18:44:11.462Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.cover.state error with Light#zwavejs>62-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T18:44:11.462Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.cover.state error with Light#zwavejs>64-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T18:44:11.462Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.cover.state error with Light#zwavejs>65-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T18:44:11.462Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.cover.state error with Light#zwavejs>79-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T18:44:11.462Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.cover.state error with Light#zwavejs>77-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T18:44:11.462Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.cover.state error with Light#zwavejs>78-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T18:44:11.462Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.cover.state error with Cover#zwavejs>206-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T18:44:11.463Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.cover.state error with Cover#zwavejs>205-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T18:44:11.463Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.cover.state error with Light#zwavejs>75-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T18:44:11.463Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.cover.state error with Light#zwavejs>74-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T18:44:11.463Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.cover.state error with Light#zwavejs>71-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T18:44:11.463Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.cover.state error with Light#zwavejs>16-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T18:44:11.463Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.cover.state error with Light#zwavejs>61-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] -
I restarted Reactor to see if I could see anything coming back up.
latest-23078]2023-04-03T19:06:05.925Z <Structure:INFO> Structure#1 stopping DynamicGroupController#groups [latest-23078]2023-04-03T19:06:05.926Z <DynamicGroupController:null> DynamicGroupController#groups stopping [latest-23078]2023-04-03T19:06:05.926Z <Controller:NOTICE> DynamicGroupController#groups stopping [latest-23078]2023-04-03T19:06:05.927Z <Controller:ERR> Controller DynamicGroupController#groups is off-line! [latest-23078]2023-04-03T19:06:09.706Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-23078]2023-04-03T19:06:09.710Z <DynamicGroupController:null> Module DynamicGroupController v22313 [latest-23078]2023-04-03T19:06:09.746Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-23078]2023-04-03T19:06:09.750Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online. [latest-23078]2023-04-03T19:06:14.711Z <DynamicGroupController:INFO> All controllers ready, setting up dynamic groups [latest-23078]2023-04-03T19:06:14.728Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.power_switch.state error with Light#zwavejs>63-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T19:06:14.728Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.power_switch.state error with Light#zwavejs>62-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T19:06:14.728Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.power_switch.state error with Light#zwavejs>64-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T19:06:14.728Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.power_switch.state error with Light#zwavejs>65-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T19:06:14.728Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.power_switch.state error with Light#zwavejs>79-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T19:06:14.729Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.power_switch.state error with Light#zwavejs>77-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T19:06:14.729Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.power_switch.state error with Light#zwavejs>78-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T19:06:14.729Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.power_switch.state error with Cover#zwavejs>206-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] [latest-23078]2023-04-03T19:06:14.729Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.power_switch.state error with Cover#zwavejs>205-0: [ReferenceError] Invalid scope in reference to member state of (object)null [-] -
OK. Two things:
-
When I made the example for
group_actionsabove, I abbreviated the select and filter expressions, which I didn't expect you to copy verbatim; I just put it there for alignment/indenting. Use the select and filter expressions you had previously. -
Update to the 23093 version of ZWaveJSController I just released, which fixes another small iBlinds issue.
-
-
@toggledbits said in Can I use Dynamic Group Control for Triggers and Reactions?:
OK. Two things:
-
When I made the example for
group_actionsabove, I abbreviated the select and filter expressions, which I didn't expect you to copy verbatim; I just put it there for alignment/indenting. Use the select and filter expressions you had previously. -
Update to the 23093 version of ZWaveJSController I just released, which fixes another small iBlinds issue.
Thanks. I thought the filter expressions format had changed for with the group_actions flag, so I changed it to your example.
I also updated to the latest ZWaveJSController.
I still eppar to be getting those same errors, even with changing back to:
"iblinds_switch": select: - include_entity: - 'zwavejs>63-0' - 'zwavejs>62-0' - 'zwavejs>64-0' - 'zwavejs>65-0' - 'zwavejs>79-0' - 'zwavejs>77-0' - 'zwavejs>78-0' - 'zwavejs>206-0' - 'zwavejs>205-0' - 'zwavejs>75-0' - 'zwavejs>74-0' - 'zwavejs>71-0' - 'zwavejs>16-0' - 'zwavejs>61-0' filter_expression: > entity.power_switch.state group_actions: true "iblinds_position": select: - include_entity: - 'zwavejs>63-0' - 'zwavejs>62-0' - 'zwavejs>64-0' - 'zwavejs>65-0' - 'zwavejs>79-0' - 'zwavejs>77-0' - 'zwavejs>78-0' - 'zwavejs>206-0' - 'zwavejs>205-0' - 'zwavejs>75-0' - 'zwavejs>74-0' - 'zwavejs>71-0' - 'zwavejs>16-0' - 'zwavejs>61-0' filter_expression: > entity.cover.position.value group_actions: true -
-
entity.attributes.power_switch.stateand the same change for the others, like you had originally. -
@toggledbits
Thanks, that did the trick. Do I need to use the local expressions when using this approach? I'm guessing no. -
That would depend on what you're using them for. The only one I see above is to make a list of entity names from a group's members, presumably to use it in a message or something else not yet completed?
-
T toggledbits locked this topic on
