Hello and thanks for creating this driver!
I just got my Vindstyrka and set it up yesterday.
I'm not seeing all the states you are and was wondering if there was something else I needed to do to get this setup.
I'm also noticing the humidity value doesn't seem correct and I'm not getting regular updates.
Thanks for any help you can provide!
Jim
I have one of these in an unconditioned outbuilding and it's been pretty cold lately. I think something is screwy with the temperature code or maybe it's the device itself, I dunno. However, I've been getting an error on a dashboard including that sensor's data so I started looking around and it seems the sensor is messing up when temps go below 32F.
Very strange, in the meantime I am just filtering out temps over 150 on that dashboard which is working but as would expect I'm getting a "floor" of 32:
Outside is OpenWeather, shop is a sonoff zigbee T&H sensor and the house front and garage side are HUE outdoor motion sensors...you can see where they all go lower.
Hi @dstutz ,
This is a bug in the driver, it is missing the code to handle the raw readings of negative temperature values (below 0 degrees Celsius).
I will check and fix this ASAP in the next few days.
Sorry to be stuck like a noob, but I could use some help setting this sensor up. I added the driver manually (before I know about using Package Manager), and added a virtual device. I tried pairing the device using the Zigbee button. No luck at all.
I suspect I've fouled things up. I restored the database, and simply installed the Vindstyrka package via the Package Manager.
Still stuck, and could use a little push in the right direction :).
I bought the device off Ebay, and wouldn't you know it, it was already Zigbee paired. Simple fix. Press the pair button four times, and the device resets to factory.
It now pairs, and I'm working on the next steps.
How have you felt this has worked for you?
I'm really curious to monitor PM2.5 in my basement and maybe near bedrooms, which i know is tricky in a monitoring device.
PM 2.5 seems to be way more useful than their relative TVOC measurement...and it's a good temp/RH monitor and zigbee repeater.
Has anyone noticed that the humidity readings are particularly high. Is there a way to calibrate this down?
I noted adding temperature and humidity offset preferences in the next driver update.
Now that is impressive, will it offset the reading down on the actual hardware display or just in the HE App?
Thanks for those Sensirion's docs.
I'm curious what values/thresholds folks have decided to use for life-concerning alerts. I assume "poor Air Quality" would not be a good "all inclusive" value to trigger early warnings as someone opening some "high VOC product" in the house would cause nuisance triggers if what you were most concerned about was:
a) the combustion by-products of house fire
b) the combustion by-products of a faulty natural gas appliance (furnace, water heater, etc)
So what PM2.5 thresholds have folks [non-smokers] found appropriate based on the device's capability and typical everyday (no-worries) operating range in their homes?
Thanks in advance for any commentary.
I hope most folks are not using this device coupled with a Hubitat for life-concerning alerts. Neither device seems engineered for that level of service.
Then I would
a) get a smoke detector
b) get a carbon monoxide detector
I suppose a faulty gas appliance might give off VOCs in abundance while not giving off high levels of carbon monoxide, but the only 'life-concerning' issue I've heard of with gas appliances is CO. If VOC from these sources is also a life-concerning issue, I'd like to be educated about it as I still have a gas water heater and furnace.
Thanks for the great drivers. They are working well in my Hubitat setup so far.
I was wondering if anyone has had experience using them with Google Home. While they are being exposed to Google I am finding that it is only passing the temperature to the app and not humidity or air quality (of any format, pm2.5, AQI, or otherwise). I'm hoping someone can help shed light on if this is a limitation of the current drivers or if its an issue with my specific setup.
Here is what I'm seeing in my app.
I think you might be surprised by what a device like this with well designed sensor capability might indicate prior to a "serious situation" that would normally be caught by traditional detectors.
For example, I literally can look at the Vindstyrka and tell when the fireplace is going...and I have all the detectors you mentioned sitting quiet. Granted the Air Quality is still in the green at that point but nontheless the data tells a story.
Why bother with this device if you don't trust its data for health & safety?
Download the Hubitat app
