Web interface won't load

Using Zynthian
,
23

Update. After working through the command line user guide to try and fix a Wiring error (setting it to MINI_V2), it fixed that, which was preventing start up, also the touch on the touchscreen that wasn’t working since rebuild, and now (venv) appears at command line too, so not really sure what happened there, but maybe some bits weren’t firing up before. Now the touchscreen is plugged in again, the delay in the web interface load is back - here’s the journalctl output at the time

Mar 04 18:30:29 zynthian zynthian_webconf.sh[896]: DEBUG:root:Loaded engine config with timestamp: 1741090293.9082677
Mar 04 18:32:24 zynthian zynthian_webconf.sh[896]: DEBUG:root:Build info => Timestamp: 2024-10-02
Mar 04 18:32:24 zynthian zynthian_webconf.sh[896]: DEBUG:root:LV2 presets => 27
Mar 04 18:32:24 zynthian zynthian_webconf.sh[896]: DEBUG:root:Pianoteq presets => 0
Mar 04 18:32:24 zynthian zynthian_webconf.sh[896]: DEBUG:root:Puredata presets => 0
Mar 04 18:32:24 zynthian zynthian_webconf.sh[896]: DEBUG:root:ZynAddSubFX presets => 0
Mar 04 18:32:24 zynthian zynthian_webconf.sh[896]: INFO:tornado.access:200 GET / (fe80::cbc:19d8:746c:8fed) 115024.23ms
(venv) root@zynthian:~#

24

Back in March I gave up on trying to fix this issue with no further input to explore. But I just installed a new image, with oram-2511.3, and still have this problem - sometimes the web ui is slow to open, sometimes it won’t load at all. Just now it was slow, but then loaded. The log shows

Jan 21 11:11:34 zynthian zynthian_webconf.sh[911]: INFO:tornado.access:200 GET / (192.168.1.130) 114974.40ms

Jan 21 11:11:34 zynthian zynthian_webconf.sh[911]: DEBUG:root:Loaded engine config with timestamp: 1768924112.4967508

Jan 21 11:11:34 zynthian zynthian_webconf.sh[911]: INFO:tornado.access:302 GET / (192.168.1.130) 36.09ms

Jan 21 11:11:34 zynthian zynthian_webconf.sh[911]: INFO:tornado.access:200 GET /login?next=%2F (192.168.1.130) 1.98ms,

any clues on why there might be a 2 min wait - is something else locking it out for which it needs to wait?

25

I just had another run at this web gui delay issue, with a bit of 'Claude vibe support’. It seems to have fixed it. Here’s what happened. It diagnosed that the gui wasn’t loading (or was taking ages) because “every time the dashboard loads, it’s running 4 separate find commands across your entire preset directory structure.”

it instructed me to edit /zynthian/zynthian-webconf/lib/dashboard_handler.py and comment out this line

‘value’: str(self.get_num_of_presets(os.environ.get(‘ZYNTHIAN_MY_DATA_DIR’)+“/presets”)),

and then it found a problem with i2cdetect so told me to comment out most of this function in the file too, so the resulting cut down function is simply

def get_i2c_chips():
return []

This seems to have worked as the web gui is loading and running quickly for the first time ever. I asked it what the consequences of the change were and it advised…

The actual problem was that i2cdetect was hanging—it was taking 2+ minutes to run every time the dashboard loaded. This suggests:

  • Your I2C bus might be unresponsive or have a faulty device

  • Or the i2cdetect command itself is broken on your system

Any thoughts from the wise ones of zynthian here?

update: curious, I uncommented the preset line so it’s back in, then rebooted, and it still works, so it seems to be only the i2c issue.

1 Like