Closed artur3 closed 2 years ago
same here, web gui is VERY slow, especially initially it takes ages to load the online/offline status of devices. using chrome and edge here. ~80 devices.
Same on Windows using latest Chrome. With >100 devices, the UI sometimes does not even load at all, but only shows a spinning tab icon.
Hi, try to switch to the latest dev branch
https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html#switch-to-the-dev-branch
ld be, shared with other programs. Dividing up the shared memory between all the processes sha
Hi!
Can you attach complete state.json file from Settings -> Tools -> Download state
?
Firefox: state.json.zip
Chromium (after few minutes of waiting): state.json.zip
Can you test on latest dev branch?
https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html#switch-to-the-dev-branch
After update to dev, devices page loaded almost instantly in Firefox. Chromium shows empty page.
I installed the 1.22.1-1 version couple of days ago as home assistant addon and also got the 'Loading, please wait' screen (from Chrome). Just installed the dev version and now I do get a proper page but no devices are shown either, like @artur3. Just started with zigbee2mqtt, never had any devices before in there, so I dont know if the problem of the empty page is because the only zigbee device that I have connected to my usb stick (motion detector) is not recognized by zigbee2mqtt or that it is another problem (the device does work with zha)
After update to dev, devices page loaded almost instantly in Firefox. Chromium shows empty page.
Can you check chromium dev tools logs?
runtime.3296ac9a5caef629c7d6.js:1 Failed to load resource: the server responded with a status of 404 (Not Found) 192.168.x.x/:1 Refused to apply style from 'http://192.168.x.x:8081/main.7379448ff31d4e2a65b8.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled. vendor.49fee1be1555be7ec8f9.js:1 Failed to load resource: the server responded with a status of 404 (Not Found) main.03d2b8de8a4207f907b0.js:1 Failed to load resource: the server responded with a status of 404 (Not Found) 192.168.x.x/:1 Refused to apply style from 'http://192.168.x.x:8081/main.7379448ff31d4e2a65b8.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled. DevTools failed to load source map: Could not load content for http://192.168.x.x:8081/scripts/vendor.109be7bda8112bf971cc.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
I tried on another computer and it loaded in Chromium. Visibly slower than in Firefox, first only text and then rearranged it with graphic. Devices status loaded quickly.
Report from tool called Lighthouse: 192.zigbee2mqttUI_8081-20211215T165519.zip
Now page loads but without devices.
I have the same issue "loading please wait". I have latest version installed on TrueNAS Core (FreeBSD) jail. After restarting the jail, sometimes need to do it twice, it would work for a while before again failing to load "devices" and "dashboard" pages.
Any news on this? Tried it today again with another zigbee device (power plug), but same issue, normal version gives 'loading, please wait', edge version gives empty device list. Both devices work in zha.
This issue already resolved in dev branch, tomorrow happens scheduled release. Happy new year
After update to 1.22.1 web UI loads very slowly in Firefox and if tab Devices is left open for longer time (just few minutes) all RAM memory will be taken and system (openSUSE) becomes too slow to take any action.
This happens every time When web UI is opened in Firefox on all my computers.
For some reason web UI won't fully load in Chromium, only top menus and "loading please wait".
zigbee2mqtt works fine all the time.
zigbee2mqtt on Debian 10 npm -v 7.16.0
KDE process monitor:
Process 2101 - Web
Summary
The process Web (with pid 2101) is using approximately 4.9 GB of memory.It is using 4.9 GB privately, and a further 11.3 MB that is, or could be, shared with other programs.
Dividing up the shared memory between all the processes sharing that memory we get a reduced shared memory usage of 2.4 MB. Adding that to the private usage, we get the above mentioned total memory footprint of 4.9 GB.
10.2 MB is swapped out to disk, probably due to a low amount of available memory left.
Library Usage
The memory usage of a process is found by adding up the memory usage of each of its libraries, plus the process's own heap, stack and any other mappings, plus the stack of its 21 threads.Full Details
Both the MMU page size and the kernel page size are 4 KB.