Had also earlier, Homey-group with many my.homey.app sheets (always only one advanced flow sheet), and a lot of others (emails etc…) on same. Have you tried “fresh” browser" as seems to make difference on mine…
Now I have been many days w/o issue with (WIN11 pro)
DuckDuckGo: my.homey.app / advanced flow (and closed when not used, always single tab)
(back-up: remotely connected server where unused browsers, same strategy)
Google Crome: rest of my.homey.app tabs & telldus (many tabs, never closed, no more 10000ms issues)
Edge: all other items…
Tried today but still google Crome and Edge not opening advanced flows correctly (as as org issue in Edge, then “poluted” also Google Crome, at least look so). With DuckDuckGo nothing else done as installed just for testing…
It’s still flaky, but sometimes it just works as it should.
With Vivaldi browser @ Android: It doesn’t seem to differ when connected per local IP or per my.homey.app
Last Thursday and Saturday evening: drama, all’s very very sluggish.
Tonight: none of all that. It Works fine.
The other thing, “the dissappearing flow” bug (and losing all changes) is still present;
A similar effect also appears with Homeyscript: When returning to an unfocused browser with an opened Homeyscript, the script screen just gets cleared, all unsaved edits are lost.
I have to select an other script, in order to get the previously edited script back on screen.
Red Error msg pops up: “Not connected after connect”
It’s occurring @ both Pro 2019 & Pro 2026, tested with 4 or 5 different browsers
I have got also this error earlier (only when advance flow issue started) but cannot recall what was special at that time (only got only at one session several times). The way I am using browsers (splitted) also made that one disappear (for now )
Just to share my “single browser” latest experience and how (it seems) to keep troubles away (at least here) as after some trouble-free time, started to see (too often) same trouble again.
So now doing (do not ask me why working as no idea) :
“do your thing” and do not leave open for long (when not used actively)
Before closing browser, move back to “Home”
Close the browser
I hope this work for others as well..
FYI: Got reply from Athom and seems that trouble-shooting promised to be WIP (sent them long list of screenshots with all combinations where issue seen (to remove doubt that on browser-side issue
Here it worked OK in general since my last post.
Only yesterday evening it was like this:
When selecting a card, it kept locked onto the mouse pointer, no matter what.
After a few browser refreshes, I could place the card on the grid again after picking one.
And from there on, no odd things were happening
I’m doing nothing special, I changed nothing on Homey or my network, apart from updating to v12.13.0 @ the day it was published.
I’m using the Vivaldi browser @ Android, local connection to Homey.
Had to work bit longer with flows yesterday and found no need to close single-tab browser (still same issue here if any other Homey-tab open on same browser), if:
I read somewhere that constant reconnection attempts by the web app to Homey was a factor in causing this issue. I see a new version of the web app was released today with a change to the reconnection logic. Not sure whether your browser is using the latest version or still has the old version in its cache.
Not sure how the web app gets updated locally, I always trusted on a sort of automatic system
So I checked the used versions;
Browsers: Vivaldi / Ecosia
OS: Android
Phone: local login: v1.15.0, my.web.app: v1.15.5
Tablet: local login: v1.15.0, my.web.app: v1.15.5
Homey Pro 2026 firmware: v12.13.0
The local app seems using different versioning, or something’s wrong with the update system.
I must say my.homey.app is more responsive, far from snappy; it didn’t come to mind to try this online version instead.
It’s just odd, I can’t get my head around the fact the local web app worked fine for the last several days, and today it’s just as bad since this issue started (november 2025).
That’s true, the local Homey Web App (for the newer generations) works locally so it’s likely embedded in the Homey firmware. You need to wait for the FW to be updated
FYI - The version of the local web app included in Homey firmware v13.0.0 is v1.15.0 by the way (just checked). So the same as in your current Homey firmware.
I checked it in the web app by going to Settings > General and then there is a Web App section that mentions the version. I think that is indeed the same link you are referring to.
Same situation today. All went well for the past days, and now all issues are back.
I updated the firmware to v13.1.1 last night, not sure if it can be related.
I’m glad it worked out for you, but I’d like to add it’s not a generic “solution”.
I don’t mind to continue in a new topic if you like, Eko; all in all you started this one.
)
:
