You should be able to simply try sending an Emergency message by typing in a string prefixed by [E] on the Pushover device’s details page in the “Device Notification” command at the top, and the press the command button.
Please disregard again. I figured it out. I created a separate device for emergency pushover notifications with some specific parameters including the repeat and timeout numbers. I thought they needed to be in the message, but apparently not. The acknowledge link in the app also worked. All good!!
anyone else having issue getting the specify sound call out to work #soundsname#? Perhaps this is only in the slightly enhanced driver and I'm just using the driver that's in Hubitat already? Thought I read that Hubitat incorporated the driver but perhaps this "enhanced" driver is still not part of the build. I'd like to be able to set 2 scenarios to both use the [H] so that it sounds off even if my ringer is flicked off (iPhone) BUT I'd like to specify Bugle sound for one scenario, and different sound for the other. Am I going about this the wrong way? My syntax is: [H] ** #bugle# After Hours Open %device% opened at %time%
Roger that. Much appreciated. Wasn't sure if the post indicating this driver being incorporated into Hubitat natively applied to this feature or not since it was a little older. I'll grab this community one! Thank you!
Sorry for the confusion... This driver will not make your phone "Speak", only a push notification.
The "speak()" command was originally added as it was the only way to pass a text string into the driver from some of the Hubitat apps back in 2018. Since then, pretty much all Hubitat apps support the 'deviceNotification()' command, and thus 'speak()' is no longer necessary. However, removing it might break some users setups, and thus it persists in the code.
Ok thank you. I am using Autonotfication/tasker currently and am looking for a less battery intensive TTS and SMS vs the Autonotfication plug in. I've been able to find solutions for everything except the Autonotfication Query I use for TTS and SMS. Neither one of these have simple solutions lol.
@guarddog13 My community Twilio or Plivo drivers support both SMS and voice capabilities. The stock Twilio driver is based on some early work of mine and doesn't provide voice capabilities. Both solutions are not that expensive but Plivo is a bit cheaper, less than $1 a month for a dedicated number and messaging.
Just create the exact same Pushover device on the second hub. Use the same key/credentials. It works great. No need to use Hub Mesh in this particular case.
Thanks for the work on this driver! Is there any way to get HSM to work with HTML-formatted URLs? Whenever I save the alert text with <A HREF=*** , it strips out everything inside the <>. It works fine on the test box on the device page.