I've recently installed an Aqara Zigbee Weather Sensor in our chicken coop, to check on the temperature in the hen house in the winter. When I opened up hubitat this morning, I think it's trying to tell me that my chicken is cooked:
Anyone have any ideas why this would be?
Your house is on fire?
The sun went supernova?
You live in a volcano?
More serious answer, could the temp be 120F or 12C (54F) and the decimal is wrong?
Edit to ask, what is the actual temperature in the chicken house compared to this reading? Is there any connection between this number and reality?
I am having the same issue with an Aqara Temp/Humidity Sensor I installed. It is installed on the Aqara M2 hub and brought in via matter. Sounds like from the above post it doesn't make a difference how it is brought into Hubitat.
I have a C8 Pro running the latest platform. I am using the Generic Zigbee Temperature/Humidity driver that is native to Hubitat but I have also tried numerous other drivers with no luck.
The weird thing is looking back through my logs you can see log entries where that the temperature is reported correctly and then most instances where it is not. Also all entries are in Fahrenheit.
I suspect whatever the cause they are similar or the same to the original post.
It’s is about 32°F outside. I considered that the unit might be metric Celsius but it would be ~0°. I suppose there’s a possibility the temperature is getting converted more than once … but that still wouldn’t give me 1100° in any scale!
Well I’m glad to know two things:
Maybe there are more of us!
No, you are not alone. I noticed my issue last night. I thought the same about the conversion but I couldn't get it to add up either. What platform version are you running? I am trying to look for similarities since we are connected differently and using different drivers.
As for the matter adoption I just started using it a few days ago because I brought in an Aqara T1 Water Shutoff valve. I had heard that Aqara devices could be frustrating in HE with the zigbee mesh. I wanted to be able to use it without affecting my mesh but use rules containing devices I have directly in HE. The matter connection has worked great to this point.
I just have the Aqara sensor paired straight to the Hubitat, which is a 6th gen. I don't use any of the Hubitat rules, all my logic is in either Node Red or Apple Home... Home sees a weird temperature value too, which is what set me looking in Hubitat's control panel.
I am stumped. Hopefully, someone with more experience and knowledge may know.
@bobbyD @mike.maxwell do you guys have any ideas or thoughts?
We are too. Our engineers are looking into it to make sure the problem is not with the driver, though it doesn't look that might be the case.
Thank you very much. I don't think it is the driver either as me and @durable-navy-blue-ot have been using different drivers and connection methods but get very similar results. Either way again thank you guys for your help.
Bobby and @durable-navy-blue-ot my sensor has been reading correctly since yesterday evening. Yesterday I switched to the "Generic Zigbee Temperature Sensor" driver and left it that way all day. It did not work correctly and I got a bunch of warning in the logs. I attached screenshots. Then yesterday evening I switched it back to the "Generic Component Temperature Sensor" driver I was originally using and it has reported correctly ever sense. Which it was not doing originally. I have no idea if this done anything I just wanted to share with you guys.
@bobbyD that did not fix the issue long term. It was fine up till around 4pm today and it reverted back.
[ C8 with 2.4.0.128]
To further confuse the situation I've been having a similar situation but with a wholly different device.. I cleared the logs but I remember at one time it was 1207°F
Current it is working but is seems to come and go.
Could this be a Zigbee issue? I've recently had issues with sever Zigbee devices that have been solid for a couple of years.
This problem preceded the 2.4 version by a number of 2.3 versions ago
I was not going to post anything because it is a custom device with a driver written by me.
Well, if it matters, it seems like my temperature sensor goes wonky about once a day around 6am!
If it's notable, these are brand new Aqara sensors reporting 100% battery. Thanks for looking into it.
Mine was messed up all night and just changed itself to reading accurate again around 11:45 and been reading correctly the rest of the day.
This is crazy. Gotta love technology. Lol.
I'll join the one I have and see whats up after putting it in the freezer, the issue seems to be when the device gets around 32F?
@mike.maxwell will this apply to the Generic Component Temperature Sensor driver as well or just a weather station? I have my Aqara Temp and Humidity Sensor brought in via matter from my M2 hub and this is the driver assigned. I have the same problem.
Download the Hubitat app
