Since you did not install docker compose the normal way (see our wiki) and using snaps? This indeed complicate things You could make a bash script that you can execute in a docker compose folder to update it. Very easy this way And as mentioned, if you don't miss anything, keep it running and don't ...

Yes, you need to update at least every 60 seconds if your sensor timeout is 60 seconds.

The Daiken AC you should be able to control with the build in Daiken hardware?

Thanks for the feedback!

I assume you installed this with docker compose?
If yes, you can update (if you need to...) when you go to the docker compose folder (for example /opt/zwavejs) and issue the below command:

docker compose pull && docker compose up --force-recreate --build -d && docker image prune -f

Did you use 116687 kWh for that day? Is this correct? or should it have been 116.xx kWh ? If that is the case, your kWh value is not correct.

This is with the normal Raspbian image (without the desktop) ?

Could you try with the docker compose Domoticz?

I added some logging (and catching the error) in beta 16360 if (sd2[0].empty()) { _log.Log(LOG_ERROR, "Empty Value in Meter table for device idx: '%q'", sd[0].c_str()); continue; } if (!is_number(sValue)) { _log.Log(LOG_ERROR, "Invalid Number sValue: '%q' for device idx: '%q'", sValue.c_str(), sd[0 ...

Or when you updated Domoticz, you should have a backup in your backups folder.
Both ways, yes, you need to perform some database actions

Shortlog values are stored every 5 minutes by default.
What value did you enter in the settings page (Other) for Sensor Timeout? (Is this still the default value of 60?)

Is both your OS and your raspberry pi date+time correct?
(For instance, Windows And your raspberry pi date/time)

Could you try with beta 16356? I enabled the device_automation and it seems to work. But you will probably get net devices. On your old device, press Edit, and then select 'Replace' and select the new device. With this, all id's stay the same including the original (old) name (If you are using it in ...

I just noticed I did not restart my Domoticz instance and therefor the old configuration was still being used At the moment the component type 'device_automation' is disabled, you can see this at the top of the MQTTAutoDiscovery.cpp file One thing I noticed, my 4 gang zigbee switch now only gets 3 ...

@Arjan2019, are you able to test this against the latest beta version of Domoticz? I think it should still work with all the recent changes. There should of course be no need for a script for each device, if it is not working anymore, we need to adopt for the changes. I'm on the latest dev branch ...

Yep, that is the way to control it. Here I am more focused on charging the battery, but you will notice in the winter times that the cheapest time to charge your car is between 01.00am - 07.00am, and in the summer between 12.00-16.00pm I bought a cheap zigbee switch with 4 buttons, and labeled them ...

It means that we expect a number value, and it is not a number or a string Looking at the code inside the function (GetJSonDevices), you can see where 'stoll' is called For example for: pTypeRFXMeter sTypeCounterIncremental And that is basically it. So now you can search the reason what is making ...

How about you try

- "/dev/serial/by-id/usb-0658_0200-if00-port0:/dev/ttyUSB0"

And for sure you need to replace 'usb-0658_0200-if00-port0' with your real serial device that you should be able to find with

ls /dev/serial-by-id

@mpx2, throw away that temperature sensor? If it reports false values it is of no use.
If your device is to far away from the 433Mhz transceiver, try a bigger antenna

Why would you need/want to run such an old version?

Just use Domoticz (and your other services) with Docker Compose. Create separate folders for each of your projects, and use folders inside these folders as volumes ./my_folder:/opt/docker-project/folder Use a rsync job to backup the dockers folders, I install all my dockers in /opt, so I only need ...