Zigbee2mqtt stuck on loading screen

Jonas_Eriksson · December 4, 2021, 9:31pm

Hey, been trying to get Z2Mqtt to work on a fresh HA supervisor install but I get stuck on loading screen all the time, been trying with 3 fresh installs of everything. Cant find any faults in any of the logs, neither HA, Z2Mqtt nor Mqtt broker. I followed the steps of https://www.youtube.com/watch?v=-YeObwEZqL4&ab_channel=HomeSight yet I’m stuck. Config is as:

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  user: mqtt_user
  password: *****
serial:
  port: /dev/ttyACM0
  adapter: deconz
advanced:
  log_level: warn
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental:
  new_api: true
availability: false
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: '-d -d'
  log: false

Log:
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] socat.sh: executing…
[21:49:46] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing…
[21:49:47] INFO: MQTT available, fetching server detail …
[21:49:47] INFO: MQTT server settings not configured, trying to auto-discovering …
[21:49:48] INFO: Configuring ‘mqtt://core-mosquitto:1883’ mqtt server
[21:49:48] INFO: Previous config file found, checking backup
[21:49:48] INFO: Creating backup config in ‘/config/zigbee2mqtt/.configuration.yaml.bk’
[21:49:48] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks …
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[21:49:49] INFO: Handing over control to Zigbee2mqtt Core …

[email protected] start
node index.js
CREATED DECONZ ADAPTER
Zigbee2MQTT:warn 2021-12-04 21:49:57: Using experimental new availability feature

Any idea where I can find a soulution? I’ve tried googling my issue with no luck.

Oh also my setup is RPI4, SSD on USB, conbee 2 stick with latest flash.
Had this work a month ago on a SD card but that broke so had to do a fresh install since I forgot my backup password.

Dixey · December 4, 2021, 10:01pm

What version are you on? I ask because yesterday I upgraded to 2021.12 and all my Zigbee stuff hung, (and so did my Alexa addon). Thinking it was just me… I downgraded to 2021.11, had everything running proper then tried upgrading again. Same issue… it wasn’t just me.
I am now dumb, fat and happy sticking with 2021.11 until this gets resolved.

francisp · December 5, 2021, 9:10am

I upgraded a HA instance to 2021.12.0b0, and my Zigbee2mqtt to 1.22.1, and all kept working.

francisp · December 5, 2021, 9:26am

See here:

github.com/nurikk/zigbee2mqtt-frontend

[Bug]: Frontend loads sometimes slow

opened 10:54PM - 30 Nov 21 UTC

Bascht74

bug

### What happened? Hi, I am using the HA-Addon. I got some UI issues wh…en loading the frontend. Other people seems to have it, too: https://github.com/zigbee2mqtt/hassio-zigbee2mqtt/issues/236 I tried to see, if direct access to the port fixes that (by adding port 8099 to the add-on configuration). Here the rendering is OK, but every second time or so it takes very long to load... The following file seems to be the cause: http://homeassistant:8099/scripts/vendor.49fee1be1555be7ec8f9.js and sometimes the css files... ![image](https://user-images.githubusercontent.com/66269310/144140799-37a6d3ad-7550-45b5-bf15-8e010ae5cc38.png) If it doesn't work, a reload takes forever to load (still spinning): ![image](https://user-images.githubusercontent.com/66269310/144141130-55b705ed-db8b-48f3-8e52-afb8576e1eeb.png) ### What browsers are you seeing the problem on? Chrome ### Relevant stacktrace ```shell ? Please provide some info how to get this.. If a state.json.zip is needed, I can provide it. ``` ### Did you donwload state.json.zip? I will not attach state.json.zip

Jonas_Eriksson · December 5, 2021, 1:46pm

Coolio, not jst me with problems then, thanks for finding this!

Jonas_Eriksson · December 5, 2021, 8:29pm

Found an issue opened for this:

github.com/home-assistant/supervisor

Ingress proxy unpacks assest and work slowly

opened 08:44AM - 03 Dec 21 UTC

nurikk

bug

