Domoticz

As the OpenZwave project has stopped a long time ago the Domoticz project is promoting to use Zwave-JS-UI.

See wiki https://wiki.domoticz.com/Zwave-JS-UI

This wil probably not help you when compiling the current OpenZwave part in Domoticz.

Then you should try to update to latest beta of Domoticz as some MQTT AD improvements are implemented there.

Check for example this topic viewtopic.php?t=3673

Or this plugin https://github.com/jgaalen/domoticz-apc-ups-plugin

You probably also have to update the Meter_Calendar table too.
But yes, fixing these counter values in the database manually is a PITA. I stay away from it if I can.
Better delete the incorrect high value the next day from the month graph by shift - click on it.

What is the -l curl option? You use in your script: domoticz.openURL({ url = baseurl .. stationid, method = 'GET', callback = 'JubileeLevel', }) Perhaps you need different OpenUrl options similar as the -l? What if you remove the GET method?

What if you go into the docker container of Domoticz and do the curl command? Do you get 200 or 403 status?

If you have 3 phase grid connection you can have for example usage from grid on phase 1 and return on phase 2 or 3. It depends on the connection of your solar production and usage devices per phase. Your P1 viruell meter shows "182 Watt, -968 Watt" meaning that in total there is on some phases in ...

because this

Code: Select all

local lux = domoticz.devices(249)

should be changed into into something like

Code: Select all

local lux = domoticz.devices(249).lux

-918+182=-736

waltervl wrote: ↑Tuesday 15 April 2025 14:02 What kind of integration do you use?

at 0:00 hours Domoticz is cleaning up its database and merging data from hourly tables to daily summary table. So it could be that your system is crashing on this. Could be due to resources, diskspace, corrupt database etc. See the troubleshooting wiki for info how to troubleshoot and solve. https ...

This should work as a start return { on = { timer = { 'every 5 minutes', }, }, logging = { level = domoticz.LOG_INFO, -- Select one of LOG_DEBUG, LOG_INFO, LOG_ERROR, LOG_FORCE to override system log level marker = "Blinder" }, execute = function(domoticz, device) local lux = domoticz.devices(249 ...

Remove the logwrite function. No need for that.
Use the build in domoticz.log() function as everybody else is using.

There is a logging example template (when you create a new dzvents script) to show the way of working.

Did some AI "help" you creating this script?

clumpton wrote: ↑Wednesday 16 April 2025 10:39 I have just created an issue on Github.
https://github.com/domoticz/domoticz/issues/6309

If the topic is missing nothing Domoticz can do about this. You have to create an issue on the Zigbee2MQTT repository. Or search for similar issue there

Nothing in the logs about remote sharing?

From the wiki

Data is pushed to the Main from the Remote triggered by device changes. So if a device changes it will be synchronised.
It would be wise to check the "Setup | Log" to double check there are no errors.

If it is missing in the config topic it is a Zigbee2MQTT issue, not a Domoticz issue. You could perhaps try to update to latest beta as some things have changed in Zigbee2MQTT from 1,x to 2.x regarding device automation. And you need to be on latest Domoticz beta to use this new functionality ...

Is zigbee2mqtt publishing a config topic for the missing device? Domoticz is creating devices based on the config topic. When you look with for example program mqtt explorer you should see config topics in the homeassistant folder in a switch or sensor subfolder/topic. See also wiki page for an ...

When using remote device sharing you have to open up the sharing port (default 6144) in the docker image configuration.

A quick search on the forum gave me this: viewtopic.php?p=311392#p311392

Just trying to understand: I dont know how your Domoticz environment is setup but the Domoticz server should always have access to MQTT Broker. It should not be depend on the user behind it. Just struggling to read through your Github issue to understand your problem. I can understand that you want ...

Search found 5290 matches

Re: OpenZWave compile error: AssociationCommandConfiguration.cpp:191:85: error: ‘this’ pointer is null

Re: Tuya ZWT198 wall thermostat, state missing from devices

Re: UPS data

Re: Database repair (utility meter totals)

Re: DzVents OpenURL response error

Re: DzVents OpenURL response error

Re: Energy Dashboard (Build in)

Re: Blinder script [Solved]

Re: Energy Dashboard (Build in)

Re: Log does not work if events do not change

Re: Domoticz crash on PC crash at 23:55 each day.

Re: Blinder script [Solved]

Re: Blinder script [Solved]

Re: Tuya ZWT198 wall thermostat, state missing from devices

Re: GPIO with docker

Re: Tuya ZWT198 wall thermostat, state missing from devices

Re: Tuya ZWT198 wall thermostat, state missing from devices

Re: GPIO with docker

Re: GPIO with docker

Re: MQTT Client ID