Yes, but it has nothing to do with homey’s capabilities, it (most likely, 99% sure) has to do that homey listens to the wrong endpoint of the door sensor.
Homey now listens to the main device for temperature reports instead of sub endpoint 2 where it is under, figured this out based on old code, from pre SDKv2 rewrite (pre fibaro app v2.x.x), where it did work.
I see. Thx for explaining that to me.
Well, so I have to sit down and wait for it. Do you KNOW that this is going to be fixed? And if so, how long that propably will take? Any chance for it within the next weeks?
Let me combine all in a quote what I’ve said so far.
So will there be a fix? There already is one, and is awaiting for testers as I don’t have the device myself.
After it being tested (like I said I can’t test it myself, so how long it takes is up to you guys) and athom have it approve in the app (I can try to let athom accept it fast).
So how long? Could be monday in the beta app.
But could also take several months if no one will/can test it
hmmm, you can try to bother Athom to accept the PR (it is awaiting for them), but with so small amount of people, don’t think it will do much.
But as it is only a small fix, don’t think it will take long for them to accept it.
Follow-up question about this problem/fix.
I have the v1 with sensor (also for my pool ).
Don’t remember when I installed it but I’m thinking it was befor the V2 update.
My temp was working but hasn’t for quite some time. It always shows the same temperature.
Is it possible this fix will solve this? Will I have to add the device again for that?