Fully Kiosk Browser: Installation and Full Configuration

This is a genuinely big, reference-style lesson about the Fully Kiosk Browser app. You'll install it on the tablet, launch the Panel dashboard full-screen, and work through every setting group that actually matters, Start URL, kiosk mode, the screensaver, motion detection, Remote Admin, and the automation interfaces.

Plan on roughly ninety genuine minutes, and honestly more on your first tablet. This is a reference lesson. You don't need to memorize every setting right away. Work through it calmly, configure the settings that genuinely matter most, and know which sections to come back to later if the panel starts behaving differently than you expect.

This lesson genuinely configures Fully as the panel's app. You'll also meet the screensaver, motion detection, Remote Admin, and kiosk mode, but you're not yet building automations inside Home Assistant. The integration comes in Lesson 7, and the full screen, brightness, night mode, and motion-waking strategy comes in Lesson 8.

What Fully Kiosk Browser actually is

Fully Kiosk Browser is a genuinely specialized Android browser built for what's called kiosk mode. An ordinary browser shows an address bar, bookmarks, history, and lets you wander away from the page entirely. Fully genuinely does something different, it launches one chosen page, your Home Assistant dashboard in this case, and keeps it full-screen. Alongside that it adds a genuinely large set of features useful for a device that has to keep running unattended.

In practice Fully genuinely can keep the screen on, control brightness, hide system bars, launch itself after a tablet restart, dim the screen after idle time, wake it with motion detected by a camera or microphone, block exiting the app, and offer a remote admin panel plus automation interfaces. That's genuinely a lot, which is exactly why this lesson runs long, and honestly why you might come back to it like a reference manual.

An ordinary browser carries an address bar, bookmarks, an easy way out, and no genuine control over the screen. Fully Kiosk gives you one dashboard, full screen, and genuine control over brightness, motion, and exit. The effect, the tablet genuinely behaves like a dedicated panel, not like an ordinary device. And it's genuinely worth knowing there's a whole family of Fully apps, but for a Home Assistant wall panel, Fully Kiosk Browser is the one that matters, it displays a web page, your dashboard, in kiosk mode. Fully Single App Kiosk instead locks a tablet to one chosen Android app rather than a web page, genuinely not what you need here. And Fully Video Kiosk is built for looping video presentations, typical digital signage, also not relevant to this module. Throughout this lesson, whenever it says Fully, it genuinely means Fully Kiosk Browser. The app works best on a typical Android tablet with a current WebView, variants like Android TV, Chrome OS, Android Go, or Fire OS can carry a genuinely smaller feature set or their own quirks, we'll come back to Fire OS's limits toward the end of the lesson.

The free version and the PLUS license

Fully carries free features and features marked PLUS. You can genuinely trial every PLUS feature for free, but the app shows a watermark and small on-screen warnings while you do. To remove those and use PLUS features normally, you buy a license.

The PLUS Single license is genuinely a one-time payment of a few euros for one device, a lifetime version that includes future updates. The license is tied to a device identifier and can genuinely be transferred to another tablet later. That matters, since many of the genuinely useful panel features live specifically in PLUS. Basic, version-dependent features cover the Start URL, full screen, hiding bars, keeping the screen on, and autostart after a restart. PLUS features cover kiosk mode, the screensaver, motion detection, sleep scheduling, Remote Admin, and the automation interfaces.

Test before you buy, before purchasing a license, test every feature you genuinely need on your own tablet. The watermark doesn't get in the way of checking whether a given feature actually works on your device at all. Buying a license genuinely doesn't fix hardware or system problems. This module assumes you'll genuinely buy PLUS sooner or later, since the Home Assistant integration in Lesson 7 requires Remote Admin, a PLUS feature. While you're learning, though, you can genuinely work fine on the trial version with its watermark.

Installing on Android

