Error opening url: http://127.0.0.1:8080/json.htm?type=graph&sensor=counter&range=month&idx=305 Topic is solved

[waltervl]

Are there perhaps already again new hdd devices available that are updated? The replace function should have managed that already with the previous merge. So it is strange it stopped working now suddenly.

[Copitano]

Are there perhaps already again new hdd devices available that are updated? The replace function should have managed that already with the previous merge. So it is strange it stopped working now suddenly.

I rechecked the device list. And yes, new devices have been created. I activated (green to bleu arrow) them, but the new one only has a limited history. However, the old device, which is no longer being updated, still has the full history back to 2020. Should I perhaps do the merge the other way around? So, select "replace" in the new device and then point to the old device?

[waltervl]

Here is the correct order described https://wiki.domoticz.com/Managing_Devi ... ace_device

If it again failed it could be you ran into a bug.

[Copitano]

Here is the correct order described https://wiki.domoticz.com/Managing_Devi ... ace_device

If it again failed it could be you ran into a bug.

That's exactly the instruction I followed earlier. I've done it again now. The newly created device disappears. The old one seems to remain as it was and isn't being updated in any case. However, new devices are being created in the device list again, with another green arrow. I also updated under Hardwaretab.
Is it a bug then?

[waltervl]

Seems so, perhaps create a GitHub issue with logging and screenshots describing the situation.

[Copitano]

Seems so, perhaps create a GitHub issue with logging and screenshots describing the situation.

Okay, I Will. Thanks again.

[gizmocuz]

This has been noticed recently before. It is the way the devices are created (poked directly into the database)
I am afraid this can not be changed easily without modifying the code.

Is it that big of a problem you loose your history of your harddisk fullness ?

[Copitano]

This has been noticed recently before. It is the way the devices are created (poked directly into the database)
I am afraid this can not be changed easily without modifying the code.

Is it that big of a problem you loose your history of your harddisk fullness ?

No, not a disaster. It is a shame, though, that all the devices also get different IDX numbers. This means modifying scripts that use them, and forwarding them to Grafana becomes a bit messy. However, in my case, this only applies to the USBbackup. That's a relatively small, mounted USB drive that reaches 100% every 10 days and needs to be wiped clean except for the last day (I'm considering to replace it with a larger one when I have a little time) .

[gizmocuz]

I know, unfortunately I am not the author of the changes and have mentioned this during his development.
The good news is that now more disks are detected