Fully Kiosk often lose connection

[chemelli74]

The problem

I often find the integartion not connected, but the table answer to pings. Enabled debug mode but nothing appears in the log if not:

2024-04-15 14:31:03.154 DEBUG (MainThread) [homeassistant.components.fully_kiosk] Finished fetching 192.168.1.11 data in 0.013 seconds (success: False)

What version of Home Assistant Core has the issue?

2024.4.2

What was the last working version of Home Assistant Core?

2023.3.x

What type of installation are you running?

Home Assistant Core

Integration causing the issue

fully kiosk

Link to integration documentation on our website

https://www.home-assistant.io/integrations/fully_kiosk/

Diagnostics information

non available

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @cgarwood, mind taking a look at this issue as it has been labeled with an integration (fully_kiosk) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of fully_kiosk can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign fully_kiosk Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

fully_kiosk documentation fully_kiosk source _{^{(message by IssueLinks)}}

[erkr]

I have seen sporadic kiosk lost connections in my log as well. A few times per week in my case. Not hampering it's functionality in my case

[cgarwood]

In these instances, see if you can hit http://<ip.of.tablet>:2323 and get the Fully remote admin page to load. I've seen issues on some tablets (especially the Amazon Kindle Fires) where the Fully Remote admin page just stops responding for periods of time.

[ecchodun]

I have this same issue on three Lenovo M8 tablets. At 8:30 a.m. this morning one of my tablets randomly became unavailable and thus, every service related to that tablet become unavailable as well. The whole process from unavailability to becoming available again took approximately 43 seconds. The error in the log appeared as follows:

Error requesting 192.168.0.20 data: Cannot connect to host 192.168.0.20:2323 ssl:False [Connect call failed ('192.168.0.20', 2323)] Error requesting 192.168.0.210 data: Cannot connect to host 192.168.0.210:2323 ssl:False [Connect call failed ('192.168.0.210', 2323)]

[artgru]

I noticed the same issue as well, but this happened i think after the recent update of Home Assistant to the newest version. Before it worked just fine.

[kongjudas]

It happens several times a day on my Lenovo tablet. I am almost getting used to not having the screen available. I can't remember when it started, but it must have been around the HA 2024.4 update. I click "wait" on my tablet and then it pops up. So, HA is obviously available but just not found by Fully.

[skywalker0403]

I have the same problem. However, it was gone with me after I deactivated Fully Kiosk in an automation. Automation ensures that different dashboards are displayed at different times of the day. I realized for this function for a while with BrowserMod, during this time this message no longer existed at all.

Logger: homeassistant.components.fully_kiosk Quelle: helpers/update_coordinator.py:328 Integration: Fully Kiosk Browser (Dokumentation, Probleme) Erstmals aufgetreten: 08:43:49 (1 Vorkommnisse) Zuletzt protokolliert: 08:43:49

Error requesting 192.168.178.25 data: Cannot connect to host 192.168.178.25:2323 ssl:False [Connect call failed ('192.168.178.25', 2323)]

[harryfine]

I have the same issue. Lenovo tablet, newest fully kiosk version, using HAOS, 2024.7.3:

homeassistant.components.fully_kiosk Source: helpers/update_coordinator.py:318 integration: Fully Kiosk Browser

Are the developers looking at this?

[screech24]

I have the same issue. Lenovo tablet, newest fully kiosk version, using HAOS, 2024.7.3:

homeassistant.components.fully_kiosk Source: helpers/update_coordinator.py:318 integration: Fully Kiosk Browser

Are the developers looking at this?

Same issue here as well 106 occurrences in one day so far making the tablet basically useless.. hopefully this gets fixed soon.

[ecchodun]

This is definitely a Home Assistant issue versus Fully Kiosk app issue (though it could be related to its integration). I'm still having this issue, but I also noticed using Home Assistant directly from my tablet's browser will still display the Connection Lost error message.

[ecchodun]

Any updates on this? I recently bought a new Samsung A7 to replace my Lenovo M8 to see if I'd still get the error. I do. The only good news is that once it becomes unavailable, a minute later it comes back. Is there a way in HA to increase the time when it becomes unavailable? Logger: homeassistant.components.fully_kiosk Source: helpers/update_coordinator.py:360 integration: Fully Kiosk Browser (documentation, issues) First occurred: 1:12:59 PM (1 occurrences) Last logged: 1:12:59 PM Timeout fetching 192.168.0.32 data

[moonbit5]

I've also been experiencing this of late. Definetely related to recent update in approx the last 6 months – would love find a fix!

[bernfp]

Same issue in a Samsung A9. System: HA docker. Connection lost between 1 and 5 times a day. Sometimes the connection is lost for 30"/1' but other times it last for hours. Very interested to be fixed. Thanks in advance

[jofr666]

I have the same problem

Logger: homeassistant.components.fully_kiosk Source: helpers/update_coordinator.py:215 Integration: Fully Kiosk Browser (documentation, issues) First occurred: 24 oktober 2024 om 23:00:00 (2 occurrences) Last logged: 08:00:00

Error requesting 192.168.1.5 data: Cannot connect to host 192.168.1.5:2323 ssl:False [Connect call failed ('192.168.1.5', 2323)]

[MarioKuester]

I have the same issue since switching to HA 2024.11 and Fully 1.56.2. Strange thing is that I can still send commands (Load URL) that will work even if it is unavailable for 12 hours. Other commands like "Load Start URL" won t work.

[sciorty]

Glad to see I'm not the only one, but I'm starting to think it's a Fully kiosk application problem.

I have an Amazon Fire HD10 that is locked (kiosk mode) to the home assistant URL, I use a movement sensor to turn on the screen that is always locked to the Fully kiosk page.

In my case the integration loses the connection after some days/weeks and is unreachable, the screen is thus not turned on anymore. In this case, if I manually turn on the screen of the tablet, I find the screen to the home page (not the kiosk app) and after a few seconds the fully kiosk automatically opens again causing the integration to work again for a few days..

[maruchok-art]

Hi! The same issue Логгер: homeassistant.components.fully_kiosk Джерело: helpers/update_coordinator.py:385 інтеграції: Fully Kiosk Browser (документація, проблеми) Вперше відбулося: 04:19:44 (5 випадки) Востаннє записано: 10:52:59

Timeout fetching 192.168.88.15 data

[cgarwood]

I don't believe there's anything we can really do about this from the Home Assistant side, the errors come from the device not responding when Home Assistant requests a status update. Seems to be more common on slower devices (like Amazon Kindle Fires).

[moonbit5]

I don't believe there's anything we can really do about this from the Home Assistant side, the errors come from the device not responding when Home Assistant requests a status update. Seems to be more common on slower devices (like Amazon Kindle Fires).

That would make sense, but why would the integration work well for years previous to roughly the version number posted above?

[chemelli74]

Eventually should be closed as "won't fix"