On a typical Android tablet with the Google Play store, installation is genuinely simple. Search for Fully Kiosk Browser in Google Play and install it. Alternatively, you can download the APK file from the maker's website and install it manually. The APK genuinely comes in handy on devices without Google Play, Amazon Fire tablets, for instance.

Install the app, either from Google Play on a regular Android device, or from the APK file on the maker's site. Update Android System WebView, the component that genuinely renders pages inside Fully, and its currency has a real effect on how the dashboard looks and behaves. Launch Fully and accept the permissions, the app will genuinely ask for several, some, device administrator rights, for instance, are needed for screen dimming and Remote Admin. And open the menu with a gesture, Fully's menu and settings open by swiping a finger from the left edge of the screen toward the middle. Remember the menu gesture, swiping from the left edge opens the menu and settings. That genuinely matters, because once full screen and kiosk mode are on, there won't be any visible buttons left at all. If you've got gesture navigation enabled in Android, hold briefly at the edge before swiping.

Android permissions: what to accept and why

Fully genuinely can ask for several different Android permissions. Not all of them are needed right away, but some are genuinely required for panel features. Don't just tap through blindly. For each permission, it's genuinely worth knowing what it's actually for.

Device administrator is genuinely needed for stronger screen control, locking, and some kiosk features. Accessibility may genuinely be needed to intercept system buttons, particularly on certain devices and Fire OS. Camera is genuinely only needed if you use camera-based motion detection or camera snapshots. Microphone is genuinely only needed if you use sound-based motion or activity detection. And display over other apps may genuinely be needed to keep the panel on top and block exiting it.

Android settings outside Fully

You genuinely won't configure everything inside Fully itself. Android has its own battery-saving, app-sleeping, and screen-lock mechanisms. Leave them unchanged and the tablet might genuinely turn off Wi-Fi after a few hours, put Fully to sleep, or drop back to the lock screen.

Turn off battery optimization for Fully, Android shouldn't be allowed to put the panel app to sleep. Check Wi-Fi behavior during sleep, the panel needs to hold its network connection, otherwise Remote Admin and the integration will genuinely keep disappearing. Remove the screen lock if the panel's meant to start on its own, an Android PIN can genuinely stop the panel dead after a restart. And disable auto-rotate, if Fully's already forcing an orientation, Android shouldn't be fighting it.

The menu and its 300-plus settings

Fully genuinely carries over three hundred options, grouped into sections. That's overwhelming at first, but you genuinely don't need to know all of it. This lesson walks through the sections that actually matter for a Home Assistant wall panel, and flags what's most important in each one, Web Content Settings for the Start URL and login, Web Browsing Settings for browser behavior and reloading, Toolbars and Appearance for full screen and hiding bars, Device Management for screen, brightness, orientation, and autostart, Power Settings for sleep and wake scheduling, Screensaver for the screen dimmer, Motion Detection for waking the screen with motion, Movement Detection for detecting the device itself being moved, Kiosk Mode for locking down the exit, Remote Administration for the remote panel and the bridge to Home Assistant, and the REST, MQTT, and JavaScript interfaces plus Fully Cloud.

Web Content Settings: the Start URL

This is genuinely the single most important setting in the whole app. Start URL is the address Fully loads on launch and returns to after recovering from an error. Here you enter your Home Assistant Panel dashboard's address, starting with http or https, carrying an IP address or server name, a port, and the path to the dashboard.

A typical address looks roughly like the example below, using your own Home Assistant address, port, and the dashboard path you built in Lessons 3 and 4. A trailing suffix is sometimes used to hide Home Assistant's sidebar, but we'll come back to that under kiosk mode. A sample Start URL would look like http://192.168.1.50:8123/panel-dom/0. Good in a home setup, a local Home Assistant address, like http://192.168.1.50:8123/panel-dom/0. Handle with genuine care, a public internet address, a tunnel, or a remote domain. It might work, but a household panel genuinely shouldn't lose function just because the internet went down.

