Has anyone seen this? Lets say the light is off, 0 watts. Turn it on to 50% and it shows 20watts, turn it to 100% and it shows 40 watts. Then turn it back to 50% and it still shows 40 watts still, take it back to OFF and it shows 20 watts
It always appears as if the real time usage is one step behind the actual usage? Ie the measurement now, is from the previous setting
Has anyone sen this or worked out away to fix it? Ive tried every setting available.
Even when its off, its showing the previous wattage. If I then send another OFF Command when its off, it shows 0 correctly.
Then use the sensor_multilevel command class which is working fine.
I remember reading something about comparison watts vs power, you will be able to find it through the forum search.
Actually it’s the same, just different command classes.
So I would recommend to use the command class which is working better than the other …
So it only sends a message if the change in W is > 10% of the current load. if you make small changes you will not see a lot. As long as you see the big changes then it is working. The dimming % will not have a direct correlation to the W so it is not a 10% change in dimming level.
If you are desperate to see blow by blow changes then you could set it to a lower value but unless you are using the change in a scene why waste the network bandwidth?
I have used the W channel for only one thing and have not set that automation up on OpenHAB yet. That was to turn on my kitchen extractor when the electric oven is turned on.
The only other automation I have heard it used for that made sense to me was someone that used it to monitor their TV turning on and off and used a roller shutter control to power the lifter.
If you have something like that then leave parameter 50 to as small % as needed to make the automation work and use the value. If not then set parameter 50 to 0 and turn the report off so it does not waste your Zwave bandwidth.
Would not recommend the poll after as that will doubly waste your network bandwidth.