Thanks vbier, just tested the latest release from Github and it works 
Thank you !
Hi guys,
Did google change something in the webview component yesterday, resetting cookies?
Magically both of my HPV panels stopped displaying the Habpanel.
It appears that both were set to local storage, and I had to manualy repoint them to the server stored one, and reapply the home page to display. weird.
Maciej
Volker, is it perhaps time for an update of the version in F-Droid?
How to set this up?
When I lock the screen (ADMIN_LOCK_SCREEN), the screen goes off, but I can wake it up by pressing the power button briefly.
After that I have full control about habpanel.
Is there a trick to prevent this?
If I am not home it must be locked (used to work with Fully Kiosk by the way).
EDIT: By the way:
How to unlock remotely?
SCREEN_ON, RESTART, SHOW_DASHBOARD…
Nothing results in showing Habpanel again.
I like this look as well very cool congrats
After a long time, I was now able to fix a rare reconnect problem I had when restarting openHAB. This was the one problem holding me back to create a new release. As this is now history, I have just released a new version on github. As always, fdroid will hopefully pick this up in a few days.
0.9.26
- add reporting of docking state
- add reporting of device movement
- add reporting of currently shown URL
- add reporting of battery temperature
- use the default port when checking server url preference if no port is specified
- add red border around webview when SSE is not connected
- add debug log activity
- new commands: NOTIFICATION_SHOW, NOTIFICATION_HIDE
- disable camera and microphone related preferences on start if permissions are missing
- add support for password protected openHAB servers
- use okhttp for realizing the SSE connection
- improve menu layout
- BUG: allow access to http pages for android 9 devices
- BUG: fix reconnect during openHAB startup
4 Likes
Hi.
Is that normal that the HPV drain so much the battery? Almost 10% in an hour?
Thanks
Nikos
I would expect that it varies with the usage scenario. If you enable sensors or motion detection, it will probably drain a lot of battery. If you disable everything, it shouldn’t.
Thanks for your response.
You have right the motion detection drain the battery so fast.
@vbier, is it possible to change the length of time before motion detection reports OPEN?
I’m trying to replicate FullyKioskBrowser’s ability to wake the screen when motion is detected, so that HPV will turn on the display whenever I walk in front of it. However, it seems that it has to go one full minute without detecting motion before the OPEN report is sent.
It would be great if the ability to wake the screen on events could be built right into HPV to avoid latency (from sending the value to OH and the command back to HPV). Is that in consideration for future development, or something that’s been ruled out?
Sorry if these questions have been asked before (this is a long thread).
Thanks for your efforts!
Waking up the display was once part of HPV, but has been removed. The decision was to remove any logic out of HPV and into openHAB rules. HPV will only report and react to commands, as this gives you the complete flexibility.
But without guarantee on when this will be implemented.
When I was running HPV, I had it set up so the charger was plugged into a smart plug. OpenHAB used battery level (sent by HPV) to start charging at 20% and shut off at 90%. I had the plugs status being logged by persistence and looking at it in grafana revealed the battery would cycle all the way thru the charge / discharge cycle about twice a day.
Russel, I actually accomplished this with a motion sensor which happened to be mounted just above the tablet. The tablet sat on a stand on the kitchen counter and there just so happened to be a motion sensor mounted on the end of the kitchen cabinet just above the tablet.
The motion detection on the tablet (at least mine anyhow) functions from the video detecting changes in the field of view. Well, it doesn’t work very well in the dark or low light conditions. With the motion sensor waking the screen, I could walk out in the middle of the night and the screen would wake up
I’ve done something similar. My main motion sensor is on the other side of the room from my wall-mounted phone, so I’m using it to trigger the screen. It’s a Belkin Wemo sensor that goes back to idle after five seconds (which is great), but the latency is higher than I’d like.
I think it would make sense to have this ability baked into HPV, but I can appreciate @vbier’s rationale for removing it.
Yeah no, HPV is not for recreating the wheel, motion detection thru tablet video is all over playstore, thanks Volker for this great OpenHAB interface!
hi @vbier 0.9.26 is really nice. Seems to run smoother now on a Samsung Note 10+ with hardware acceleration. Question, I use this app to connect to my private openhab cloud, and the ‘store credentials’ doesnt work. A restart will request the credentials again. There is also a red border around the outside of the app. I assume this is something to do with the connection. How can I disable this or do you know why this occurs? The app seems to work OK from my small testing.
Thanks
I have added configuration of the motion timeout. If you want to try it out, install the apk from the master branch or wait for the next release (which will probably take some time)
Great, I’ll try it. Thanks for your work!
Ignore this earlier reply (which is now removed).
After switching to the latest version of HPV, I forgot to disable all battery optimization settings. I will have to assess the wifi connection experieince again.
Keep up the good work with the app!
Regards, Niklas.
Earlier reply removed.