I've released a couple of minor updates to the app today, now at v3.2.3 (per some discussion in another topic) with the following changes:
- Option to omit attribute name in notifications/TTS for custom groups (e.g., "Bedroom Lamp is on" instead of "Bedroom Lamp switch is on"). This is configurable inside each custom group.
- Alphabetize device names inside custom groups for both display in the UI and in notifications
As usual, HPM should have it, and manual install also works (only the child app code was updated if you are doing it that way).
Nice Job "
Just wondering a few things .. How to get Alexa to talk / notify me ?
and if you can add a off command to this ? Need a way to activate this with a OFF command Please.
I have add a switch : ALL ON/OFF - GROUP < that's always on till ALL lights go off.
or a way to add a switch ( a button controller ) or Scene Switch ?
I'll think about the switch thing, but for now, an easy workaround is a virtual switch that turns on (via some other means, perhaps a rule) in response to wherever you events you want.
For TTS, this is just an app and doesn't help you get such a device per se; like any app, you'll need a device on your system to use for that functionality. Nothing built in to Hubitat can send TTS to Alexa devices (well, not arbitrary text), nor does Amazon offer an official means to do so, but Echo Speaks is a popular community solution that many find to work for them.
Took your advice ..
I created a virtual switch and added that to the all / off command
A little more work But it works great thanks
Is there a way to set the Pushover notification priority within the device status announcer app? the pushover notifications work great but I wanted to change the priority.
Yes, enable the "Text to prepend..." option and put your priority there. See the Pushover docs for those.
Thank you for that, I knew the priorities but didn't know where to set them in the app. I appreciate you very much.
@bertabcd1234
Any chance we could get an option to omit the switch state (is on/off) from a custom devices group in addition to the attribute. I would like to announce a list of switches that are on without the actual announcemnt including the state.
I'm assuming you're already using the option to only announce if the devices are in a specific state? I've never considered leaving the "is on" part out of the notification/announcement since then I'd have no idea what it meant in my case. But a small code modification could probably get you there even without an in-app feature if you really wanted to...
I'd like to use the app to create a list of switches that are in an "on" state so that I can create an announcement to close windows.
"it's too cold outside, and furnace is running."
Yes I'm using the announce only if the switch is "on" and I've selected the omit attribute, but having the app notify "it's too cold outside is on, and the furnace is running is on" is odd.
Any guidance on where I would look to modify the code to achieve this?
From a quick look: around line 402, I see this:
statusReportList << """${d.displayName} ${customDeviceCapabilities."$capability"?.displayName} is ${d.currentValue(attribute)}"""
Replacing it with something like this should work, though note that it will affect all custom groups and not just switches:
statusReportList << "${d.displayName}"
Tried this, but it's still listing the "is on" perhaps wrong line to modify?
Maybe I meant line 411...didn't think through the logic of what runs when.
Modifying 411 does work, but it's with the omit attribute disabled, perhaps it should be 408?
but i guess it doesn't really matter since the attribute is also removed by modifying the code.
408 modification, made it work the way I expected/wanted. THANKS!
@bertabcd1234 Thanks again for the tip on how to tweak the app to remove the "is on/off" for my edge case usage. One more request if possible, can the output of rule be stored in a hub variable so that it can be used in another rule? I'm currently doing this by having two triggers but it's not ideal as it requires to seperatre messages sent. If I could have the 1st rule output include the content of the 2nd rule as a suffix that would be much better.
Check out the latest version.
I was thinking about this myself but ended up just creating a secret modified version of the app I just use for myself and did the whole announcement in that fork instead ... but this would have worked for me, too!
I just tried the new version, while i can get it create the list and populate a hub varialbe using the test announcment/notification in the app, it doesn't seem to trigger the hub variable update using the switch, presence, or time triggers.
I can't see any reason that should be happening; the code that does this is the same no matter how it's invoked. Can you enable debug logging for the app and see if there are any clues?
Note that the variable will be cleared if there is no text to notify or announce (debug logging will tell you this, and it's one reason it might be helpful).
I spent a couple of hours playing around with different combinations of settings, with the child app setup as follows nothing happens when the trigger device is activated. Only when the test annoucment button is pushed in the child app. I used your "proxy" notification device so the app didn't throw an error as I don't want the child to make an announcment just set the variable. I have debugging enabled, nothing is logged unless I use the test notification button.
The switch I set to invoke the child (vSwitch Update Inclmenet List) is triggered by an RM rule triggered by one of the "list" switches changing state.
Debug log if the test announcment/notification now button is pressed in child
Nothing happens if the trigger switch (vSwitch Update inclement list) is turned on
Just tried another child that uses contacts/locks the trigger worked on this one, so I assume it has something to do with the custom switches, but it worked before the latest version so I don't know why
I just did an HPM repair, then got this error when I did apply settings on this child
@bertabcd1234
I am trying to use the also write notification or TTS text to hub variable and am getting the same line 524 error when trying to save it.
When my trigger switch is turned on nothing is logged in the app but it works as expected if I push the test notification now button:
If I turn the hub variable option back off then it works fine again:
Any ideas?