Check the address in an ordinary browser first, before typing the Start URL into Fully, open that exact address in a regular browser on the tablet. If it doesn't work there, it genuinely won't work in Fully either. Fix the address, Wi-Fi, DNS, or the login first, then configure the kiosk. IP address, use a fixed IP address for the Home Assistant server. If the address changes, the panel will genuinely stop loading the dashboard. Dashboard path, this is the exact address of the Panel view, not the login screen or settings, the panel should genuinely open directly on Start. And login, this section also carries a spot for login credentials, that's login to the page itself, the Home Panel account topic was covered back in Lesson 3.

Logging into Home Assistant itself, the simplest path, enter the Start URL, launch the dashboard in Fully, and log in normally with the Home Panel account. Don't log the tablet in as administrator. The login credentials saved in Web Content settings relate to page-level mechanics and aren't genuinely needed if Home Assistant remembers the Home Panel user's session. Why a fixed address genuinely matters, the panel hangs on a wall and nobody's going to fix the address daily. If Home Assistant gets its address from DHCP, set an address reservation in the router or a fixed address on the server. Otherwise, after a network restart the panel might genuinely show an error instead of the dashboard.

Web Browsing Settings: how the page behaves

This section decides how Fully genuinely behaves as a browser. For a wall panel, what matters most is that the dashboard genuinely recovers on its own after a restart, a network drop, or an error. A handful of options genuinely make a real difference here.

Wait for Network Connection, don't try to load the page until there's actually a network. That way, after a restart the panel genuinely waits for Wi-Fi instead of showing an error. Load Start URL on Home Button, tapping the home-screen button returns to the dashboard, and it genuinely works in kiosk mode. Enable Pull to Refresh, pulling down refreshes the page, convenient during testing, but in daily use it can genuinely get triggered by accident. And Auto Reload on Idle, an automatic reload after idle time, useful if the dashboard genuinely tends to lose its Home Assistant connection over time. There's also a whole group of Auto Reload options, reloading after a page error, after reconnecting to the network, or after the screen turns back on. You genuinely don't need to enable everything at once. It's genuinely good to start with waiting for the network and reloading on error, then fine-tune the rest if you notice problems.

Toolbars and Appearance: getting to full screen

Here's where the tablet genuinely becomes a real panel. You hide every bar and button that reminds you it's an ordinary device. The goal is for the screen to genuinely show only your dashboard, no address bar, no Android status bar, no browser elements at all.

Show Navigation Bar, turn this off to hide the system's bottom navigation bar. Show Status Bar, turn this off to hide the top status bar with the clock and icons. Show Action Bar, turn this off to hide Fully's own bar with browser buttons. Show Address Bar, turn this off to hide the address bar. Full screen isn't just about looks, hidden bars genuinely mean less room for accidental taps and less temptation to leave the panel. That lines up exactly with the layout principles from Lesson 5, fewer distractions, more room for the dashboard.

Device Management: screen behavior and autostart

This section genuinely controls the screen's physical behavior and how the app launches. For a wall panel it's genuinely one of the most important setting groups, since it decides whether the tablet's even fit for continuous wall duty at all.

Keep Screen On, the screen doesn't turn off on its own, the genuine basis of any panel meant to stay visible. Screen Brightness, sets the screen's brightness, usually on a scale roughly from 0 to 255. Force Screen Orientation, forces an orientation, landscape, say, so the panel doesn't rotate. Unlock Screen, Fully displays over the lock screen, so the panel returns immediately without manual unlocking. Screen Off Timer, a PLUS feature, how many seconds of inactivity before the screen turns off, zero means no dimming at all. And Launch on Boot, Fully launches automatically after the tablet restarts. Screen always on, or dimming, you've genuinely got two schools of thought here. One, keep the screen always on, dimmed only by the screensaver at night. Two, let the screen turn off after a delay and wake on motion. On some tablets, Fire especially, screen dimming can genuinely cause real trouble. That's why we'll build the full screen and night-mode strategy properly in Lesson 8, for now you're just genuinely learning the available options.

