It should be implemented in latest beta, at least for a generic thermostat device. Can you check with your Nest? Sorry, i've been busy with other things than my dashboard lately, so my reply is a little late. Still use my dash daily though, and yes, it works like a charm. Thanks for implementhing ...

That's awesome. I've installed the update, cleared everything and it works like a charm. Thanks so much!

Thanks for your reply. I didn't realise it happened when the devices were updated. And indeed, my P1 meter is updated every 5 seconds. I've checked, and you're right! With a group with IDX 22, same number as one of my Hue bridge devices, changes to 'Hue Bridge' when the Hue is updated. So it isn't ...

Thanks a lot for your explanation. I suspected groups have 'different' IDX's and can therefore have the same number as another device. I create a new group by going to 'Scenes' and clicking 'Add scene' and selecting 'Group'. I'm unaware of any other way to do that.. I've tested a little further ...

I've found the issue, sort of. It didn't have anything to do with caching or something like that. The devices table somehow mixes up devices and groups. I had a few groups of switches. When the table with devices loaded, the devices and groups were shown correctly. But after a few seconds, the ...

waaren wrote: ↑Thursday 12 March 2020 11:03 I posted below already a couple of times on the forum....

Sorry, In my excitement and eagerness to learn more I asked, while I should have searched for it. Thanks a lot, i'll give it a try!

It is unlikely that your screen reflects what is in the database because the Idx is the primary key of the devicestatus table and must be unique (or null) by sqlite design. If you already cleared cache and appcache (different things) it's time to look in your database (table devicestatus) with ...

Thanks for your reply!
I'll dive into it

Hello, I couldn't find any related topics, so I assumed it was best to create a new one. Last night I noticed that my p1 meter has duplicate devices in the database. I'll attach an image that shows what I mean. When I set the Power device (IDX 1) to unused, both instances change to unused. When I ...

Last weekend I bought myself an AVR-X1600H. I was kinda thrilled when i found out it was possible to control the device with domoticz, until i realised it didn't work as easy as I thought it would :D Unfortunatly I haven't made a lot of progress either. With the default 'HEOS by Denon'-hardware i'm ...

Thanks for your reply. Yes, i did. I checked the log, and as you pointed out it's only triggered by a device change. After disabling dzvents in the settings, i noticed the CPU dropped immediately. So, it's not caused by the script, but by dzvents in general. In another post i found it could be ...

I have a question about the dzvents script, as well. After some struggle I got your script to work, and it's awesome! Finally able to control my Nest properly through domoticz. Thanks a lot. One question though, since I added the dzevents setpoint script, my CPU usage increased quite a bit. From <1 ...

Thanks for your help! I'm getting these errors after I copied the file "dzVents_script_Nest_Setpoint.lua" to the folder "domoticz/scripts/dzVents/scripts/". I added the .lua extension to the template file. The content I did not change, the Thermostat device (subtype setpoint) is called "Nest" in ...

I have a question about the dzvents script, as well. After some struggle I got your script to work, and it's awesome! Finally able to control my Nest properly through domoticz. Thanks a lot. One question though, since I added the dzevents setpoint script, my CPU usage increased quite a bit. From <1 ...

clinkadink wrote: ↑Friday 28 February 2020 2:41 I have updated the beta, please can you try and let me know if this issue is now resolved? Thanks.

Yes, it is!
You sir, are -again- the hero of the day. Thank you!

Thanks for your reply! That is indeed the method i'm using now. But because i use different 'kinds' of blocks, all with normal, hover and active states and also a day- and night mode, the list becomes quite large. A custom class, 'stat-block, or 'switch-block' for example, would result in a lot ...

Since the update i git-pulled this morning, my custom axis label colours and gridline options stopped working. Has something changed in how to define 'options' variables? I'll attach my graph definition. And yes, i know this is not very dry code, but i couldn't find a better way to make it work ...

I've spent the last couple of days making some custom css themes. And because I'm using different styling for differend kinds of blocks, that's kind of a pain: My css contains of big lists of block classes. And when blocks are added or removed, they have to be changed in a lot of places. So i was ...

clinkadink wrote: ↑Monday 24 February 2020 17:49 Thanks for the quick response. I have found the issue and will correct it this evening.

Works like a charm now, thanks a million!

Of course, with pleasure! { "blockId": "block_6", "block": { "devices": [ 9 ], "datasetColors": [ "rgba(255, 61, 61, 0.8)", "rgba(50, 180, 250, 0.8)" ], "barWidth": 0.9, "beginAtZero": false, "borderColors": [ "rgba(255, 61, 61, 0.8)", "rgba(50, 180, 250, 0.8)" ], "borderDash": [], "borderWidth": 2 ...