Welcome to Smart Home Forum by FIBARO
Dear Guest,
as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.
As a member you can:
- Start new topics and reply to others
- Follow topics and users to get email updates
- Get your own profile page and make new friends
- Send personal messages
- ... and learn a lot about our system!
Regards,
Smart Home Forum by FIBARO Team

Question
perjar 10
Hi,
I have an issue with a device for which the HC2 does not display its values properly in the UI.
The device in question is a power/energy meter built on the z-uno device.
As seen in the attached screen shot, the power and energy values are correctly written out in green and blue in the footer, but the main value, in big white letters, always shows "0.00".
I have other devices (for instance the Fibaro powerplug) for which the power values are correctly printed in the UI.
Has anyone seen this glitch for other types of devices? Or, is this a config issue somehow?
Please login or register to see this attachment.
Edit:
Have done some further investigations, sharing them here:
Comparing the HTML code in the we UI for my energy meter to a Fibaro wall plug, I can see that the UI fetches different device properties:
My device (device id 452, device kind = com.fibaro.multilevelSensor): <div class="TxtSensor" id="FG-452-value">0.00W</div>
Fibaro wall plug (device id 17, device kind = com.fibaro.FGWP102): <div class="TxtPlug plugwhite" id="FG-17-power">6.4W</div>
So, apparently, the UI fetches the "value" property instead of the "power" property.
I have tried to force data into the "value" property via a call to the Fibaro API (in a VD), but the data does not stick. The "value" property is apparently read-only .
Browsing this forum, I came across the thread below which brings up the same issue. A solution mentioned in the thread is to create a VD which shows the relevant data. That would be my work-around too, but I would prefer if devices appeared properly in the first place in order to minimize the number VDs running in the system and all the maintenance work that comes with it.
Edited by perjarAdded further details
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.