Fully Kiosk Browser

Yes, add card has reappeared.

Hello, I have Fully installed on my new MINIX X35-i Android box. I have a iiyama 32 touch monitor in portrait mode. All apps run beautifully in full screen mode, except Fully. Tried to force rotation. But it doesn’t change anything. Could this be related to Webview? Thanks !!Edit:
I have done this with magisk to 108 Webview but that didnt resolve the issue. Any ideas?

What start URL you have configured in Fully?

http://192.168.X.X:8123/lovelace/home?edit=1
or
http://192.168.X.X:8123/lovelace/home

http://192.168.X.X:8123/lovelace/home?edit=1

There we have the problem :slight_smile:
Use http://192.168.X.X:8123/lovelace/home

1 Like

Hi guys,
I struggle to find out which password this could be…
Please guide me in the right direction… thx and cheers

image

The one you set in fully app on device under remote access…

Hi all,
I’d like to use the microphone to access voice commands for HA Assist at the table, but when I try to do that, it says “Google Speech engine not found”…or something like that. Anybody get Assist to work on their Amazon FireTab HD10?

2 Likes

this is the password you configured on the fully kiosk for the remote administration > remote password

1 Like

Pro tip, put this in “advanced web settings” → “inject Javascript”

document.getElementsByTagName('body')[0].click();

When using browser_mod with camera enabled.
Then create an automation that presses the button.load_start_url after home assistant has started.

Now the cameras always work!

1 Like

So I see examples in this thread on how to send an image (doorbell ring) to a fully tablet via REST. The question I have is how is this done with multiple tablets? Would I have to create a rest command for each one? Are there any other options to send a doorbell image to multiple tablets at the same time? Thoughts?

I am using the browser_mod custom component which allows me to open a popup on all my tablets. In that popup I am displaying a “picture-entity” with the doorbell’s camera defined as “camera_image” parameter.

The following sample action shows how you can use one action and target 3 tablets:

action:
  - service: browser_mod.popup
    data:
      title: Doorbell
      content:
        type: picture-entity
        entity: binary_sensor.doorbell
        camera_image: camera.doorbell
        show_state: true
        show_name: true
        aspect_ratio: "16:9"
      size: wide
    target:
      device_id:
        - 204bxxxxxxxxxxxxxxxxxxxxxxxx29ac
        - 5774xxxxxxxxxxxxxxxxxxxxxxxxd069
        - 53b1xxxxxxxxxxxxxxxxxxxxxxxxa59e

However, what is also necessary (at least for me, using Amazon Fire HD 8 tablets) is to call the triggerMotion command which increases the screen’s brightness. And I do this by using a rest_command - one for each tablet.

Also, the browser_mod component comes with a close_popup service that I am calling after my doorbell sensor turns off (after about 1 minute after the doorbell was pressed).

1 Like

Nice one, will try this.

I’m now using a hidden dashboard tab with 1 camera card (Panel mode).
When the doorbell rings, an automation switches the tablet to the url off that hidden tab and turning the screen of the tablet on. After 60 seconds, return to dashboard and turn off screen.

Did you find some answers? I tried to get the camera working but also no success, no issues with a Fire Tab but the Galaxy now, its not working.

I stopped trying the REST sensor at all, but I got the camera working by using the Generic Camera integration. HTTP and basic authentication, for the still image I entered:
http://[Tablet_IP]:2323/?cmd=getCamshot&password=[yourpassword]

For camera / motion detection inside of home-assistant I turned to frigate (0.12+), no longer have browser_mod camera enabled. Works quick & stable.

go2rtc:
  streams:
    tablet1:
      - http://tablet1ip:2323/?cmd=getCamshot&password=mypassword
      - "ffmpeg:http://127.0.0.1:1984/api/stream.mjpeg?src=tablet1#video=h264"
cameras:
  tablet1:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/tablet1
          input_args: preset-rtsp-restream
          roles: ["record","detect"]
2 Likes

I too have been having reliability issues with browser_mod 2.0. I’m wondering if something like this would work for Blue Iris integrated cameras? How do you do the popups in FKB? Can you share your automation?

I’m mainly talking the other way around, using the camera’s inside my tablets and feeding it into home assistant. Displaying those feeds is another thing, and not really camera specific. Still using browser_mod for (custom) popups, device_id’s seems stable enough.

Just starting out with FKB and got MQTT all setup with assistance from @Robert_S 's post earlier in this thread. Getting the following “Invalid state message” error message, would anyone know what the issue is here or where to start?

2023-09-26 11:40:14.064 WARNING (MainThread) [homeassistant.components.mqtt.sensor] Invalid state message 
'{
"deviceId":"XXXXXXX-XXXXXXX",
"deviceName":"Lenovo Tab M10 Plus 3rd Gen",
"packageName":"de.ozerov.fully",
"batteryLevel":84,
"isPlugged":true,
"SSID":"\"XXXXXXX\"",
"BSSID":"00:11:32:93:6a:9b",
"Mac":"7A:FC:F0:07:52:C2",
"ip4":"10.1.1.76",
"ip6":"FE80::78FC:F0FF:FE07:52C2",
"hostname4":"10.1.1.76",
"hostname6":"fe80::78fc:f0ff:fe07:52c2%wlan0",
"wifiSignalLevel":8,
"isMobileDataEnabled":false,
"screenOrientation":90,
"screenBrightness":63,
"screenLocked":true,
"screenOn":false,
"batteryTemperature":24,
"plugged":true,
"keyguardLocked":true,
"locale":"en_AU",
"serial":"unknown",
"version":"1.53.1-play",
"versionCode":1211,
"build":"TB125FU_S100078_230713_ROW",
"model":"Lenovo TB125FU",
"manufacturer":"LENOVO",
"androidVersion":"13",
"SDK":33,
"webviewUA":"Mozilla/5.0 (Linux; Android 13; Lenovo TB125FU Build/TP1A.220624.014; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/117.0.0.0 Safari/537.36",
"foreground":"de.ozerov.fully",
"motionDetectorStatus":2,"isDeviceAdmin":true,
"isDeviceOwner":false,
"internalStorageFreeSpace":107892563968,
"internalStorageTotalSpace":113082777600,
"ramUsedMemory":2505674752,
"ramFreeMemory":1537069056,
"ramTotalMemory":4042743808,
"appUsedMemory":13495808,
"appFreeMemory":254939648,
"appTotalMemory":268435456,
"audioVolumes":[{"4":53},{"8":53},{"5":53},{"3":53},{"1":53},{"0":66},{"2":53}],
"installerSource":"com.android.vending",
"timestamp":1695681613828,
"scopedStorage":true,"displayHeightPixels":1200,
"displayWidthPixels":2000,
"isMenuOpen":false,
"topFragmentTag":"","isInDaydream":false,
"appStartTime":"2023-09-26 09:34:59+1300",
"isRooted":false,
"isLicensed":true,
"isInScreensaver":false,
"kioskLocked":false,
"isInForcedSleep":false,
"maintenanceMode":false,
"kioskMode":false,
"startUrl":"http://10.1.1.252:8123/dashboard-tablet/tablet?kiosk",
"currentTabIndex":0,
"mqttConnected":true,
"currentPageUrl":"http://10.1.1.252:8123/dashboard-tablet/tablet?kiosk"
}' 
from 'kitchen_tablet/deviceInfo'

This causes the error :
value_template: '{{strptime(value_json.appStartTime+"-0500","%m/%d/%y %I:%M:%S %p%z", "1/1/1900 00:00:00 AM")}}'

How it works:
value_template : '{{ value_json.appStartTime }}'

1 Like