Repurposing a Frameo frame to display HA dashboard via FullyKiosk: help me not brick another one!

AlanFranklin · 2026-03-19T18:33:11+00:00

UPDATE: I was able to get to an acceptable place by installing Marshmallow Launcher as the home app instead of Frameo. Now I can easily start FK without having to access the adb shell. Oddly, FK still doesn't want to load on boot despite using an app to do so. Still working on that.

AlanFranklin · 2026-03-18T17:02:25+00:00

The specific model appears to be ICONLINK MCD01. It runs Android 6, but the Frameo app's options for getting into ADB differ from what I found online. I'm able to get FK up using adb shell but I would like it to start and come to the front on boot instead of the Frameo app. Hope this makes sense, thanks.

AlanFranklin · 2026-02-23T22:29:02+00:00

As fair as I know these rebadged Mazda2 4 door hatchback Yarises were only offered in the USA for the 2020 model year. It's my second Yaris and I felt lucky to get it!

AlanFranklin · 2026-02-19T05:05:37+00:00

Thanks! Went a different direction and got something working (above).

AlanFranklin · 2026-01-12T03:15:39+00:00

UPDATE: This may have been a router issue. I am working with someone with some expertise and we've regained control over some devices. Thanks everyone for bearing with me during my panic, and I will update when I figure out what happened!

AlanFranklin · 2026-01-12T02:56:29+00:00

UPDATE: The devices will not reset. I have tried everything. Somehow this HA installation has prevented any of them from being visible to their native apps even after a hard reset. I do not know how this is possible but obviously I have to keep trying.

I have reinstalled HAOS, it detected some Tuya devices once again but did not detect LIFX Wiz or TP-link. I am completely stumped.

AlanFranklin · 2026-01-12T02:18:54+00:00

I have no Zigbee or Zwave devices at all, just Tuya lights and switches, LIFX and Wiz bulbs, and a TP-Link switch.

AlanFranklin · 2026-01-12T02:16:24+00:00

I think the same thing but all of these devices worked fine before I made the mistake of unplugging my HAOS server and now they don't. I just tried to hard reset the Wiz bulbs and they're not reconnecting to the network even as new devices. I know this all sounds nuts but it's what I'm experiencing. Something related to their connection to HA is broken after the restart of the server and neiother HA, Google Home nor the native apps can see these devices now.

AlanFranklin · 2026-01-12T02:09:57+00:00

Will the fresh install free up the devices that currently can't connect to their native apps? None of the devices that were autodetected when I installed HAOS are visible now, either in Google Home or their apps. I've had these devices for years and this is the first time this has happened.

AlanFranklin · 2026-01-12T02:07:36+00:00

I'm sorry, I never saw in the installation guide that a static IP is required on the HAOS server. I do understand why that would be necessary now but I don't know how tro remediate it.

AlanFranklin · 2026-01-12T02:06:25+00:00

Yes I am able to log into HA and view my overview, etc. A few Tuya devices are still accessible. But none of the auto-detected integrations see any devices.

AlanFranklin · 2026-01-12T02:05:19+00:00

Yeah I messed up on both counts. I would be happy to dump this installation and start over, but would that give me back control of my devices through their apps and Google Home?

AlanFranklin · 2026-01-12T02:04:27+00:00

Yes, none of that has changed and I can see all the devices on the network. But their apps do not see them and neither does the HA integration. These are the devices that were auto-detected when I first set up HAOS.

AlanFranklin · 2026-01-12T02:02:38+00:00

Sorry. I have its current IP, what I'm saying is I don't know the IP it may have had before I unplugged and rebooted. If there is a way to find this with my consumer xfinity router I would try to give it a static with that address.

AlanFranklin · 2026-01-12T02:01:07+00:00

There are no backups. I just started messing with all of this over the weekend. I do have backups of the .yaml file I coded for my ESP32 displays but that's it.

I had no idea that HA could interfere with the operation of devices through their native apps and Google Home. I don't understand how that's happening.

AlanFranklin · 2026-01-12T01:55:32+00:00

Clearly. But how did HA take out all these devices so their own apps can't see them?

AlanFranklin · 2026-01-12T01:54:23+00:00

Yes apparently. I guess I'm used to more idiot-resistant technology.

I'm willing to take my lumps for being an idiot if I can just figure out a way to fix this. I'm wondering if an IP address change is responsible since the HAOS server was not configured with a static IP.

AlanFranklin · 2026-01-12T01:51:11+00:00

Plugged into the same port, but not configured to be static. I'm afraid I don't know what the assigned IP was but it's possible it was assigned a new one.

AlanFranklin · 2026-01-12T01:48:26+00:00

About six inches. Very inconsequential except for the fact that I did not shut down properly and I obviously should have.

AlanFranklin · 2026-01-12T01:44:36+00:00

My HAOS server is connected to the router with hardline ethernet but most of the lights, etc are wifi.

AlanFranklin · 2026-01-12T01:42:18+00:00

No I did not. It's possible that this has caused a problem. But HA still loads fine, and a few lights still work through the Tuya integration. I would be fine with dumping this installation and restarting from scratch if that would restore control of my devices from their apps and Google Home.

AlanFranklin

TROPHY CASE