A TadoX can not be controlled with the existing Tado integration?

Also make sure you use full paths in the scripts, also in the sub-scripts. Like for example
/bin/bash /home/pi/octopi_shutdown.sh

You are free to add it....

But serious, what would it add? What devices can I control that I cannot control now with Domoticz and its gateways and python plugins?

And use this instruction to report this issue https://wiki.domoticz.com/MQTT_AD_Report_Problems

Does your system support python plugins?
Check in the menu Setup - About if python is listed.
Also check the wiki to fix it if not. https://wiki.domoticz.com/Using_Python_plugins

I use the same method as you for a kwh General Instant and counter device:: http://MY-IP:8080/json.htm?type=command&param=udevice&idx=407&nvalue=0&svalue=187721000;-368000;2025-05-31 The value will always be added to the end of the table so it depends of the sorting you use when you see it.

Check the database values. I think update here means adding a row for that date as I explained before. So not overwriting the existing value. At least that is what happens on my counter device that I maintain this way.

You are using deprecated API calls in the script.
For example
/json.htm?type=devices
will be
/json.htm?type=command&param=getdevices

See the wiki how to solve it:
https://wiki.domoticz.com/Domoticz_API/ ... and_newer)

hjzwiers wrote: ↑Friday 13 June 2025 14:53 That was very simple ... but most things are if you know where to look.

Working!

It is more that you have to understand what is happening when you use docker.....

You are running Domoticz also in a docker? Find the real IP of your Domoticz server by open up a terminal window and execute the command: ifconfig -a Then you have to change in Domoticz menu Setup - Hardware - NefitEasy hardware gateway http://127.0.0.1:3000 into http://<Domoticz Server IP>:3000

That probably depends how the docker image has been created..... Does it even work properly? In the NefitEasy wiki page https://wiki.domoticz.com/NefitEasy there is a troubleshooting part. curl http://127.0.0.1:3000/api/status It should give a valid JSON result. You can also try curl http://0.0.0.0 ...

You have to be aware you have to do this everytime you update the Domoticz Docker image!

Does it run in Docker? What does the log of the docker say?
Did you stop the normal nefit-easy server on your system?

And stop posting credentials like ID and password/PIN codes on the internet!!!!!

Then you probably have to write a persistent file yourself.

Why do you want the exact correct time in that file? As it is possibly not designed to have the exact time in that file but the UTC time. The time in that file is only needed to calculate time differences to manage the size of data fields

Please do the following:

waltervl wrote: ↑Thursday 12 June 2025 17:22 what happens if you login to the container with

Code: Select all

docker exec -it domoticz

and list the contents of folder /opt/domoticz/userdata/scripts/lua_parsers

Code: Select all

ls -l /opt/domoticz/userdata/scripts/lua_parsers

And what if you create it from within the container?

you should put it in
/opt/stacks/domoticz/config/scripts/lua_parsers/watermeter.lua

You can check what happens if you login to the container with and list the contents of folder /opt/domoticz/userdata/scripts/lua_parsers

If you are running from docker: check your volumes. You probably have to make an extra link to /opt/domoticz/userdata/scripts (but I am no docker expert....)

hjzwiers wrote: ↑Wednesday 11 June 2025 19:43 I have auto discovery installed, but its not downloading?

I see the results in the separate website, is it a setting somewhere?

Better discuss this in a new topic in the MQTT AD subforum, not here

MQTT AD subforum: viewforum.php?f=82

@hjzwiers you are not using the standard MQTT auto Discovery for zigbee2mqtt? As for that value should be a lux sensor be created.