Closed pickonedev closed 3 years ago
Very similar problem here on Fully Kiosk Browser on Android. With 2021.11.0 the HA frontend hangs with a rotating spinner and text "Loading data...". I can imagine that there is some JS error in the background but I cannot access any console on Fully to check that. Opening the frontend in Chrome on the same tablet works flawlessly. Downgrading to 2021.10.7 resolves the problem. Might be worth adding "& Fully" to the title of this bug report.
I am using Kiosk mode as well... but this problem appear even if I have by default, a dashboard without Kiosk But still, on my phone Huawei P30 Pro it is working ok, only on my tablets MadePad T10S I have this problem
And yes, on Chrome browser all good. I have the same issue but I don't want to downgrade :-(
Downgrading is painless if you have a terminal add-on installed (i.e. "Terminal & SSH"):
ha core update --version 2021.10.7
Downgrading is painless if you have a terminal add-on installed (i.e. "Terminal & SSH"):
ha core update --version 2021.10.7
Thanks!
BTW: I think the title should be something like:
Sorry for being imprecise.
BTW: I think the title should be something like:
* After core-2021.11.0 Update, HA Mobile **& Fully Browser** on tablets, stuck on "Loading Data"
Sorry for being imprecise.
No problem :-)
Same problem here
Downgrading is painless if you have a terminal add-on installed (i.e. "Terminal & SSH"):
ha core update --version 2021.10.7
Seems that the downgrade has solved my problem as well...
Same problem here
You can do the same thing, till HA will repair this bug.
Same problem here. tried with a fresh homeassistant 2021.11.0 and it does not have the problem
tried with a fresh homeassistant 2021.11.0 and it does not have the problem
Very well possible that this is the result of 2021.11 in combination with some other component. My first suspect was in fact browser_mod. But I uninstalled it and the problem persisted.
I found that Fully has a remote debugging feature. I will try to get that flying over the weekend. If it works it should be easy to look behind the scenes and identify the problem and the components involved. Most likely there is a JavaScript error that blocks the system during initial loading.
Update: Remote debugging Fully on the tablet per USB works perfectly. Tomorrow I will get HA back to 2021.11 and analyze the problem.
maybe this helps to narrow down the error: System: HAOS also Problem with "Loading data" after update to 2011.11 - but I use Firefox (same problem in private browser)
Scenario: use private brwoser and browse to x.x.x.x:8123 login with username and password ... "Loading data" (forever)
last message on core log: ERROR (MainThread) [frontend.js.latest.202111030] http://x.x.x.x:8123/frontend_latest/94a4fdf6.js:1:23438 RangeError: Invalid timeZoneName
if I go to console and type core restart the "Loading data" finally ends and the site can be used - however as soon as I enter "http://x.x.x.x:8123" into the browser - I am stuck with "Loading Data" again ...
downgrade to 2021.10.7 worked for me as well
In the iOS app I get this in the console: Unhandled Promise Rejection: RangeError: Invalid timeZoneName
I experience the same Problem. The mobile App hangs with "loading data". But for me it is regardless, if fully single app kiosk is running or not.
Made a full wipe of the device (Sony Tablet Z with Lineage Android 9), that didn´t change a thing.
Workaround is to restart the HA Server. This causes the mobile app on the Tablet to continue loading the data.
no problems on my phones.
Anyone have installed 2021.11.1? The problem still persists?
Anyone have installed 2021.11.1? The problem still persists?
2021.11.1 did not fix it :(
Sometimes I am asking if devs are looking here for solving some issues... And this is happening when I see a new update, without solving some important parts like this
For an easier workaround, try turning wifi off and on again (or on and off again) while it is stuck loading. This allows the app to start. No need to restart HA
I tried, but not working... I think the best workaround si with downgrade to 2021.10.7 :-D and wait.
Here is a first result of my debugging with a new workaround:
You have a time zone defined your HA frontend under Configuration > General (or in your configuration.yaml under homeassistant: time_zone:
). At Lovelace loading time this time zone is matched against a list of available time zones. If this match fails, the error RangeError: Invalid timeZoneName
is thrown, which some of you have observed.
For reasons I am still analyzing this list differs from browsers to browser. In Fully it does not contain "Europe/Paris" (which was my setting). But it contains "Europe/Oslo" which is actually the same time zone.
So a quick workaround is to try and set another time zone. Below you will find a list of zones that is active on Fully in my testing environment. I don't know if this list will be the same for your environment. But it might be a starting point. Changing/Testing is faster and easier if you do not set your zone in YAML but in the frontend.
I will report back when I have found the source of the different time zone lists.
List of time zones available in Fully with HA 2021.11.1. You must match the RIGHT part in Mixed Case writing!:
AFRICA/ASMERA: "Africa/Nairobi"
AFRICA/TIMBUKTU: "Africa/Abidjan"
AMERICA/ARGENTINA/COMODRIVADAVIA: "America/Argentina/Catamarca"
AMERICA/ATKA: "America/Adak"
AMERICA/BUENOS_AIRES: "America/Argentina/Buenos_Aires"
AMERICA/CATAMARCA: "America/Argentina/Catamarca"
AMERICA/CORAL_HARBOUR: "America/Atikokan"
AMERICA/CORDOBA: "America/Argentina/Cordoba"
AMERICA/ENSENADA: "America/Tijuana"
AMERICA/FORT_WAYNE: "America/Indiana/Indianapolis"
AMERICA/GODTHAB: "America/Nuuk"
AMERICA/INDIANAPOLIS: "America/Indiana/Indianapolis"
AMERICA/JUJUY: "America/Argentina/Jujuy"
AMERICA/KNOX_IN: "America/Indiana/Knox"
AMERICA/LOUISVILLE: "America/Kentucky/Louisville"
AMERICA/MENDOZA: "America/Argentina/Mendoza"
AMERICA/MONTREAL: "America/Toronto"
AMERICA/PORTO_ACRE: "America/Rio_Branco"
AMERICA/ROSARIO: "America/Argentina/Cordoba"
AMERICA/SANTA_ISABEL: "America/Tijuana"
AMERICA/SHIPROCK: "America/Denver"
AMERICA/VIRGIN: "America/Port_of_Spain"
ANTARCTICA/SOUTH_POLE: "Pacific/Auckland"
ASIA/ASHKHABAD: "Asia/Ashgabat"
ASIA/CALCUTTA: "Asia/Kolkata"
ASIA/CHONGQING: "Asia/Shanghai"
ASIA/CHUNGKING: "Asia/Shanghai"
ASIA/DACCA: "Asia/Dhaka"
ASIA/HARBIN: "Asia/Shanghai"
ASIA/KASHGAR: "Asia/Urumqi"
ASIA/KATMANDU: "Asia/Kathmandu"
ASIA/MACAO: "Asia/Macau"
ASIA/RANGOON: "Asia/Yangon"
ASIA/SAIGON: "Asia/Ho_Chi_Minh"
ASIA/TEL_AVIV: "Asia/Jerusalem"
ASIA/THIMBU: "Asia/Thimphu"
ASIA/UJUNG_PANDANG: "Asia/Makassar"
ASIA/ULAN_BATOR: "Asia/Ulaanbaatar"
ATLANTIC/FAEROE: "Atlantic/Faroe"
ATLANTIC/JAN_MAYEN: "Europe/Oslo"
AUSTRALIA/ACT: "Australia/Sydney"
AUSTRALIA/CANBERRA: "Australia/Sydney"
AUSTRALIA/CURRIE: "Australia/Hobart"
AUSTRALIA/LHI: "Australia/Lord_Howe"
AUSTRALIA/NORTH: "Australia/Darwin"
AUSTRALIA/NSW: "Australia/Sydney"
AUSTRALIA/QUEENSLAND: "Australia/Brisbane"
AUSTRALIA/SOUTH: "Australia/Adelaide"
AUSTRALIA/TASMANIA: "Australia/Hobart"
AUSTRALIA/VICTORIA: "Australia/Melbourne"
AUSTRALIA/WEST: "Australia/Perth"
AUSTRALIA/YANCOWINNA: "Australia/Broken_Hill"
BRAZIL/ACRE: "America/Rio_Branco"
BRAZIL/DENORONHA: "America/Noronha"
BRAZIL/EAST: "America/Sao_Paulo"
BRAZIL/WEST: "America/Manaus"
CANADA/ATLANTIC: "America/Halifax"
CANADA/CENTRAL: "America/Winnipeg"
CANADA/EASTERN: "America/Toronto"
CANADA/MOUNTAIN: "America/Edmonton"
CANADA/NEWFOUNDLAND: "America/St_Johns"
CANADA/PACIFIC: "America/Vancouver"
CANADA/SASKATCHEWAN: "America/Regina"
CANADA/YUKON: "America/Whitehorse"
CHILE/CONTINENTAL: "America/Santiago"
CHILE/EASTERISLAND: "Pacific/Easter"
CUBA: "America/Havana"
EGYPT: "Africa/Cairo"
EIRE: "Europe/Dublin"
ETC/UCT: "Etc/UTC"
EUROPE/BELFAST: "Europe/London"
EUROPE/TIRASPOL: "Europe/Chisinau"
GB-EIRE: "Europe/London"
GB: "Europe/London"
GMT-0: "Etc/GMT"
GMT+0: "Etc/GMT"
GMT0: "Etc/GMT"
GREENWICH: "Etc/GMT"
HONGKONG: "Asia/Hong_Kong"
ICELAND: "Atlantic/Reykjavik"
IRAN: "Asia/Tehran"
ISRAEL: "Asia/Jerusalem"
JAMAICA: "America/Jamaica"
JAPAN: "Asia/Tokyo"
KWAJALEIN: "Pacific/Kwajalein"
LIBYA: "Africa/Tripoli"
MEXICO/BAJANORTE: "America/Tijuana"
MEXICO/BAJASUR: "America/Mazatlan"
MEXICO/GENERAL: "America/Mexico_City"
NAVAJO: "America/Denver"
NZ-CHAT: "Pacific/Chatham"
NZ: "Pacific/Auckland"
PACIFIC/JOHNSTON: "Pacific/Honolulu"
PACIFIC/PONAPE: "Pacific/Pohnpei"
PACIFIC/SAMOA: "Pacific/Pago_Pago"
PACIFIC/TRUK: "Pacific/Chuuk"
PACIFIC/YAP: "Pacific/Chuuk"
POLAND: "Europe/Warsaw"
PORTUGAL: "Europe/Lisbon"
PRC: "Asia/Shanghai"
ROC: "Asia/Taipei"
ROK: "Asia/Seoul"
SINGAPORE: "Asia/Singapore"
TURKEY: "Europe/Istanbul"
UCT: "Etc/UTC"
UNIVERSAL: "Etc/UTC"
uppercaseLinks:
US/ALASKA: "America/Anchorage"
US/ALEUTIAN: "America/Adak"
US/ARIZONA: "America/Phoenix"
US/CENTRAL: "America/Chicago"
US/EAST-INDIANA: "America/Indiana/Indianapolis"
US/EASTERN: "America/New_York"
US/HAWAII: "Pacific/Honolulu"
US/INDIANA-STARKE: "America/Indiana/Knox"
US/MICHIGAN: "America/Detroit"
US/MOUNTAIN: "America/Denver"
US/PACIFIC: "America/Los_Angeles"
US/SAMOA: "Pacific/Pago_Pago"
UTC: "Etc/UTC"
W-SU: "Europe/Moscow"
ZULU: "Etc/UTC"
I was thinking that is something about the timezone, because they changed something about this, in these last two updates... And I found on google some informations about this, but I don't understand why on my phone is working and the tablet not. I will try this as well. Thank you for your info
Thank you so much @Jpsy , could at least apply your easy temporary fix by putting the timezone to Europe/Oslo as well in HA (instead of Europe/Brussels, both are UTC+1 anyway). It now works for my Huawei Matepad Pro and my Amazon Fire HD 8 Plus which were both stuck on "Loading Data"
I think I could isolate the problem. To describe it without any clutter I created a new issue report: https://github.com/home-assistant/frontend/issues/10548
Thank you @Jpsy for your workaround. It fixed it for me as well. I'm using an older version of Safari (13.2.1 but can't upgrade it). I had no problems with it except it didn't load ESPHome section anymore since a while. But with 2021.11.0 it didn't load HA at all and got stuck on loading data. Changed timezone from Europe/Amsterdam to Europe/Oslo and problem was gone 😀
I guess it would help if you would all vote up the boilded down issue report: https://github.com/home-assistant/frontend/issues/10548 Just give a thumbs up to the first posting there. This may give an indication of how many users are affected.
Thank you very much, you solved my issue... I was struggling with it two days, now I changed my TimeZone to Europe/Oslo and everything works again :)
Have also change from Europe/Amsterdam to Europe/Oslo... worked... To bad because HA is also a Dutch product and we can't use Europe/Amsterdam hahahaha :)
My URL in FKB was : http://192.168.100.24:8123 didn't work. Changed to https://ha.mydomainname.com and this was working for me. So change of Timezone worked for my Safari 10.13 and with change of URL also for my FKB
Moved this to the frontend. Do you know what timezone is being sent by Kiosk Browser? Seems like it's not a correct one.
@balloob: The timezone is correct on Fully. But it is used for a polyfill which has a missing timezone list. See https://github.com/home-assistant/frontend/issues/10548 for a complete analysis.
Thanks, marking this as duplicate of #10548
Solved in 2021.11.2. MANY THANKS!
Yes, the actual problem has been solved.
Now I found another issue. Sometimes the HA application from the tablets it is closing by itself. I have 6 tablets in my house, I am using them as light switches and stuff, but after this 2021.11.2 update, I find that often, the application dissapear from screen and I need to reopen manually
Anybody have this problem as well?
I thought that the problem appear from the new HACS addon which I installed (Browser_Mod), but today I have uninstalled the mod and the issue still persists...
Yes, the actual problem has been solved.
Now I found another issue. Sometimes the HA application from the tablets it is closing by itself. I have 6 tablets in my house, I am using them as light switches and stuff, but after this 2021.11.2 update, I find that often, the application dissapear from screen and I need to reopen manually
Anybody have this problem as well?
I thought that the problem appear from the new HACS addon which I installed (Browser_Mod), but today I have uninstalled the mod and the issue still persists...
Don't hijack this topic for your other problem but create your own topic.
Yes, the actual problem has been solved. Now I found another issue. Sometimes the HA application from the tablets it is closing by itself. I have 6 tablets in my house, I am using them as light switches and stuff, but after this 2021.11.2 update, I find that often, the application dissapear from screen and I need to reopen manually Anybody have this problem as well? I thought that the problem appear from the new HACS addon which I installed (Browser_Mod), but today I have uninstalled the mod and the issue still persists...
Don't hijack this topic for your other problem but create your own topic.
If you didn't look, it is my own topic as well 🥇
No I didn't look that is my bad but you shouldn't consolidate issues into one topic imho. 🙏🏻
The problem
Hi!
After I updated to core-2021.11.0, the android application Home Assistant, it is not working anymore. When I open the android app, it got stuck on "Loading Data". The only workaround is to restart Home Assistant Server but keep the android app running with "Loading Data". After the server has started, the android app will work as well, till I close the app and reopen... Everytime I open the android app, I must restart server to make it works. On my phone there is no such problem, only on my Huawei T10s tablets.
What version of Home Assistant Core has the issue?
core-2021.11.0 & core-2021.11.1
What was the last working version of Home Assistant Core?
core-2021.10.7
What type of installation are you running?
Home Assistant OS
Integration causing the issue
-
Link to integration documentation on our website
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response