Power Settings: scheduling and sleep

In the power section, Fully genuinely can put the tablet to sleep and wake it on a schedule, and react to the charger being plugged in or unplugged. That's genuinely useful if you want the panel to sleep at night and wake up in the morning. Not every tablet wakes correctly from a schedule, so this feature genuinely needs testing on your specific device.

Schedule Wakeup and Sleep, a PLUS feature, sets sleep and wake times for each day of the week. Sleep on Power Disconnect, the tablet sleeps after power is disconnected, useful for a night-mode setup. And Prevent from Sleep while Screen Off, keeps the processor active despite a dark screen, needed for stable Remote Admin on battery, but it drains the battery considerably faster.

Screensaver: the screen dimmer

The screensaver's a PLUS feature and genuinely important for a panel that's meant to glow around the clock. Instead of physically turning the screen off, Fully can genuinely show a dark screen or dim the display after idle time, then return to the dashboard on a touch or motion detection. For plenty of tablets, Fire especially, the screensaver is genuinely safer than physically switching the screen off.

Screensaver Timer, how many idle seconds before the screensaver kicks in, ends on a touch or detected motion. Screensaver Wallpaper URL, what to show as the screensaver, a value like fully://color#000000 gives a plain black screen. Screensaver Brightness, brightness in screensaver mode, this is genuinely where you dim the panel for the night. And Screensaver Playlist, optional photos or pages, a plain dark screen is usually genuinely enough for a household panel. Screensaver instead of turning the screen off, on plenty of tablets, Fire included, physically switching the screen off can genuinely kill the app or force a manual unlock. It's genuinely safer to keep the screen on and use a screensaver with a dark screen and low brightness. We'll dial in the exact night-mode settings in Lesson 8.

Motion Detection: waking the panel with motion

Motion detection is a PLUS feature that genuinely lets the panel react to a person's presence. Fully can genuinely detect motion using the front camera or the microphone. When someone approaches, the panel genuinely wakes from the screensaver and shows the dashboard. When nobody's there, it genuinely returns to the dark screen after a delay.

Enable Visual Motion Detection, motion detection from the camera, genuinely works well with sensitivity set high, but needs decent light. Enable Acoustic Motion Detection, detection based on microphone sound, genuinely works even in the dark. Turn Screen On on Motion, turns the screen on when motion's detected. And Exit Screensaver on Motion, interrupts the screensaver when someone approaches. A camera running constantly has a genuine cost, camera-based detection loads the battery and processor, since the camera has to keep working continuously. It also raises a genuine privacy question. Plenty of users genuinely prefer waking the panel with a Home Assistant motion sensor instead of the tablet's own camera, we'll build that kind of external-sensor wake-up in the integration and screen lessons ahead.

Movement Detection: protecting against the device being moved

This is a genuinely separate feature from motion detection. Movement Detection uses the device's own motion sensors, the accelerometer and compass, to detect someone actually moving the tablet itself. You can genuinely use this to wake the screen, interrupt the screensaver, or trigger an audible alarm as a theft deterrent. On a household wall panel this is genuinely rarely needed, but it's worth knowing it exists.

Kiosk Mode: locking down the exit

Kiosk mode is a PLUS feature that genuinely restricts leaving the panel and steers the user straight back to Fully. Once it's on, a household member genuinely can't easily wander into Android, other apps, or settings. That said, it's genuinely not absolute protection, Android and the tablet maker can have their own shortcuts, buttons, and quirks. Fully will genuinely ask to be set as the default home-screen app, so the Home button returns to the panel instead of Android's own launcher.

