Ha, the access key was stored in plain text in the database :) Repo should be up to date, updated 3 minutes ago. But probably something was wrong with the cron job as the previous commit was from May 13th. I will probably not be visiting this forum often anymore. For any tips on Pass2PHP search me ...

I guess so
Still some work to do but 98% is operational.
Mostly need to move my Xiaomi bridge, if I can figure out the access key.

As of now my Github repo pass2php is no longer compatible with Domoticz. It's rewritten to suit Home Assistant MQTT Statestream.
If you still like to use it, as example or anything, you'll have to browse the history to a date before today.

Do you mean in a Proxmox backup?
That's called STOP mode. The schedule and mode are set at Datacenter --> Backup

I think you first need to ask yourself if it's all worth it? I mean, do you have that many failures to set up a redundant system? I worked with Windows print servers in cluster and that was just a pain to manage. I am also running Domoticz in a Proxmox CT and never had an issue since. In case of a ...

I also have this problem on all Windows, MacOS and iOS devices that I have access to. So I don't believe it's a 'clear caching' thing.

It also happens when logged in...

You sure? If I open a private window I still get the snow. Used a private window because that's disabled in my profile.

What browser are you using?
Just tested in Chrome 131 on MacOS 15.2 in a private window and I could login normally.

I see the same issue in Chrome and Safari on MacOS and Chrome, Firefox and Edge on Windows. Each test was done in a private browsing window.

/var/log should be easy to clean.
And I suppose /var/cache/apt with "apt clean".

I'm running Domoticz without Docker on Debian in a Proxmox CT. Runs perfectly. No hassle at all to restore a backup if needed. Because CT uses a LXC container there's practically no overhead at all. Am I right in thinking that you are running the docker containers in Proxmox without using a VM ? I ...

I'm running Domoticz without Docker on Debian in a Proxmox CT. Runs perfectly. No hassle at all to restore a backup if needed.
Because CT uses a LXC container there's practically no overhead at all.

I find it quite annoying to have to wait a few seconds for the forum to open. Because of this I come less online here.

Use the developer tools of your browser... http://192.168.2.2:8080/json.htm?type=command&param=system_reboot This is a script I run on the domoticz server itself: DOMOTICZ=`curl -s --connect-timeout 2 --max-time 5 "http://127.0.0.1:8080/json.htm?type=command&param=getdevices&rid=1"` STATUS=`echo ...

Why not just use apis that work with lat/lon? Would be a lot easier.

I use several weather services and calculate average of them. These are all based on latitude/longtitude: https://api.openweathermap.org/data/3.0/onecall?lat=50.9929&lon=3.2112&exclude=minutely,daily,alerts&units=metric&appid=APPID https://api.weatherapi.com/v1/current.json?q=50.9929,3.2112&key=KEY ...

I already guessed it would be the recorder. I disabled default config to disable history and recorder completely. Still 3GB written each day

sincze wrote: ↑Monday 26 February 2024 13:51 creates a 30GB DB in 10 days... (because I forwarded some devices to domoticz to it...) it is crazy.

Did you find anything to limit the db size? I'm searching for avoiding disk writes but can't get it lower than 3GB/day for hass. My domoticz server only writes 200MB/day.

Aha, was truly simple to have it al in mqtt, just had to add the binary_sensor line.