Thanks! You saved my day. I had the same problem after trying to delete and re-include a faulty device. Ended up with several of these 'ghost' nodes. Had to borrow a Windows computer in order to run the Zensys Tools, but it worked! I wonder, however, what's the use of a z-wave control panel, if it ...

Using a device more than once (with the idx parameter) is certainly a welcome addition, but it's not very clear to me whether it applies to all kinds of blocks. I tried it quickly on a switch device and on a sensor device. For the sensor device it worked, for the switch it didn't (I got an empty ...

I use a DzVent script. It's simpler and more or less standalone (apart from the custom sensor). return { on = { timer = { 'every hour' }, httpResponses = { 'coronaRetrieved' } }, execute = function(domoticz, item) if (item.isTimer) then domoticz.openURL({ url = 'https://coronavirus-19-api.herokuapp ...

Thanks!

Can't answer your question, but how did you set up this sensor in Domoticz?

Great. I tried it and it works now.s Thanks a lot!

Something I noted when experimenting with multiple sources in one graph: They tend to be very slow in loading on Android. On MacOS and iOS there is hardly any speed loss, but on Android devices (phone and tablet) they can take up to thirty seconds to load (independent of the browser choice). While ...

Then it's correct, but it's not a real solution of course. One to have the freedom to choose the order.

And what about the beginAtZero?
Is it supposed to work for each Y axis separately (so three different settings), or is just a single value that controls all the Y axes in the same way?

I know what mean. It's just that for some reason the debug file didn't upload (maybe because I made a draft first?).
Second attempt:

This is the resulting file. Don't pay too much attention to the array value for beginAtZero. I tried a simple value as well, no change. Since not everything is documented, I sometimes use trial and error. Log file : block_49158.json.zip Block definition : blocks['outside_weather'] = { debugButton ...

In many of the graphs above and also in my own Dashticz graphs I notice the following bugs(?):
- Humidity seems to be expressed in ºC and temperature in % (which can be solved by defining them yourselves, but still)
- beginAtZero only works for one of the axes (in case of multiple axis)

I would also appreciate it if a solution would be found for external access. Configuring the external Domoticz server address in CONFIG.js is not a very elegant solution and (in my case anyway) and for some reason prevents the graphs from being displayed, both internally and externally (they seem to ...

Thanks for the explanation and suggestions! And yes, it seems it is not necessary to make the table persistent. I only plan to use it from within global_data, so local will probably do.
Looking forward to the new version, by the way.

I'm not very familiar with dzVents nor with LUA, but the recent problems with timer forced me to have a look at it. However, I've got a problem which I do not really understand. I created a table representing groups of thermostats in global_data.lua. I call the helper to set the setpoint of all ...

Problably too late, but try this:

https://blog.therzogs.com/?p=295

Thanks!

If you consider, however, that an lcd watch can permanently show time for more than two years, with a much smaller battery, I wonder whether the saving power argument is really convincing. Anyway, it's not just my configuration than.

I've got a few Devolo and one Danfoss radiator thermostat heads (LC13), with Domoticz running on a Raspberry with a Aeon Gen5 Z-wave stick. After some initial configuration problems (not all Danfoss thermometers were recognised, I had to add one by hand in the configuration file), I've got ...