Kiosk Exit Gesture, the gesture that brings up a PIN prompt, a double tap on the top-left and bottom-right corners, for instance. Kiosk PIN, the code required to exit kiosk mode, set your own, avoid 1111 or 1234. Set Fully as the Home App, the home-screen button returns to the panel, not to the system. And locking down buttons, you can genuinely lock the status bar, volume buttons, and other elements to further limit exiting the panel. Test exiting the kiosk first, before you leave the tablet mounted on the wall, run kiosk mode through fully, restart the device while in kiosk mode, enter the gesture, provide the PIN, and turn kiosk mode off entirely. Remember the PIN and the gesture. If you forget them, getting out of kiosk mode becomes genuinely difficult. On Android 12 and newer, kiosk mode carries some real limits without advanced device provisioning, so a long press on the power button will usually still let you power the tablet off regardless.

A fixed IP address for the tablet

Remote Admin, the Home Assistant integration, and later automations will all genuinely reference the tablet by its IP address. If the router hands it a different address every time, the integration will genuinely stop working. That's why the tablet should genuinely carry a DHCP reservation in the router, or another stable address on the local network.

A note worth writing down might look like tablet name Home Panel, location hallway, tablet IP 192.168.1.60, Remote Admin port 2323, Remote Admin password saved in the password manager, and Start URL http://192.168.1.50:8123/panel-dom/0. Don't guess the IP later, write the tablet's address down now, you'll genuinely need it in Lesson 7 when adding the Fully Kiosk integration in Home Assistant.

Remote Administration: the bridge to Home Assistant

Remote Admin is a PLUS feature and genuinely the key to connecting the panel to Home Assistant. Once it's on, Fully genuinely exposes a small admin panel on the local network at the tablet's address on port 2323. You can genuinely connect to it from a computer, check the device's state, change settings, take a screenshot, turn the screen on or off, and considerably more.

A typical Remote Admin address looks like http://192.168.1.60:2323. Enable Remote Administration turns on the remote panel and the automation interface. Remote Admin Password is the password required for the panel, the REST interface, and the Home Assistant integration, set a strong one and record it. And Remote Admin from Local Network needs enabling to connect from elsewhere on the local network, without it the connection genuinely only works from the device itself. This is genuinely the gateway to Lesson 7, it's exactly through Remote Admin and its password that Home Assistant will see the tablet as a device in Lesson 7, battery, screen state, brightness, app launching, and screen control. The tablet's IP address and the Remote Admin password are the two things you genuinely need to write down right now. Don't expose Remote Admin to the internet, Remote Admin genuinely lets you control the tablet, change settings, and trigger actions on the device. Don't forward port 2323 on the router out to the internet. If you ever genuinely need remote access, use a VPN or a deliberately configured service, not a simple port forward.

REST, MQTT, and JavaScript interfaces

Beyond the native integration, Fully genuinely carries its own automation interfaces. You don't need to know them for this panel, but it's genuinely worth knowing they exist, since people use them in more advanced setups. The REST interface offers simple HTTP commands over port 2323, turning the screen on, for instance, it genuinely requires Remote Admin and its password. MQTT integration lets Fully send device information and events to an MQTT broker, useful if you're building automations around MQTT. And the JavaScript interface lets a page genuinely control device functions, powerful, but potentially risky, so only enable it for pages you genuinely trust.

Don't enable everything "just in case," REST, MQTT, and the JavaScript API are useful, but they genuinely increase the number of things you have to understand and secure. For this course's path, Remote Admin plus the official Home Assistant integration from Lesson 7 is genuinely enough. This course genuinely takes the simplest, safest path, Remote Admin plus the native Home Assistant integration. You don't need to hand-build REST commands or configure MQTT, though you now genuinely know the option exists.

Fully Cloud and managing multiple devices

Fully also offers a cloud service, Fully Cloud, letting you genuinely manage devices remotely over the internet, including from outside the local network, and configure multiple tablets at once. That's genuinely more of a solution for businesses running multiple kiosks than for one household panel. For a home panel, Remote Admin on the local network is genuinely enough, with VPN access if you'd like a remote view.

