Reporting in - I recently had to deal with some buttons and battery issues. My battery tile was reporting the devices (thanks!) and like a good robot, I replaced the batteries.
HD+ continued to show me battery issues - but the device was reporting a new battery as seen in the HE Device screens.
The manual Refresh (pull down from the top) did not refresh the battery tile. Waiting a few minutes it eventually caught up (10 mins?). It would be nice that the manual Refresh also forces the battery tile to refresh as well!
hmm.. I'll check. It should detect changes to any device with the 'battery' attribute. Did the devices themselves update their battery level? Just want to make sure the Hubitat got the new battery level. I know when I replace batteries it can take some time for the battery update to come in from Zigbee/Zwave or whatever device
In this particular case - it had updated on 2 Smart thing buttons - I had both pages open. I freely admit I was having issues with getting the buttons back online doing the factory reset dance on them. Hence me doing the 'pull down forced refresh' on my HD+.
It wasn't long before I noted it had updated itself - less than 30 mins as I recall but I really didn't time it. If you're eyes on says its part of the manual refresh - then NTF!
FWIW I did check and the battery monitor tile should update when the battery attribute changes on any of the tiles it's monitoring. Not that there couldn't be a bug somewhere in there but at least the code seemed like it should work
I'm trying to get the app to connect to my new hub. I hit discover and it finds the hub, but then says login failed. I don't have hub security enabled.
@waterboysh Are you saying that you had HD+ running on a previous hub? If so, that's the reason it's failing to login, as the config file has the old hubs token in it. That token from maker api is specific to the hub. You'll need to open and edit the file with the new hubs ID to get it to work. My dashboards are backed up to the hub so what I did was:
download the backup from the hubs file manager (or find it in your devices local storage)
open it with a text editor
replace the "token" in the file with the one from the new hub. You'll find that "token" in your maker api instance for HD+
save the amended file and upload it back to the hubs file manager
when you open HD+ select restore, restore from hub and select the amended backup file.
Yes, but I am not trying to migrate to a new hub. I got a C8 Pro while moving and decided to just start fresh on it without performing a migration. So I installed Maker API and added the only 2 devices I've added to the new hub. On the phone app, I logged out. The app is at the main login screen. I hit the discover hub button, it finds my new and only hub, but when I select it that's when I get the login failed message.
I've even tried doing the manual mode. I enter the maker API ID and access code and still get a login error. I cleared the app data and now both via the auto discover and manual options I get a pop-up that says invalid access token. I can go to the manual entry after doing a discover and it has the correct IP, ID, and access token entered.
I still think it’s the same issue I’ve mentioned. I’m guessing that even if you did not migrate hubs and started afresh, there is a cached HD+ config file on your device (phone, tablet). So you enter the correct maker api details at the app login screen to connect to your new hub, but HD+ then tries to load a dashboard from that cached config file on the device. That file contains the token from the previous hub which doesn’t match and so it fails.
You can either find and edit the file in your local storage, or if you’re starting afresh anyway, find and delete the file and HD+ will create a new one (with the correct token ID)
I really don't think so. I didn't delete just the cache, I deleted the app's data. That includes files and settings (and cache).
It also doesn't seem to actually be accessing the hub at all. At least Hubitat is not generating anything in the logs. Nothing under "hub" and nothing under Maker API, even after turning on debug logging. Both devices are on the same network.
Really strange.. I was going to say maybe you're running a newer or older version of Hubitat firmware that isn't able to capture the Maker API app ID or auth token. But, you said when you hit the manual login button it shows the correct IP, app ID and auth token? That should be all that's needed.
If you enabled debug logging, can you look at the debug logs and look for any login-related errors? Or if you're able/willing to send the logs that would help (menu -> about -> support);
Well, I don't know what this would have changed, but I went into Maker API and created a new access token. The HD+ app on my phone still did not work with the discover button (and nothing showed in the Hubitat logs for Maker API). So I tried the manual connect again and it worked. I messed around with it a bit and added the cloud token and tested that.... as far as I can tell everything is working now. I don't know what the problem was when I was trying the other day.
I've got an issue that I hope can be resolved. For the past several weeks I'm getting an error on HD+ from my Foscam video camera feed, "Failed - Read timed out" I've never had this in the past. I'm on version 1.0.2799 of HD+ and I get my video via RTSP. I'm using an android tablet. In fact I've got this setup on two tables both of which have the same error. The Foscam cameras are on their latest firmware with no errors on the Foscam app.
Any ideas?
I've been noticing that my presence detection has become less consistent. I'm thinking there are possibly issues with the combiner I use, but also noticed that HD+ has shown some unusual symptoms as well.
On looking at Recent Events I see these errors where it appears that HD+ is having a number of command departed or command arrived failures, see screenshots.
I'll test the RTSP driver with my cameras. I was able to find an issue with the ExoPlayer video driver a few weeks ago but was never able to test with this one because my Fire Tablets are too old to support it.
side-note -- I recently discovered go2rtc which will let me get my cheap $20 Kasa cameras as RTSP video feeds to HD+; it has to run on a separate server (raspberry PI) so not for everyone but should help video testing
Yeah that's the issue for sure. HD+ is trying to update the presence and the command is failing. It does re-try a couple of times I believe since I know when going from WIFI -> cellular sometimes the network isn't always ready. But, I haven't had any errors like this.
Something that could help is to enable debug mode (menu -> about). Then, after seeing this happen again, either send device logs (menu -> about -> support) OR view device logs in the app. There should be more context around the errors
@jpage4500 I apologize if this is covered somewhere above but I did look for it...
With the recent changes to folders I'm seeing that the icon colors ON the folder don't follow the same icon's color IN the folder at least not all. Specifically, I have a door that I've given red/green colors but the door icon on the folder stays white while a few months ago they'd be in sync.
I am able to view my camera using the RTSP driver. I'll let it run for a day and see if it continues to run. That said, I'm running on a newer Android device and not a low memory Fire Tablet too
-- if you enable debug mode and reproduce it - then send device logs (about -> support) I can look for anything that might help figure out the problem
I did notice that there's newer versions of the RTSP and ExoPlayer libraries but they require API 23+. Right now HD+ supports API 21+ so I'd have to raise the minimum version to support these updates. I checked and that means Fire Tablets from 2017 and older wouldn't be supported. But, maybe I can leave the min version at 21 and just not allow videos to be played until 23+.. that's 1 option. Not saying updating the libraries is always better too but generally speaking I try to keep them up-to-date.