### Describe the issue you are experiencing Hello from zigbee2mqtt team! R…ecently many users started complaining that z2m frontend open slowly. https://github.com/zigbee2mqtt/hassio-zigbee2mqtt/issues/236 https://github.com/nurikk/zigbee2mqtt-frontend/issues/1124 After some debugging i can see that when frontend is loaded through ingress proxy, it's loaded very slowly: there are few symptoms: - Assets aren't gzip compressed - Missing caching headers - Sometimes response comes in form of headers from underlying backend as is, kind of http response parsing issue <img width="524" alt="Screenshot 2021-12-04 at 7 30 59 PM" src="https://user-images.githubusercontent.com/1525421/144707934-19f7d8dc-fc92-48c5-92b5-0ba158b32747.png"> Here're some screenshots <img width="1440" alt="Screenshot 2021-12-03 at 10 31 18 AM" src="https://user-images.githubusercontent.com/1525421/144567914-cf39d012-634b-4103-85a0-1b5abd72d8d7.png"> <img width="382" alt="Screenshot 2021-12-03 at 4 51 00 PM" src="https://user-images.githubusercontent.com/1525421/144573582-040a432e-077b-45f3-842e-5015816c13c1.png"> This how it looks if we request frontend directly, without ingress First load (no cache) <img width="1440" alt="Screenshot 2021-12-03 at 10 26 37 AM" src="https://user-images.githubusercontent.com/1525421/144572218-e85741c4-2268-4416-8d86-560b032526dd.png"> <img width="388" alt="Screenshot 2021-12-03 at 10 27 48 AM" src="https://user-images.githubusercontent.com/1525421/144572280-2492bda3-fcf0-4fff-a588-ffb73d01f14e.png"> After refresh <img width="1440" alt="Screenshot 2021-12-03 at 10 25 09 AM" src="https://user-images.githubusercontent.com/1525421/144572313-dcfbb301-6ad8-4570-85e8-8a21a7c8cf40.png"> ### What is the used version of the Supervisor? supervisor-2021.10.8 ### What type of installation are you running? Home Assistant Supervised ### Which operating system are you running on? Debian ### What is the version of your installed operating system? Ubuntu 18.04.6 LTS ### What version of Home Assistant Core is installed? core-2021.11.5 ### Steps to reproduce the issue 1. Install zigbee2mqtt addon 2. Start it 3. Open web ui ### Anything in the Supervisor logs that might be useful for us? ```txt no ``` ### Additional information [nurikodd.duckdns.org.har.zip](https://github.com/home-assistant/supervisor/files/7653833/nurikodd.duckdns.org.har.zip) Attached HAR archive from chrome dev tools

rcruikshank · December 9, 2021, 9:20am

Similar issue here. Getting “Loading, please wait” from frontend when I select “Devices” from the menu. Other frontend menu items seem to be ok?

HA version 2021.11.5
Z2M version 1.22.1-1
RPi 4 with USB SSD
ZB Coordinator based on TI CC2652P

Configuration.yml

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
serial:
  port: /dev/ttyUSB0
advanced:
  log_level: warn
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
  ikea_ota_use_test_url: true
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
availability: false
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: '-d -d'
  log: false

Log

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing... 
[19:57:24] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing... 
[19:57:25] INFO: MQTT available, fetching server detail ...
[19:57:25] INFO: MQTT server settings not configured, trying to auto-discovering ...
[19:57:26] INFO: Configuring 'mqtt://core-mosquitto:1883' mqtt server
[19:57:26] INFO: MQTT credentials not configured, trying to auto-discovering ...
[19:57:26] INFO: Configuring'addons' mqtt user
[19:57:26] INFO: Previous config file found, checking backup
[19:57:26] INFO: Creating backup config in '/config/zigbee2mqtt/.configuration.yaml.bk'
[19:57:26] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[19:57:28] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start
> node index.js
Zigbee2MQTT:warn  2021-12-09 19:57:36: Using experimental new availability feature

If I put in the new_api: true line in the config I get the following error in the HA logs:

21-12-09 19:32:15 WARNING (MainThread) [supervisor.addons.options] Unknown option 'new_api' for Zigbee2mqtt (45df7312_zigbee2mqtt)

What am I doing wrong?

Thanks in advance
Rob

francisp · December 9, 2021, 11:52am

That is not supported any more

Seems a bug in the add-on

drjjr · December 23, 2021, 3:23pm

@rcruikshank Hello, did you ever get this sorted out? Trying some experiments with zigbee2mqtt and getting the same thing: stuck on “loading, please wait”

drjjr · December 23, 2021, 3:30pm

Actually it works once a device is added.

rcruikshank · December 23, 2021, 11:48pm

@drjjr nope. Just went with ZHA.