Importing and exporting settings

You can genuinely save every Fully setting to a file and load it back later. That's genuinely handy. If you spend an hour dialing in the settings, export them to keep a copy. If something breaks, or you're swapping tablets, you'll genuinely load the file back and restore the whole configuration in seconds. Make a backup once configuration's done, once the panel behaves the way you want, export Fully's settings to a file and keep it alongside the Remote Admin password and the tablet's IP address. That's genuinely your insurance policy against a failure or a device swap.

A note on Amazon Fire tablets

Fire tablets are cheap and popular as panels, but their Fire OS is a genuinely specific Android variant. In practice it can cause more trouble than plain Android, APK installation, feature limits, and issues with the screen, the camera, Google services, and updates. If you've deliberately chosen Fire, here's what genuinely matters most to remember.

Install from the APK, on Fire OS you genuinely install Fully from the maker's APK file, since it's not in Fire's own store. Enable Detect Home Button in the accessibility settings, this is genuinely needed for kiosk mode to behave correctly on Fire OS. Don't turn the screen off with the camera running in the background, certain Fire OS versions genuinely kill an app using the camera once the screen goes dark, use the screensaver instead. And returning to the panel can genuinely be slower, on some Fire tablets, returning to Fully after pressing Home genuinely takes a few seconds. The rule for Fire, on a Fire tablet the genuinely safest combination is keeping the screen always on plus a screensaver with a dark screen and low brightness, without physically turning the screen off. That sidesteps most of Fire OS's known issues.

A recommended starting settings set

So you don't get lost among hundreds of options, here's a genuinely simple starting set for a Home Assistant wall panel. Set this up first, confirm everything works, then fine-tune the rest. For the minimum start, set the Start URL to the Panel dashboard's Start view. Hide the navigation, status, action, and address bars for full screen. Turn on Keep Screen On and force landscape orientation. Turn on Unlock Screen and Launch on Boot. Turn on Wait for Network Connection and reload on error. Turn on Remote Admin, set a password, and record it. And set the tablet's IP address as fixed and record it too. For fine-tuning later, add a screensaver with a dark screen and low brightness for night. Add motion detection, or wake the screen with a Home Assistant sensor instead. Add a sleep and wake schedule, if the tablet supports it. Add kiosk mode with a gesture and PIN, only after fully testing the exit. And export the settings to a file as a backup.

Test after a tablet restart

The wall panel genuinely has to come back on its own after a restart. That's one of this lesson's most important tests. It's genuinely not enough that Fully works when you launch it manually. After a power outage, an update, or an accidental restart, the tablet needs to genuinely return to the Panel dashboard by itself.

Restart the tablet. Don't touch it for a few minutes. Check whether Fully launched on its own. Check whether the Panel dashboard opened on the Start view. Check that the tablet didn't stop at the lock screen. And check that Remote Admin still works at the same IP address.

Test losing Wi-Fi

The second genuinely important test is losing the network. The panel shouldn't genuinely stay stuck forever on a blank screen or an error message. Once Wi-Fi returns, it should genuinely refresh Home Assistant on its own or return to the Start URL.

Disconnect the tablet from Wi-Fi, or briefly turn off the access point. Wait until the panel shows a connection error. Restore Wi-Fi. Check whether Fully returned to the dashboard without you manually re-entering the address. And if it didn't return, go back to the Wait for Network Connection and Auto Reload settings. Stability first, extras later, don't enable every Fully feature just because it exists. First set the Start URL, full screen, autostart, Remote Admin, and run the restart tests. Only afterward fine-tune the screensaver, motion, scheduling, MQTT, or a more advanced kiosk setup.

What we don't do in Lesson 6

