I haven't added support for that yet
Hi @jpage4500,
I'm having a problem with geofencing on one of my devices. I use HD+ geofencing on 4 phones. 3 of them work fine. One of them has stopped reporting the "departed" event consistently. However, even that phone works properly for the "arrived" event.
What can I do to troubleshoot this?
I'm trying to use HD+ widgets for displaying text (such as "rain", "sunny", "cloudy") using a HD+ widget on my phone (These are text attributes of devices on my hub). Does anyone know if it is possible to output text data (such as might be found in a device attribute) via an HD+ widget? So far I'm only able to display numerical data via HD+ widgets.
@jpage4500, hoping I can get your help with a problem I am having.
I was successfully using the "HD+ Device" driver to make voice announcements on various devices. Now, when I try to speak some text from those devices I get the following error:
notifyVia: projectId not set, text: hello
I installed the device driver using HPM and I just ran an update to make sure I am on the latest version.
When I turn on debug logging I get the following warning:
logTokens: no parent device!
Any help you can provide would be greatly appreciated.
It's now done though a new app and the app needs to create the device. You also need to do some setting up of a dev account. The walkthrough on the docs page makes it easy to do though.
^^
Yep - what he said! Although I don't think it's easy 
I never really announced anything as I hadn't had time and wanted to make sure it was going to work without any issues.. but, it has been working for me for a while now so I'd say it's getting close.
It's a lot harder to configure than the previous version and I explain why in the doc below. On the plus side, I did find a flag I wasn't using previously which makes the notifications arrive pretty much instantly -- I've been testing with both native Hubitat app and HD+ and they both arrive at the same time. I'd be curious too if you see a difference with TTS -- including playback while the device is locked or the app isn't running.
https://joe-page-software.gitbook.io/hubitat-dashboard/tiles/hd+-companion-app-driver
side-note -- you will likely have to remove that previous driver as the new app creates one automatically.
side-note 2.. I want to get it to support multiple devices but haven't had time to really look at this.. when I get that part done I'll definitely post something
2 Likes
Until you do this, can you at least add a way to manually link the app with an existing device? I use my existing device in a lot of automations and it would be a pain to redo all that just to get push notifications.
Sure, I can try.. I'll have to look through some other apps for examples how to do this. I know there's an API get get all child devices but in this case it's not a child device since the app didn't create it. I think I might need a way to get all devices by type or something like that instead
I don't know if that's possible or if it is I can't find out how if there is
I just pushed an update that does this. It's super basic.. the button will add a new child device. For every new device you add, change it's name or label, add it to MakerAPI and then link it with HD+
I think you have to add a device selection box to the app's preferences. As per App Preferences | Hubitat Documentation
Options for type on input are:
...
device.DriverName: provides a way for the user to select a device using the specified driver name (matched by driver name with spaces removed). Selecting by capability instead is generally recommended.
Do you have an example of how this is used? I searched github for an example of this but couldn't find one.
Then once it's selected I'd still need to link it somehow.. the child device calls methods on the parent like this
def projectId = parent.getProjectId()
I don't, but it works just like any other preference. You end up with a variable that points at a device.
Since you're going to limit devices to the HD+ driver, you could do something where the app pushes the project ID (and whatever else it needs) into the device when you save the app preferences. Then, the device can do something like:
if (has pushed value)
use that
else if (parent != null)
Look up from parent
else
Linkage is missing
Philips Hue ZB 9290022406A will not add to HD+ as a device. I have added it to HE and can control it with Generic Zigbee Switch driver.
Trying to add weather to a dashboard and when I tap + and then the Weather option, I only get the instruction dialog about using an OpenWeatherMap virtual device to create a weather forecast. I have a couple of OpenWeatherMap virtual devices set up, but HD+ doesn't seem to be able to see them...
What obvious thing am I forgetting...(again). 
Just stating the obvious here.....did you include those virtual devices in settings for the exposed devices in the Maker API for your dashboard?
1 Like
Looking for a place to hide...thank you very much for stating the extremely obvious and not judging.
1 Like
I'm surprised if it's just a generic switch and not a custom driver. Can you send me the JSON that MakerAPI reports? Maybe something's different than expected?
Here is a new Pixel tablet feature to access Google Home from the quick settings, the screensaver and the lock screen. Could HD+ do the same thing?
Has anyone seen an issue with image tiles not refreshing after the screen comes back on from the HD+ screensaver? I have several camera images set to refresh from the cameras' URLs every 2 seconds. Works great except when coming back from the screensaver being on. If I change the cropping of the image, it usually "kickstarts" the refresh again (or if I close and re-open HD+). This only seems to happen with the HD+ screensaver setting - I can turn the screen off via the tablet's power button then back on and the images are still refreshing. Thanks!
