I did not really think about that. I have now changed the SCREEN_ON command to set brightness back to original value in case it is dimmed.
1 Like
In have a similar problem. My Lenovo tablet do not start remotly if I turn it of with âallow_screen_offâ and then try to start it with âkeep_screen_onâ. I have to turn it on with the switch. And I also have to send/update the item with âkeep_screen_onâ after I manually started the tablet to prevent it to turn of the screen.
I did work as expected with the old version of HabPanelViewer so it shuld not be any problem with the tablet.
I made a minor change to the code that wakes up the tablet, but that should not make a difference according to the android api docs. Can you please update to the newest version (I just pushed an update) and reproduce the problem? Afterwards open the Command Log from the menu and see if the commands have been received/processed by HabPanelViewer?
This is great, thank you.
I know I can set a default panel, but is there a way to set a default dashboard within that panel?
The âStart Panelâ option is what set which dashboard to open at startup. This is the actual panel name in the config (CASE sensitive, you can get by the last part of the url when you are on that dashboard.
Also, you can set the default panel in the PaperUI under Configuration->Services->UI->HABPanel
Ah, thanks Michael. I can see where my confusion came from. Iâve messed something up (very new to this).
You wouldnât happen to know where I can change that name - to change âdashboardâ to Lounge to get it back in sync. Or is it too late now?
I also should have known better that it was case sensitive on another test I did.
Iâm probably the only one, and maybe itâs because a lot is changing, but I thought there were panel configurations e.g.
and that the Lounge, Upstairs etc in my example were called Dashboards - the documentation would seem to support that. https://docs.openhab.org/addons/uis/habpanel/readme.html
That said, youâre entirely rightand for anyone else coming to this, entering âDashboardâ in the start Panel option opens up the Lounge one correctly.
Thanks for coming back to me on that - appreciated.
I ran into that when 1st starting with Habpanel as well. I created my 1st dashboard as âTestPanelâ which eventually became my âMain Menuâ⊠You canât rename the dashboard currently***. The easy way is to create a new dashboard named properly (ie. âMainMenuâ in my case) and then just copy all your widgets from the existing to the new one. (will have to arrange them again, but is a very easy/quick process)
***afaik. however, all the dashboard/panel config is all in a .json file which you could edit. However, 2 main caveats:
- not for novice
- OH service needs to be shutdown when editing .json files. OH reads on startup and overwrites as changes are made. It doesnât re-read any of them after startup.
Changing the id of a dashboard afterwards is not supported currently, but you can hit the âEdit the local panel configuration (experts only)â link in the screenshot above.
It will show you the JSON object and youâll be able to find the affected id and change it - be careful though!
1 Like
Hi to everybody
I download and test HABPanelViewer and it is good.
Iâd like to know if is possible to start an app from the status of an item in openHAB?
it will be very useful for example to switch from HABPanel and other app
cheers
valentino
@vbier - thanks for a very useful app! One thing I have been struggling with on the new test build is consistently getting commands to reach the tablet (Kindle Fire 7"). I have managed to get commands to get through a few times (and the command log shows these), but then for some unknown reason, commands stop going through. I have tried rediscovering the server etc, but still nothing. However, the auto-complete in the Command Item settings dialogue correctly shows the item.
Can you suggest if there is anything else I can/should be doing?
UPDATE: One thing I noticed is that the panel is showing ânot connectedâ in the menu, even though the dashboard appears to be showing fine (and responding to key presses). Doing a fresh discovery then re-finds the same server, and this time shows connected correctly for a period of time. Again, a short time later, the menu shows ânot connectedâ and commands stop getting through.
There are two connections involved: one made by the browser and one made by the app in order to get item state updates from openHAB. The second one is also used to show the connected state in the menu. I use a library for making the connection called com.tylerjroach:eventsource. This should, in theory, try to reconnect as soon as the connection is lost.
Can you grab the log and send me the interesting part?
I have just pushed an update that has a new command START_APP. It has one argument, which is the package name of the app. You can look that up in Settings->App->App of your choice. The package name is shown below the version, it is e.g. com.android.chrome for Chrome.
So with command
START_APP com.android.chrome
you can now start Chrome.
2 Likes
Iâve attached a logcat snapshot covering a period of from rediscovering the server to getting to a disconnected state - the whole process is only a couple of minutes. I hope this covers it but do let me know if you need anything further. Thanks again.
EDIT: Connection seems to get lost when the device goes to standby. I have tried using both with and without SSL (as with SSL it initially gave some warnings, which I told it to ignore), but the problem persists.
The log file below should cover a period where I have changed from https back down to http (and the connection is lost after standby)
This looks like the device is enforcing some kind of power saving mechanism. Does the Fire tablet have settings that allow to specify whether WIFI should stay enabled when the screen is turned off?
We already had some other people in this thread with Fire Tablets. Does anybody else have an idea?
Nothing obvious in the usual places. Iâve tried a setting in developer options that allows constant scanning for wifi roaming but that didnât help with the problem.
One odd thing that I noticed this time round was that when I came out of standby, HABPanelViewer was still showing as connected. However, no commands were getting through (and command log was showing empty). A few minutes later - with the device having remained continuously on - the HABPanelViewer showed its not connected status. I think the log attached captured this period.
logcat3.7z.xml (97.6 KB)
I have added some more logging. Can you please reproduce and update the log?
edit: please open an issue in github and we can continue there.
@vbier I have a few problems. Using an Amazon fire 7.
-
if i set the motion setting to updated openhab when it can see motion it only seems to work when i first open the app, I get a very quick message int eh openhab logs to say âset to openâ then âset to closedâ. If i turn on the preview window i can see it detecting the motion, the word âmotionâ shows up at the top of the screen but the openhab item is never set. I had this problem in the play store version and the new apk you uploaded.
-
if i setup the new command bits and send the SCREEN_ON command once the screen is off it will turn back on some times, but other times it causes the tablet to reboot or the app to hang.
Anything i can get for you to aid with investigation?
- If the contact is set to closed that means motion is detected. After a period without motion the contact is then set to open again (which means no motion).
- Buy me a fire 7
or grab a log and send it to me.
edit: please open an issue in github and we can continue there.
thanks for the reply
Iâm new here, where i can download the update version .apk of the app for test?
thanks
Valentino