Dynamicly change dummy kWh counter icon state

[RonkA]

Hello All.

I use a lot of dummy kWh counters in Domoticz, and for almost all counters i made some nice custom icons that have both ON and OFF states.
For example: on my dashboard i have a switch:

wisselaar button.PNG (8.01 KiB) Viewed 1237 times

and a kWh counter:

wisselaar kWh.PNG (11.36 KiB) Viewed 1237 times

So both devices use the same icon.
Now the issue:
At this moment there is nothing to count but the ON-icon is shown on the kWh counter, this is IMHO not correct visually..

It would be nice to see both states reflected in the counter: If counter-value is zero, the OFF-icon is shown. Any other value shows the ON-icon..

The only problem visually i can imagine is that, if there would be fast switching between zero and a value, this could be annoying..
But i think this could be resolved by fixing one of the icon-states to the device, or add a De-bounce time before the state is changed.

[FlyingDomotic]

It's possible to dynamically set any icon through a dzVents script :

Code: Select all

return {
    on = {devices = "my Device Name"},
    execute = function(dz, item)
        local icons = {
        [0] = 140, -- Off
        [10] = 137,-- Auto
        [20] = 138-- Manual
    }
    print('Info: '..item.name..', level '..tostring(item.level)..', icon '..tostring(icons[item.level]))
    item.setIcon(icons[item.level])
    end
}

In this example, "my Device name" is a selector with 3 values (0, 10 and 20), associated respectively with icons number 140, 137 and 138.

[RonkA]

Hi,
Thanks for your reply to my suggestion;
But this feels more like a workaround for wat i am proposing, because you have to make the same icon twice..

One icon, like the original i made, to use for the swich that has all the functionallity build into it to work in both on and off states;
And a second icon that is stripped of the original On-state image to use with for example a counter that has than to be swiched by using 'seticon' in a script..

Yes it should work, but it would IMHO be so much more elegant to be able to use just the one icon like i propose..

Another little bit lesser elegant way could be to have a function like a boolean device attribute like 'seticonstate'..