v2.13.1 - Invalid password and disappearing device names after install

[jurriaan]

Describe the bug

Tried to switch to v2.13.1 but I run into a few issues.

In the GUI all device names are gone (I see 0xABCD hex names instead of the actual device names) but lines start to appear between the coordinator and routers, so it seems that there is some sort of connectivity (the logs also indicated this).

Also tried to login to Phoscon, but Phoscon reported incorrect password (and does show a different generic icon), so I couldn't log in.

Switching back to v2.12.6 both issues are gone.

Did something change relating to configuration storage that can cause this issue?

Steps to reproduce the behavior

1. Make backup
2. Install v2.13.1
3. Observe issue
4. Install v2.12.6
5. Observe that issue is gone and all devices have names again

Expected behavior

deCONZ continues functioning with all device names kept and password authentication on Phoscon working.

Screenshots

Environment

• Host system: PC
• Running method: 'Ubuntu' (installed the .deb package)
• Firmware version: (26700700)
• deCONZ version: (2.13.1)
• Device: ConBee II
• Do you use an USB extension cable: yes
• Is there any other USB or serial devices connected to the host system? no

deCONZ Logs

No weird errors in logs, and it seems to connect fine to the devices. Can provide more details (logs and screenshots) if requested (but won't share all details publicly).

Additional context

Mixture of all sorts of routers and devices (Xiaomi / IKEA / INNR / Bitron)

[Smanar]

Hello, it strange, It seem the database is not used (0xXXXX name and no password).
You can run the v2.13.1 with logs enabled ?

[jurriaan]

@Smanar I've compared the logs between 2.12 and 2.13

Indeed, the DB seems not to be used!

In 2.13 there is no single log entry with the word DB or a SQL query. Even the line DB sqlite version 3.36.0 is not emitted in deCONZ 2.13

[jurriaan]

Did some extra investigations using strace, and it seems like sqlite is loaded, and even zll.db is read on v2.13. however the logs don't seem to indicate this. 🤷

[Mimiix]

Hi there

As this is not a bug report as mentioned in #5113 I am closing this issue.

Please use the forums

Kind regards,
Dennis

[jurriaan]

@manup Why isn't this considered a bug report? The latest beta (v2.13.1) doesn't work since it doesn't load the configuration from zll.db on my system. If there's anything I can do to debug the issue please let me know.

[Mimiix]

I think you meant to tag me.

The bug report is not a bug report because it's only about your system and not anything global.

[manup]

Could you please send me the zll.db file for investigation to [email protected]

I have not seen this issue yet (multiple installations and platforms). But since 2.13.x contains heaps of new code,
it seems the database code bails out at a specific location depending on the contents of the database.

[Mimiix]

Please continue the discussion on the forums.

[jurriaan]

For future reference/so that other people know how this can be fixed: just figured out that this was indeed an issue that I caused myself, I thought I installed libQt5Qml.so, but I didn't do that properly. That causes deCONZ to enter this state (where it still loads but is partially functional) since libde_rest_plugin.so cannot be loaded properly.

@Mimiix I'm very sorry for wasting your time on this issue! :)

[Mimiix]

@jurriaan As a community member, you never waste my time :)

Don't worry about it. All that matters is that the issue is resolved!