This lesson's genuinely large, but it still keeps its scope. You're learning the app and setting up the basics. Full integration with Home Assistant and the final night mode come in the lessons ahead. We don't build the Home Assistant integration yet, adding the tablet as a device, sensors, and screen control is Lesson 7. We don't build the full night mode yet, exact brightness, screensaver, and wake settings are Lesson 8. We don't settle full security yet, the gate, the alarm, children, and guests are Lesson 9. And we don't seriously dig into REST, MQTT, or JavaScript, we're taking the Remote Admin and native-integration path instead.

What can genuinely go wrong

If the panel shows a login screen instead of the dashboard, check the Start URL and the login details, the address should genuinely point to the Panel view, not a login screen. If the panel shows a network error after a restart, turn on Wait for Network Connection and reload on error, and set a fixed IP address for the server. If the dashboard looks wrong or cards won't render, update Android System WebView, an outdated WebView is genuinely the most common cause of display problems. If the screen goes dark and won't come back, on plenty of tablets, Fire especially, use a screensaver with a dark screen instead of turning the screen off. If you can't exit kiosk mode, use the gesture and PIN you set, which is exactly why you should test the exit before mounting the tablet on the wall. If Home Assistant can't see the tablet, that's usually a missing Remote Admin, a missing password, or Remote Admin from Local Network turned off, we'll come back to this in Lesson 7. If the tablet gets stuck on the lock screen, remove the screen lock or check the Unlock Screen option, the panel should genuinely return on its own after a restart. If Remote Admin works from the tablet but not from a computer, check Remote Admin from Local Network, the tablet's IP, the password, the firewall, and whether the computer's on the same network. If an error lingers after losing Wi-Fi, turn on Wait for Network Connection and set a reload after an error or after the network returns. If Fully doesn't start after a tablet restart, check Launch on Boot, Android's battery restrictions, and whether the system is putting the app to sleep. And if you've forgotten the kiosk PIN, don't mount the tablet permanently until you've tested entering and exiting kiosk mode and recorded the PIN somewhere safe.

Assignment: launch the panel in Fully Kiosk

Your assignment here is genuinely to launch the Panel dashboard on the tablet in Fully Kiosk and set up the basics. You don't need to enable everything yet. The point is that the tablet genuinely shows the panel full-screen and returns to it on its own.

Install Fully Kiosk Browser and update Android System WebView. Set the Start URL to the Panel dashboard's Start view. Hide the navigation, status, action, and address bars for full screen. Turn on Keep Screen On, force the orientation, and turn on Launch on Boot. Turn on Wait for Network Connection and reload on error. Turn on Remote Admin, set a password, and record it along with the tablet's IP address. Set a DHCP reservation or a fixed IP for the tablet. Confirm Remote Admin works from a computer at the tablet's address and port 2323. Run the restart test. Run the Wi-Fi loss and recovery test. Turn off Android's battery optimization for Fully if the system applies one. And export Fully's settings to a file as a backup.

Key takeaways

Ready for Lesson 7?

Confirm honestly that Fully Kiosk shows the Panel dashboard full-screen, that the panel returns on its own after a tablet restart with no help from you, that Remote Admin is enabled and its password recorded, that you know the tablet's IP address and have it written down, that you've got a copy of Fully's settings saved to a file, that you've tested exiting kiosk mode with the gesture and PIN if you're using it, that the tablet has a stable IP address or a DHCP reservation, that the tablet returns to the Panel dashboard on its own after a restart, that the panel can recover after a brief Wi-Fi loss, and that Remote Admin isn't exposed to the internet.

What's next

In Lesson 7 we'll genuinely connect the tablet to Home Assistant through the native Fully Kiosk integration. Thanks to Remote Admin being enabled and its password recorded, Home Assistant will genuinely see the tablet as a device with battery and memory sensors and with screen control. That opens the door to panel automations and to the night mode built in Lesson 8.

What genuinely matters right now is that the tablet has stopped being an ordinary device. Once it's on, it genuinely shows your household panel, keeps it full-screen, and returns to it on its own. That's the foundation the rest of this module gets built on.