On VERA3/UI5
Using Fibaro FG211, containing a zwave root device and two virtual devices, all appearing on the Dashboard as 3 devices in total.
The two virtual devices are controller by the zwave root device and switch the connected appliances.
These devices do not measure energy usage but by entering a value in Watts under the Device’s Settings tab in the field “energy used” this value will be used to report energy usage dependent on ON/OFF and dimming levels.
After mixing up root and virtual device, I put in a value for “energy used” in the root device.
As a result, the energy usage shown in the dashboard now also include this energy. As the root seems to switch along with virtual device #1 it distorts the picture.
I put the “energy used” field back to empty, tried putting it to zero, but the root device remains to report energy used at a level as specified in virtual device #1.
Any ideas how to reset a value specified in the “energy used” field?
(If there is no fix, I could probably exclude and re-include the device)
Thanks !
only thing i can think of is goto measuring and start a measurement on the device… causing it to reset to 0 then immediatly stop it. or put a 0 in the energy variable
I tried putting a “0” in the field, but it does not change anything.
On the Dashboard, I still see 40Watt displayed on the root device and when I look at historic and live usage it remains there.
So discrepancy between what has been put in the field and what is reported.
This is however only the case for the root device. The two virtual devices follow the “energy used” value properly when reporting energy usage, also when put to zero.
I can’t actually do a measurement because the device does not really sense the energy usage.
mm then i wouldnt know… it should change… then probably have to remove the whole device and re-add it
i saw in the fixes list of the new to come update to the firmware that they adressed some energy functions. maybe this fixes also this problem. i was tampering between the aeon and fibaro switches… tend to go aeon as these have built-in energy report thus not having this issue.
Fibaro €60, Aeon €70 with energy measurement. Seems a good deal.
Advantage of the Fibaro 211 is the fact that it facilitates two switches. Halfens the cost per switch…
[quote=“Turk4U2, post:5, topic:170894”]Fibaro 60, Aeon 70 with energy measurement. Seems a good deal.
Advantage of the Fibaro 211 is the fact that it facilitates two switches. Halfens the cost per switch…[/quote]
indeed i was looking at this 2-in-1 as well… thing is i have a ceiling light which has 3 bulbs… and one that has 4 ledlights for dimming. i want to use this dimmer from aeon for this and the 3 bulb light has to have a yet to figure out solution. i want to be able to switch them separatly but on the other hand i might as well make it dimmable …
Ok, excluded the devices and included them again.
Needed to edit scenes that use the devices but all in good order now.
Lesson: when putting in a wattage in the Fibaro device’s “energy used” field, make sure you know what is the zwave root device and what are the virtual devices.
These have all the same name after including the device.
But it is possible to see it by checking what is controlling each device under the device’s “Advanced” tab.
The virtual ones are controlled by the root device. The root device is controlled by the network (zwave).
Not that simple to put the “energy used” field back to zero if you happen to have entered a value in the root device unintened.
But one gets a good approximation of energy usage by entering the wattage of connected lamps. Basically of anything that has a load that is fairly accurately known.
As long as you do that only for the virtual devices…
When looking at the advanced tab, there should be a field called id_parent, that is the main device of the child devices.
Cheers Garrett,
Terminology check:
root = master = parent
virtual = slave = child
Is this correct ?
See these all used in the different threads.
Yes, it should be referred to as parent and child devices.
does this happen with the new beta build also ?
i think its coz the parent device holds the combined sum of energy used by its childs. so if you would manually fill both the system gets confused as the calculation is not correct
Even if the system gets confused, I would expect that emptying the field “energy used” would do the job.
It doesn’t though.
It works as long as only wattage is specified for the child devices and the parent device remains untouched.
Solved now by excluding/including but will reproduce the issue and try with the new beta release.
yup thats what i say… when u would set the parent to 0 … it get override by the child devices as sum of all energy
[quote=“Da_JoJo, post:11, topic:170894”]does this happen with the new beta build also ?
i think its coz the parent device holds the combined sum of energy used by its childs. so if you would manually fill both the system gets confused as the calculation is not correct[/quote]
Yes, still the same under 1.5.346