JJ that all makes sense. Not limited to Fibaro, other devices are also failing. Don’t thik ST will roll back, they have never done this when faced with problems before. This, apparently is an issue to do with ST being compliant with changing z-wave specifications. Trouble is if Fibaro fix the issue with an OTA firmware update we can not do it on ST platform. Has to be done on Fibaro own platform. Unless ST lean heavily on them. Along with 100’s of other ST sers we will have to sit back & wait to see what happens.
Interesting is that my two later FGK-101 that have temp & use native ST handler show temp.
Thanks for your time on this.
I also have other non Fibaro devices that are not working correctly, SSR boiler control for one.
It is interesting that your 2 FGK-10x ZW5 are OK : likely, it comes from the stronger encoding performed by the newer FGK-10x for reports (see the different decoding sections in my v0.9.7.4 Handler).
Unfortunately, there is again nothing I can do : the FGK-10x choose the way they wish to report.
The only (partial) solution AFAIK would be for SmartThings users to be able to opt for NEVER UPDATING their Hubs firmwares. That would have avoided the latest sore episode.
But unfortunately, that would not avoid updates within the rest of the SmartThings cloud, as we have seen multiple times in the past
You may volunteer for beta-testing the just released 0.30.4 Hub firmware, supposed to solve the endpoints<>0 issue for older FIBARO devices, on v2/v3 Hubs.
See this post in the other thread.
Thanks @johnny2678, your findings are unfortunately “normal” now that SmartThings confirmed 0.30.4 took care only of “Destination Endpoint 1” and ++NOT++ of “Destination Endpoint 2”, as used by FGK-101 for Temperature reports.
I added a post in the Z-Wave Issues with Firmware Update 30.3 thread to make the case for FIBARO and pre-ZW5 FGK-10x.
Let’s pray the “Compliance Fundamentalists” do not win…
There are so many lawyers in the States, some must have too much free time on their hands due to the confinement.
If one of you knows one such, could be worth to start agitating a Class Action Suit menace…
And no, I am definitely not a prosecution freak, but I hate to be swindled as neglectable “collateral damage” when law is clearly (?) on our side.
Especially since the cost for SmartThings to give us satisfaction is basically ZERO, they just have to backtrack (and yes, lose some face too ).
Unfortunately (or maybe fortunately) I don’t know any lawyers like that and I’m not the litigious type either. I let my money speak for me.
Already own a hubitat, this will just accelerate my migration.
buuuuut of course hubitat does not support the FGKs, probably due to zwave incompatibility ;). I tried the other night, they pair ok but don’t even report open/close correctly, much less Temp. Kept getting “BasicSet” responses.
I am running into the same issue that appears to be driven by the recent Firmware push (30.3). Can others confirm that the beta FW (30.5) corrected the temp reporting issues? If so, can someone point me in the direction of getting my hands on this FW version?
).