Does it mean that? I only use mine locally but reading the docs, it would indicate that Cloud Auto should work the way that you want (local links while on WiFi, Cloud while away from home). However it does state that you must grant location permissions for that to work (you didn't mention whether you had done that)
I'm trying to understand what's happening here and maybe just missing something. When the screen saver is active the app just displays a black screen so the app should never go into the background. If goes into the background that sounds like it crashed.
I do get crash logs and I'll look through them tomorrow. Almost all of the crashes I've seen are due to the device being out of memory -- so that combined with a Fire Tablet and RTSP video streaming.. that could be too much for the tablet to handle. But, if there's something else in there I'll try to find it.
If you can send me the device logs I'll look at those too. I need to do more video testing anyway as that's not something I've spent a ton of time doing. I have 2 cameras but my dashboards (also Fire Tablets) are just using auto-refreshing images every 30 seconds instead of live video. I just didn't think they could handle video streaming.
@jpage4500, some new about the missing icons problem? I changed my phone by a new one and the problem persists...
I wonder if the issue is with the Google Play version of the app since I can see them fine and I am using the direct download apk.
I don't see why it would have changed but I'll check.
Can you send me device logs? There might be an error in there
HD+ for presence has worked great for a while. Recently it started notifying me while not moving for hours (phone sitting on counter) "Present" "Not Present". Now I get the following messages "Unable to Connect to Server" and " Command ON failed for HD+ Kevin". What should I be looking for?
If you send me the device logs I'll take a look. Even better if you can put the app into debug mode for a while and reproduce it too. Otherwise, look at the logs and look for an error. At least it should say if it's trying to connect to local or cloud mode
Well, I found the problem. The IP address for the Hub changed... Not sure how/when... Maybe a power outage... Anyway, I changed the IP address on both mobile devices and it is working again.
I just switched to this dashboard app a couple days ago on two wall mounted tablets that are always on. Love it so far, but having an issue where my dashboards get stuck and stop updating.
Both tablets are seeing the same issue, and it appears to be at the same time since they both show the same thing. One presence sensor and one contact sensor stuck. Doing a pull-down refresh doesn't fix it....I have to do a restore to get it to reload everything, then it updates.
I have both set to cloud mode off / local only currently, but it did the same thing previously on Auto. Mesh wifi - I'll try to bind each one to the closest AP, didn't have that already. Also don't have static IPs assigned, not sure if this matters.
Anything else I should be looking at to ensure these don't get stuck again?
Probably not the cause of your issues, but I had something similar when I started out using HD+ a couple of years ago.
I have some standard mechanical door locks and I’ve fitted micro switches behind the mortise bolts so that I know at a glance which doors are locked/unlocked. When I added the devices, I changed the icons to locked and unlocked but I think they were auto identified as ‘door’. I left them that way and sometimes they would be in the wrong state. The fix for me was to edit the tile device type from ‘door’ to ‘generic sensor’ (that reset the icons and then I just changed them back to what I wanted) They’ve never been in the wrong state since.
1 Like
If set to local only the AP or location permission shouldn't matter.. I just try to detect the current WIFI network and if it matches the one you set for the Hub then I use local mode. Otherwise, cloud mode. But, setting it to local only should prevent the need for any of that.
This is concerning since it's basically doing a full refresh. Do you see an error message saying 'unable to connect'? If you send device logs I'll take a look.
Also don't have static IPs assigned, not sure if this matters.
This might be it actually.. HD+ reaches the hub by IP so if that changed at any point it's going to fail to connect. There's an option in About -> Hubitat Hub -> Hub Details -> Discover Hub which will try to detect it using UPnP. Otherwise, can you check that the IP matches?
FWIW I've got 3 tablets always on during the day and they're still getting instant updates after running for months.
1 Like
I kind of forget about this happening.. I got into a habit of using a fixed IP address for any home server type device.
I should look into using mDNS (ie: "hubitat.local") as a fallback whenever the app can't reach the hub for a period of time.
FWIW I setup a Fire Tablet to show 2 live video streams and also set a screensaver for 5 minutes and let it run for the last few days. It was working well all day yesterday but this morning I noticed the app had crashed. There wasn't anything too useful in the logs but at least now I can reproduce the issue.. that's usually half of the battle.
Previously what I'd do is update the RTSP driver which does update quite frequently. But, this time I'm going to get AI to take a deep look and see if there's something I'm missing or could improve. I'm fairly sure it's an out of memory crash which isn't too surprising given these are $30 Fire Tablets.. but, if there's a way to prevent it I'll try to find it
1 Like
Yup! Won't happen again. Reserved IP 252 just for Hub... 
Sorry what I meant is the tablets don't have static IPs...but the hub does. I can set the tablets to have a static IP as well, not sure if that matters.
I'll check for logs on a pull down refresh next time...one of the two tablets got stuck again mid morning today.
RE: RTSP videos
I forgot to mention I'm using the ExoPlayer driver.. my Fire Tablet doesn't support the RTSP driver since it's for API 22+ only
I did push some changes to help prevent a memory leak. It's easier for me to get the update on my tablet this way so no need for anyone to do an update just yet.. I'll see if it can last overnight first.
My test device is stilling running this morning w/2 video streams! I'm using the ExoPlayer video driver on a Fire tablet (RTSP driver requires a later version of Android)
I don't think it has anything to do with the screen saver -- just every time the screen turns off and on again the video streams have to re-connect/etc. I'll keep it running for a few days though but I imagine just turning the screen on/off many times might be another way to reproduce it
Still going - worth a try if you have a live video feed on your tablet. Version 1.0.2799
Back to say I haven't had any more disconnecting / freezing issues. Not sure what the deal was, but it hasn't come back.
Also wanted to give a huge thanks for the presence sensing - MUCH better than the Hubitat app.
Also was able to get a RTSP feed running on my Galaxy tablet from my Tapo doorbell, as well as a periodic still frame on my much older Fire tablet using go2rtc on a Raspberry Pi. Cool stuff! Thanks for all your work on this.
1 Like
I have been running the ExoPlayer instead of the RTSP for the last 2 days with no crashes at all.
There seem to be a few smaller issues with ExoPlayer.
- When reconnecting it splashes the window with the ID and password to the RTSP feed and url for everyone to see
- There are very random and less than a second red time clock timers in the window Over th video), but less than a second
- I have seen the odd horizontal line in a video window (5% size of screen) that looks like static for a second or two.
But much better overall from the crash!! Can't wait to get the iPad fully working to get ride of the Fire Tablet!.
M
1 Like
I can fix that.. maybe just a more generic "loading.." text
red time clock timers in the window
not sure what this would be exactly but I'll look
I'm curious if the RTSP driver also works as well.. I can't test that with my Fire Tablet because it's too old but the RTSP driver I'm using at least indicates it's much faster/better than the ExoPlayer
