Domoticz

flemm wrote: ↑Thursday 12 March 2020 9:50 Last night I noticed that my p1 meter has duplicate devices in the database. I'll attach an image that shows what I mean.

waaren wrote: ↑Thursday 12 March 2020 10:35 It is unlikely that your screen reflects what is in the database because the Idx is the primary key of the devicestatus table and must be unique (or null) by sqlite design.
If you already cleared cache and appcache (different things) it's time to look in your database (table devicestatus) with sqlite3 or similar tools.

manjh wrote: ↑Thursday 12 March 2020 10:38 It might be worth to do a backup and then restore. Just guessing, but it might reorganize the DB if anything is wrong in there. And it's not a big deal to try.

flemm wrote: ↑Thursday 12 March 2020 10:56 Thanks for your explanation. I already tried clearing my browser cache, that didn't make any difference. Feeling kinda dumb, but could you tell me what the app cache is, and how I should clear it?

A lot of the problems users experience after a domoticz update are gone when the browsercache and appcache (different things !) are cleared. There are also quite a number of posts on this forum related to these kind of problems.

To summarize and sorted from little effort to a bit more effort take these steps and check after each step if it address the issues you encounter.

- Try another browser. Edge, Internet Explorer, Firefox, Chrome, Brave, Opera.. They all are up to the task

- clear browser cache and appcache
Chrome: chrome://appcache-internals/#
Firefox: https://support.mozilla.org/en-US/kb/storage

- in www/js look for domoticz.js.gz, if its there remove it, (KEEP domoticz.js !! )
- use incognito mode using
Chrome [control] [shift] n
Firefox: [control] [shift] p

- restart domoticz
- rename the location of the original installation and install the new version to an empty target directory. Next copy database and scripts from the old location and fire it up.


Hope this will also solve your problem.

waaren wrote: ↑Thursday 12 March 2020 11:03 I posted below already a couple of times on the forum....

flemm wrote: ↑Thursday 12 March 2020 11:38
The devices table somehow mixes up devices and groups. I had a few groups of switches. When the table with devices loaded, the devices and groups were shown correctly. But after a few seconds, the groups change into the P1 devices. After I deleted the groups, the duplicates were gone.

So, the group IDX's conflict with the devices IDX's. Are these supposed to be 'different' indexes and therefore to be able to exist alongside each other? Or is the error in the fact that a new group gets an IDX that already exists? When I create a new group, it automatically gets IDX 1, which is already in use, and I don't see the option to change that.

After IDX 1-5 I had a gap until 22. So I fixed it by creating groups until they reached IDX 6. Not the answer to the issue, but it works.

flemm wrote: ↑Thursday 12 March 2020 17:45 Since screenshots might not be clear enough, here's a screen recording of what happens: https://www.dropbox.com/s/iil32kvvtzxyj ... s.mov?dl=0. Hope that makes it more clear. As you can see, after a few seconds, the groups with 'conflicting' numbers, are replaced by duplicates of the P1 electricity devices. I hope you understand my confusion earlier today..

flemm wrote: ↑Friday 13 March 2020 8:54 I didn't realise it happened when the devices were updated. And indeed, my P1 meter is updated every 5 seconds. I've checked, and you're right! With a group with IDX 22, same number as one of my Hue bridge devices, changes to 'Hue Bridge' when the Hue is updated. So it isn't related to my P1 after all.

waaren wrote: ↑Friday 13 March 2020 22:37 Issue has been picked up and a PR is created. Fix will be in one of the next Beta's