hassio-zigbee2mqtt: Home Assistant frontend not working on 1.25.1

Hi,

after updating to 1.25.1 is frontend on Home Assistant not availible but z2m works behind. Rolling back to 1.25.0-1 seems fine . Im running HA on RPi 4 with the prebuild Image.

Frontend-Version: 20220405.0 - latest

System Health

version	core-2022.4.7
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.9.9
os_name	Linux
os_version	5.10.103-v8
arch	aarch64
timezone	Europe/Berlin

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 7.6
update_channel	stable
supervisor_version	supervisor-2022.04.0
docker_version	20.10.9
disk_total	58.9 GB
disk_used	4.6 GB
healthy	true
supported	true
board	rpi4-64
supervisor_api	ok
version_api	ok
installed_addons	eWeLink Smart Home (1.2.4), File editor (5.3.3), Mosquitto broker (6.0.2), Terminal & SSH (9.3.0), Zigbee2mqtt (1.25.1-1)

Dashboards

dashboards	2
resources	0
views	1
mode	storage

My /config/zigbee2mqtt/configuration.yaml

homeassistant: true mqtt: server: mqtt://core-mosquitto:1883 user: addons #password:******** keepalive: 60 reject_unauthorized: true version: 4 serial: port: tcp://192.168.178.23:8888 adapter: ezsp baudrate: 115200 rtscts: true frontend: port: 8099 permit_join: true devices: '0x847127fffedd1a9d': friendly_name: '0x847127fffedd1a9d' '0xcc86ecfffe951311': friendly_name: '0xcc86ecfffe951311' '0xcc86ecfffe9550ba': friendly_name: '0xcc86ecfffe9550ba' '0x00158d0002ffeaa3': friendly_name: 0x00158d0002ffeaa3 Tint Remote legacy: false '0x804b50fffe052b4e': friendly_name: '0x804b50fffe052b4e' advanced: log_syslog: app_name: Zigbee2MQTT eol: /n host: localhost localhost: localhost path: /dev/log pid: process.pid port: 123 protocol: tcp4 type: '5424' channel: 15 network_key: ******* groups: {}

Any Ideas ?

Best Regards

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 10
Comments: 27 (1 by maintainers)

Most upvoted comments

Android by uninstalling and re-installing the Home Assistant app

Just go into app settings and clear the cache, no need to uninstall.

marcbritten on May 2, 2022

Same issue here. Seems to be a web-packaging problem as the following resources are no longer found:
<script defer="defer" src="scripts/vendor.f3635c6dc09aacfa6bae.js"></script>
<script defer="defer" src="main.e47e35f1394ea10dd81d.js"></script>
The rest of the resources are loaded except those two, preventing the frontend app from running properly.

Yup, my browser console throws up a 404 error for these 2 files.

EDIT: Fixed by emptying caches on Safari. (Develop -> Empty Caches) EDIT2: Resetting frontend cache on the HA iOS app fixes the problem also.

JudahBella on May 2, 2022

Fixed for me (Chrome) by opening dev tools, right clicking on the reload button, and selecting “Empty Cache and Hard Reload”

ScottG489 on May 2, 2022

Could this be some caching problem? (CC: @nurikk) Does a CTRL+F5 fix it?

no, I try to clear chache, but doesn’t fix it. I try also to restart HA OS , but nothing: The Z2M add-on seems working in background , but the GUI is missing 😦

ippo112 on May 2, 2022

workaround: uninstall and install again.

snowyu on May 2, 2022

I have the same problem. I restored 1.25.0.1 from backup last night and tried again this morning with no success.

Fixed by clearing cache on Chrome and on android App

pblanar on May 3, 2022

I managed to get the frontend to show in Chrome by using Developer Tools -> Network -> Disable cache

Lynetk on May 2, 2022