Hi,
after the recent update to HA (from 0.58.1 to 0.59.2 in my case), my Fibaro wall plug got an additional data point “velocity” which showed up as a new badge:
It does not seem to be a one-off thing.It always reported a pretty recent update timestamp when I checked it.
Also, it is stable at 35m/s even though - last time I checked - the device is stationary…
Whats going on?
Thanks
Jochen
Same here. All of a sudden one of my Fibaro Wall plug shows Velocity. Not any of the other Fibaro Wall Plugg that i have.
I have the same problem. In addition it shows humidity and multiple other types of measurements that ut is not support to report.
The same goes for my Aeotec multisensor 6. Suddenly badges with power and other things show up. When they first show up they stay until i exclude and include the devices all over again.
Then ut is fine for some days, until the invalid badges show up again.
This happens om both 0.60 and 0.61
I have a Velocity sensor, too. Digging around in the xml file I found this:
<CommandClass id="115" name="COMMAND_CLASS_POWERLEVEL" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="list" genre="system" instance="1" index="0" label="Powerlevel" units="dB" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
[---cut---]
</Value>
<Value type="byte" genre="system" instance="1" index="1" label="Timeout" units="seconds" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
<Value type="button" genre="system" instance="1" index="2" label="Set Powerlevel" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="byte" genre="system" instance="1" index="3" label="Test Node" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
<Value type="list" genre="system" instance="1" index="4" label="Test Powerlevel" units="dB" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
[---cut---]
</Value>
<Value type="short" genre="system" instance="1" index="5" label="Frame Count" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-32768" max="32767" value="0" />
<Value type="button" genre="system" instance="1" index="6" label="Test" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="button" genre="system" instance="1" index="7" label="Report" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
<Value type="list" genre="system" instance="1" index="8" label="Test Status" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" vindex="0" size="1">
[---cut---]
</Value>
<Value type="short" genre="system" instance="1" index="9" label="Acked Frames" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-32768" max="32767" value="0" />
</CommandClass>
My guess is, that somehow that “Test”. value is triggered.
Well I’ve just hidden the entity from home assistant. So far it seems as if it is not making up further entities.
What bothers me more are the implausible power readings. I sometimes get 100.000W values in between the normal ones.
Since a reboot yesterday it is also showing Distance.
There wasn’t an issue yet, so I created one