I already used {'EnergyMeterMode': '1'} or {'EnergyMeterMode': '0'} so already defined it as string and still encountered the problem. As already mentioned, the problem is not in creating the device. Creation works and also the device looks exactly like other "computed" kWh devices (created via the ...

Carefully reviewing your conf file, you're using the same MQTT server for both client and slave. It's possible to set Domoticz up like this BUT you have to differentiate both instances, for example naming one domoticz-master and the other domoticz-slave (giving domoticz-master/out and domoticz ...

In the meantime I can confirm that if I switch off the "MQTT Client Gateway with LAN interface" on the slave, then the feeding of slave electricity and slave gas meter values onto the slave temperature devices stops, while the feeding of master temperature devices onto slave temperature devices ...

Could you try to install (and setup properly) "MQTT Client Gateway with LAN interface"? On both machines. FYI, it manages 'domoticz/in" and "domoticz/out" topics, which are used by Mqtt Sync plugin. It's generally installed on Domoticz, so I didn't mention it into Mqtt Sync README, but I should do ...

Sorry not seeing it in previous... It seems that nothing is sent on domoticz/out. Did you install "MQTT Client Gateway with LAN interface" on both machines? No I did not install "MQTT Client Gateway with LAN interface" but I installed "MQTT sync with network interface". I did an additional test ...

Having a copy of your configuration file (with personal data replaced by xxx or ***) may help. it is in my earlier message here https://forum.domoticz.com/viewtopic.php?p=327128#p327128 If my config file would be wrong then it would not work on startup either I think. Additional thought: Could it ...

I tried to understand the code and the source of the problem. I could not really determine what the trigger would be for the master to send an update of values. Would it be on the heartbeat or would it be on the update of a value of a device? I am not sure whether the plugins registers anywhere ...

I was cheering a bit too early... It now seems that the synchronisation only occurs once. If I restart the master, either with a reboot, or a domoticz restart, or a plugin restart (either disable/enable or update the logging) then the values are arriving at the slave without problems, but only once ...

Just to share my experience here. It worked on the first try !! What I did: 1) Install a new Raspberry Pi with Domoticz and two 1-wire temperature sensors. This one is the master, i.e. data provider. 2) Install Mosquitto broker on this system. 3) Install the plugin and add it into the Domoticz ...

I just wrote a new Python plugin synchronizing a master (local) instance of Domoticz to a slave (remote) one at https://github.com/FlyingDomotic/domoticz-mqtt-sync-plugin You just have to get list of IDX (or names) of devices you want to synchronize on master, and that's it. Everything is ...

First try directly updating the device with a browser. In that way you can eliminate an issue with the device itself. Use the following command http://domoticzIP:port/type=command&param=udevice&idx=IDX&nvalue=0&svalue="yourText" Of course replace DomoticzIP:port, IDX and yourText with the relevant ...

The first version of the Domoticz plugin for the Intergas Xtend heatpump is now available at github at the following link: https://github.com/WillemD61/XTEND-plugin It will create 52 Domoticz devices and collect data from the Xtend and store it on the Domoticz devices. For more info, see the readme ...

I found a workaround 1) First I create the kWh device using the plugin with the default "from device" setting (leave the options field empty when creating the device). 2) Immediately after creation, I update the device svalue to "0;0" using the plugin. 3) and then immediately I update the options ...

I think I found where the problem is. It is in line 5371-5397 in the SQLhelper.cpp file. If the initial svalue does not consists of two elements then it just restores the initial value. So if the initial value is empty (which it always is after the device is created) then the svalue remains empty ...

More info: also updating the device with a JSON statement does not work when there is no initial svalue present.
So the only workaround now is to add a svalue in the devicestatus table first directly in the dbase.

Note there is no problem updating other device types, only the computed kwh device.

I found that if you put an initial svalue on the device (with sqlite3, directly on the devicestatus table) then after that the update code works correctly. So it is a bug when the device is created. It should initialize it with an initial svalue. Or alternatively the update statement should work ...

I see an issue 6194 on Github which https://github.com/domoticz/domoticz/issues/6194 also describes the problem, although the description states that the device cannot be created. I can create the device I just cannot populate it with data. There does not seem to be any action or solution to that ...

Below is a small piece of code from a Python Plugin that I am developing using the DomoticzEx framework. After each piece of code I have pasted the log output. It all seems to work fine except for the final update. You can see the sValue is not updated onto the device. sValue remains ''" instead of ...

Just to inform you that I am going to develop a plugin myself instead of doing this via DzVents. It will probably take a few weeks. This is my first plugin from scratch, using the templates and examples available. The plugin will include more or less the same data as available on the Intergas Xtend ...

For anyone installing an Intergas Xtend heatpump with or without Intergas Gateway. It is possible to communicate to the Gateway by chosing the Intergas Gateway from the Domoticz hardware list. See this thread https://forum.domoticz.com/viewtopic.php?f=38&t=7745 for more info on this setup. This will ...