Gizmocuz has solved the issue. No issues anymore

Updated to the last beta 2025.2 17204. No issues.

Saw already some changes in the overview and database restore screens. Is this the same project?

Created a new sd card with Trixie 64 bit lite. Installed Domoticz 2025.2 stable. Through the settingsscreen (check for updates) installed beta 2025.2 17175. No problems, during the countdown the dashboard came back normaal. No issues.

When i was building a test sd card and did some installations, release and beta, from the setting screen, there where no issues. I am not shure because did a lot of testing yesterday. Have to do that again.

Saw that Gizmocus is working on it....#6577
Edit: Updated to last beta 17163, same problem. On trixie domoticz is crashing after database restore, on Bookworm not

Did some tests with another os (Bookworm) and Domoticz versions.
Trixie + Stable 2025.2 restore database Domoticz crash, restart domoticz service
Bookworm + Stable 2025.2 restore database Domoticz online Ok
Bookworm + beta 2025.2 17163 restore database Domoticz online Ok
Bookworm + beta 2025.2 ...

Thanks.
Removed Somfy to test, problem still exist. I am on Trixie and Domoticz beta 2025.2 17198, going to test with an older os (Bullseye, Bookworm) and older Domoticz.
Am i the only one with this problem?

After a database restore Domoticz doesn't come online, no devices found or no communication...
Did a service restart, after that domoticz was running normal. Tried this with a database backup and restore (no database changes) and after a powercycle of the Rpi3B+. Seen this also on earlier versions ...

After a update from beta 17099 to 17189 Domoticz did not restart. Did the update throuh the settingsscreen. Counter counted until 100, then the message update failed, no internet connection....
After a domoticz service restart was domoticz running normaal on the downloaded beta 17189. I thought this ...

I had to do that in the past. But now i can do a normaal update via the web ui. I did the 2 last updates via the web ui without problems. Running now 7.1.027, updated from 7.1.026.
Thanks

i am seeing 2 counter jumps on 31 january and 3 february. Don't know where it's comming from. Are there others users seeing those counter jumpings, in my case only the envoy production counter?

Switched to 5.2.0. Remark: password is visible in settingsscreen, caused by a capital T in last "true".

<param field="Password" label="Password" width="200px" required="True" default="" password="True"/>

should be:

<param field="Password" label="Password" width="200px" required="True ...

Made some changes in plugin.py:

<param field="Mode2" label="Refresh interval" width="100px" default="30;900;15"/>
<param field="Mode3" label="Night Mode" width="100px" default="30;60"/>

and

# Check Mode2 and set default as empty or invalid
if not Parameters.get('Mode2') or ';' not in ...

Moved to beta 5.1.7. No issues. I can't test the creating of new devices.

I have tested the latest version 5.1.6.
For me it works without problems. Just some remarks/ questions, what is the advantage of using a config file? The only parameter that is used in that file (at this moment) is the fast polling time (temp_time). The other parameters are set in the parameters ...

I did have the same problem this morning after a Domoticz service restart. After installing Domoticz beta 2025.2 17057 was problem solved. I don't use node red.

After a service restart of Domoticz the Enphase envoy stopt communicating with Domoticz. Running stable 2025.2. Enphase software D8.3.5386. I saw this problem earlier in this forum, and switched to beta 2025.2 17057. Communication is working again. Maybe its time for a new stable?

Just for information, i am running the plugin, latest master, on Trixie, Rpi3b+, Domoticz 2025.2. No issues here.

I think you will find the new GPIO numbers in the file /sys/kernel/debug/gpio. Also i think you can find the new gpio numbers by adding 512 to your old gpio number, gpio 6 will be gpio 518