Released version 5.5.0 with the following changes:
The throttle events preference was added for Vindstyrka and Inspelning, the chattiest IKEA devices:
Have fun!
Can a sample interval rate setting be added to the air quality sensor driver? Looking to reduce it a bit.
Hi Dan, thank you for these updates! They are not showing up for me when I try to update with HPM. I am on 5.4.1
I really appreciate all your hard work making these for us all.
Thank you very much!
Cheers
Tim
I moved the code repository from GitHub to a nicer location, looks like HPM does not handle this corner case. I believe the quick fix is to use "Un-Match" then "Match-Up" in HPM. Sorry about this.
My 24hr errors look to be fixed. Good not to see red in my logs now! Thank you @dandanache
That's great - thanks @dandanache . I have updated both my Vindstyrka and they are both reporting all the relavant readouts. I have them both set to report every 5 minutes. The readouts seem to show up in the info log with the appropriate frequency, with the odd one missing here and there (I dont have an extensive ZIgbee network).
The one that is odd is temperature, which seems to only report about once an hour (sometimes a little more often. It also seems to only report temperatures in 1.8 degree increments: 69.8, 68, 66.2 64.4 etc. I have no idea as to whether this normal expected behaviour for the device - I might start paying attention to the device display to see the temps reported there. Happy to screen capture logs if this is of interest or unexpected etc.
Thanks again for all your work.
Jim
That's actually 1°C increments starting a 0°C
0°C - 32°F
1°C - 33.8°F
2°C - 35.6°F
-----
19°C - 66.2°F
20°C -68°F
21°C - 69.8°F
This is not really how the new setting is working. When you select "5 minutes" from the "Preferences" tab, it instructs the device to not report an attribute change, if the previous report was less than 5 minutes before (throttle).
This is a crude approximation of how Zigbee attribute reporting works (if you selected "5 minutes" from the dropdown):
The odd ones missing here and there are not lost messages, but rather the device did not sent a new report since the attribute value did not change from the last sent report (no point in sending the same value again). This behavior is more visible with temperature reporting, where the temperature does not have big swing changes.
Thanks @nclark for the clarification. I use C and F for a variety of different readouts/platforms but rarely need to do the conversion! I should have recognised the relevance of it being 1.8!
Thanks @dandanache for the clarification. My various other motion/temp sensors report to 1 or 2 decimal places in F. I had briefly wondered whether it was an "only report changes" scenario but as with @nclark 's clarification, it had not occured to me that the temp would only be reported to 1C sensitivity and thus not trigger reporting events. I guess my Vindstyrka are never going to tell me it's 63 degrees F! LoL
Cheers
It's a real shame that IKEA implemented it this way (no decimal precision), although the Sensirion SEN54 sensor it uses is actually quite capable.
I'm still hoping they will release a firmware update to fix this limitation.
That's interesting to know and really quite disappointing / amazing. Otherwise, the obvious conclusion would have been to assume a cheaper / less sensitive sensor was used! I also came to the conclusion that the temp / repeater functionality would actually be the most useful. As I find the air quality readouts don't change much for me and when they do, it's really not information that prompts any hubitat action.
Seems to be a issue with the Hubitat package managers location for this. It just failed?
I think a HPM "Un-Match" and "Match-Up" should fix this problem.
In my case, that did not work.
I had to install the new package, manually change every driver to the new version, and then delete the old drivers.
Yes not sure if it's working for me either. Need to try again but looks like it's pointing nowhere.
it sorted it now, thanks @dandanache
Hello @dandanache.
Would it be possible to add a selection to increase the “Throttle Events” to greater than 20 seconds, perhaps 1 minute?
I just upgraded my (2) Vindstyrka’s to firmware 11 and they have become very spammy. One is worse than the other where the VOC changes every second. Unless perhaps there is a way to adjust this within the device’s settings?
Additionally, would you happen to know any trick to updating the Vallhorn firmware beyond what has been stated in the forums? I keep getting an update failed. I’ve tried several times. Even sitting it on top of my hub.
Thanks!
You should be able to select values bigger than 20 seconds; the dropdown contains values up to 5 minutes.
To make sure the update completes: First re-pair (don't remove the device from Hubitat) the device very close to the hub (max 5 cm); this way we make sure that the hub is the parent device. Then start the firmware update (see below). Keep the device in the hub range (1-2m) until the update completes (about 100 minutes, check log entries coming from device called "sys1"). Finally relocate the device to its final place, it will select a new parent at some point.
To start the update: Immediately after you click "Update firmware", and then the "Yes" confirmation, click on one of the buttons on the back of the device. It should wake it up.
Download the Hubitat app
