There is also the device create option Image to select an existing icon already in the database. So if the user wants to set a different icon at creation than the default this could be implemented in MQTTmapper. He should the do the getcustomiconset api call first to find the correct icon number to ...

For device options you should look at wiki page https://wiki.domoticz.com/Developing_a_Python_plugin

You see in python plugins that the plugin author sets a specific own custom created icon that is attached to one ore more of the plugin managed devices. So if the custom icon zip file is attached to the MQTTmapper plugin one could create some config option to add that custom icon to a MQTTmapper ...

Less than 40 euros for 10 zigbee relay switches https://a.aliexpress.com/_Ewqz9Aw and then 1 coördinator for 30 with the option to safely use all kind of other devices...
And no need to flash to some kind of firmware. So plugin and play.

Ah, OK, I did not read carefully and did not understand it was about the change in the config section in a plugin. But I think it is better to have pipiche, as a plugin author, report the issue. Perhaps it is related to the type of change and perhaps he did something wrong. He better make it ...

The zigbee4domoticz gui on port 9440 also has a restart plugin option.
Are you running Domoticz beta or Stable as in beta something has changed in stopping plugins. So perhaps this has te be taken into account.

This is probably related to the plugin and not a general issue. So I move this the zigbee section.

I also use this plugin have no issues here with updating.

And this is the list of all Domoticz compatible (and cheaper than Zwave) Zigbee devices https://zigbee.blakadder.com/

For a kWh, general device there is no Watt attribute, there is a actualWatt attribute. See the wiki for the proper attributes per device https://wiki.domoticz.com/DzVents:_next_generation_Lua_scripting The script probably should shown errors in the log as "domoticz.devices("kWh Delivery L3 ...

I think gizmocuz thought it was a Domoticz source files issue and not a Dashticz issue.
I think you should do the following for Dashticz to get over this issue:

Perhaps you have a python, php or batch script running that connects to Netatmo outside of Domoticz?

If there is an old entry of the Zigate plugin in the database there also should be an entry visible in the Setup-Hardware page. You should delete that. You say there is no active Zigate plugin on that page, but is there an inactive plugin visible? Else you have to go into the database (domoticz.db ...

There is no reference in the Domoticz code to netatmo.net:
https://github.com/domoticz/domoticz/bl ... etatmo.cpp

Good to hear!
Perhaps try to switch to zigbee for your 433 devices, more reliable, like Zwave and same security. Wifi devices are less secure (in my opinion), not mesh and more power consumption. Those Sonoff devices are normally also in zigbee version available.

just for the record, the bug or behavior is also discussed in this github issue https://github.com/domoticz/domoticz/issues/6194 And just a quote from @pipiche, plugin author of the Zigbee4Domoticz plugin I'm wondering if the error is not in the (python plugin) code device1 = Domoticz.Device(Name ...

And everything still works as expected?
I changed the wiki on the replace/move wording.

From the wiki https://wiki.domoticz.com/Managing_Devices#Replace_device press the Edit button on the Old device, select replace and select the new Device. (In this case the devices called ‘New UV Meter’). Next press OK. Result: The old and new device will be merged and get the name and IDX of the old ...

I dont know, but probably yes.

I understand for test purposes but for syncing production data you normally use 1 MQTT server in your network to connect to.

For communication between Domoticz instances in your network it is even easier is to use the out-of-the-box device sharing without MQTT....

Having 2 mqtt servers in your network seems a little bit strange... Better have them to write to different topics (like the examples you have given domoticz-master/out and domoticz-slave/out)