'Fibaro Z-Wave FGK-101 Temperature & Door/Window Sensor' Full Support Handler

@daven @IcarusR @tonydt1g3r
It is clearly due to SmartThings cloud modifications.
Below is is the email notification I received on April 4th :

SmartThings Hub 2015 (v2) and 2018 (v3) Firmware Update

Maintenance complete

Firmware version 30.3 has been released to all Samsung SmartThings 2018 and 2015 model Hubs. Please contact us via support.smartthings.com if you have any questions.

Time posted

May 4, 20:28 EDT

Components Affected

Americas - Hubs, Devices, and Automations, Europe, Middle East, and Africa - Hubs, Devices, and Automations, Asia Pacific - Hubs, Devices, and Automations

What I can contribute to this debate is that curiously (for once !), my dozen of FGK-101 are STILL WORKING :smile:
They are all :

=> Please confirm that you all have v2 or v3 Hubs.

Since I do not have a v2 or v3 Hub, I will not be able to help much, although there is clearly something in my custom handler to which the latest hub updates are allergic.
Usually, I find incompatibilities running “live logging” after a reload of my custom handler.
If somebody among you knows how to do that, I may try to work with him to isolate the problematic code.

Unfortunately, SmartThings support will be completely useless , as they have been since they decided “custom handlers” were anathema (and that after SmartThings promoting back in 2014/2015 these handlers as one more proof of SmartThings “open” solution superiority… :frowning: ) .

Once we have a better idea from where comes this new incompatibility, we may try to post to the developers forum, but they will not help until we have more or less isolated the problem line(s).

Sorry I cannot help more, it would a nice change from corona-virus worries… :smile:

I am using a V2 hub on v9.7.4 of the handler

Is your FGK-101 a true ZW5 version ?
If not, you may try to use the pre-ZW5 version of the handler instead.
But since you have a v2 Hub, the suspect becomes clearer…

Unfortunately, I cannot even check if the problem comes solely from my ZW5 version of the handler, because the only ZW5 FGK-101 I own is at home, out of battery, and I am confined 500 miles away from home, thanks to that nice virus…

@geeji
Thanks for then interest.
Yep so my hub now runs the new firmware that obviously messed things up again. Thanks Smartthings. Its fine if you tow the party line & only do things the Smartthings way. But if you try to improve / tweak things you are in trouble !!

My hub is V2 in UK. FW 000.030.00003

my temp FGK-101 x 2 of each not working using v0.9.5.1 with sensor commented out

zw:S type:2001 mfr:010F prod:0700 model:1000 ver:2.01 zwv:3.42
zw:S type:2001 mfr:010F prod:0700 model:1000 ver:2.05 zwv:3.67

my door sensors with temp x 2 still working with temp. Using standard smartthings “Fibaro door/window sensor ZW5 with Temperature”

zw:Ss type:0701 mfr:010F prod:0701 model:1001 ver:3.02 zwv:4.05

I tried using full uncommitted v0.9.5.4 on one of the ver:2.01 zwv:3.42 temp sensors using a magnet it registers open & closed, but not temp.

If you need more info let me know.

Thanks Andy, that’s interesting :

  • v2 Hub latest firmware update (FW 000.030.00003) is definitely involved
  • problem exists both in US and in UK
  • pre-ZW5 FGK-10x are affected
  • both versions (pre-ZW5 9.5.1 and ZW5 9.7.4) of my custom Handler are affected
  • SmartThings standard handler for ZW5 FGK-10x still works

As explained before, I do not have a v2 Hub, and because of that cannot do much meaningful testing.
However, if one of you with a pre-ZW5 FGK-10x could :

then, may be, I could locate the problem (no warranty thou, since I am not home and have not any Hub or any FGK-101 at hand).

On the other hand, those with the problem could revert to the SmartThings standard Handler, if it is enough for their temperature measurement needs.

Sorry again about this problem, but as you can imagine, SmartThings has never included me nor my custom Handler in their new firmware pre-release validation process…

Hi JJ
I have tried using the standard handler & that does not work on one of my affected FGK-101.
I came across this thread z-wave-issues-with-firmware-update-30-3 in particular this post talks about end points.

I will change to your v0.9.5.4 & post logs later.

Don’t apologise it is not your fault. It would seem a lot of Fibaro devices are having problems.
See this thread, SHM not disarming & setting off alarms

@geeji Just done as you asked. Hot water temp FGK-101 reverted to your v0.9.5.4 handler logs …

a7b647fe-e9c6-496b-8499-db1b28a54a82 14:12:42: debug Parsed WakeUpIntervalReport(seconds: 3600, nodeid: 1) to null
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:12:42: debug WakeUpIntervalReport WakeUpIntervalReport(seconds: 3600, nodeid: 1)
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:12:42: debug Parsing… 'zw device: 22, command: 8406, payload: 00 0E 10 01 ’
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:12:42: debug --------------------------Parsing… ; state.parseCount: 7--------------------------
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:12:42: debug Parsing… 'zw device: 22, command: 8406, payload: 00 0E 10 01 ’
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:12:42: debug --------------------------Parsing… ; state.parseCount: 7--------------------------
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:12:41: debug Parsed SensorAlarmReport(seconds: 0, sensorType: 0, sourceNodeId: 34, sensorState: 255) to [[‘name’:‘alarm’, ‘descriptionText’:Hot Water Temp is tampered with !, ‘isStateChange’:true, ‘displayed’:true, ‘linkText’:Hot Water Temp], physicalgraph.device.HubMultiAction@7bebaea2]
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:12:41: debug cmdBlock : [8405, delay 1200, 600D02023104, delay 1200, 8408, delay 2000]
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:12:41: debug wakeUpNoMoreInformation()
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:12:41: debug sensoralarmv1.SensorAlarmReport 255
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:12:41: debug Parsing… 'zw device: 22, command: 9C02, payload: 22 00 FF 00 00 ’
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:12:41: debug --------------------------Parsing… ; state.parseCount: 6--------------------------
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:40: debug Parsed WakeUpIntervalReport(seconds: 3600, nodeid: 1) to null
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:40: debug WakeUpIntervalReport WakeUpIntervalReport(seconds: 3600, nodeid: 1)
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:40: debug Parsing… ‘zw device: 22, command: 8406, payload: 00 0E 10 01 ’
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:40: debug --------------------------Parsing… ; state.parseCount: 5--------------------------
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:39: debug Parsed BasicReport(value: 255) to [[‘name’:‘contact’, ‘value’:open, ‘descriptionText’:Hot Water Temp is open, ‘isStateChange’:true, ‘displayed’:true, ‘linkText’:Hot Water Temp], physicalgraph.device.HubMultiAction@78af0325]
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:39: debug cmdBlock : [8405, delay 1200, 600D02023104, delay 1200, 8408, delay 2000]
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:39: debug wakeUpNoMoreInformation()
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:39: debug openClosed BasicReport(value: 255)
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:39: debug basicv1.BasicReport 255
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:39: debug Parsing… ‘zw device: 22, command: 2003, payload: FF ’
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:39: debug --------------------------Parsing… ; state.parseCount: 4--------------------------
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:37: debug Parsed BatteryReport(batteryLevel: 74) to [[‘name’:‘battery’, ‘displayed’:true, ‘isStateChange’:true, ‘unit’:’%’, ‘value’:74, ‘linkText’:‘Hot Water Temp’, ‘descriptionText’:Hot Water Temp battery is 74%]]
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:37: debug battery map : [name:battery, displayed:true, isStateChange:true, unit:%, value:74]
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:37: debug state.forcedWakeUp : true
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:37: debug state.batteryInterval : 83700000
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:37: debug state.lastReportBattery : 0
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:37: debug nowTime : 1588943077739
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:37: debug batteryv1.BatteryReport 74
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:37: debug Parsing… 'zw device: 22, command: 8003, payload: 4A ’
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:37: debug --------------------------Parsing… ; state.parseCount: 3--------------------------
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:30: debug Parsed VersionReport(applicationVersion: 2, zWaveLibraryType: 3, applicationSubVersion: 1, zWaveProtocolSubVersion: 42, zWaveProtocolVersion: 3) to null
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:30: debug versionv1.VersionReport: VersionReport(applicationVersion: 2, zWaveLibraryType: 3, applicationSubVersion: 1, zWaveProtocolSubVersion: 42, zWaveProtocolVersion: 3)
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:30: debug Parsing… 'zw device: 22, command: 8612, payload: 03 03 2A 02 01 ’
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:30: debug --------------------------Parsing… ; state.parseCount: 2--------------------------
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:10: debug device.data: [:]
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:10: debug device.label: Hot Water Temp
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:10: debug device.name: Hot Water Temperature
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:10: debug device.id: a7b647fe-e9c6-496b-8499-db1b28a54a82
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:10: debug device.displayName: Hot Water Temp
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:10: debug zwaveHubNodeId: 1
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:10: debug device.currentValue(‘reportASAP’) : 1
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:10: debug state.maxEventInterval : 13800000
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:10: debug state.batteryInterval : 83700000
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:10: debug state.deviceID: Temperature
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:10: debug Updated !
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:10: debug tempQuantumSixteenth : 5
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:10: debug device.displayName.substring(0,1) : H
a7b647fe-e9c6-496b-8499-db1b28a54a82 14:04:10: debug Configuring…

Thanks a lot Andy, and special thanks too for the link to this thread : z-wave-issues-with-firmware-update-30-3.
It looks like they have clearly isolated the incompatibility issue, related to the (possibly illegal) use of multiple channels with endpoints <>0 by FIBARO devices, including FGK-10x.
I also posted in this thread to remind SmartThings development that the issue is NOT limited to endpoint 1, but also concerns endpoints 2, specifically used by FIBARO for Temperature reports.

The trace you posted is definitely consistent with that since no multi-channels reports are present in it.

If the analysis in that other thread “Z-Wave Issues with Firmware Update 30.3” is correct, then there is nothing I can do anyway within my custom Handler to work around this issue, since the temperature reports are all filtered out by the Z-Wave layer of the new v2/v3 Hubs firmware, BEFORE my handler gets control.
We will have to wait and pray, hoping that SmartThings will backtrack, rather than making furious all users of FIBARO (and others) devices :smile: .

1 Like

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.

@geeji Just read your post on my linked Z-Wave Issues With Firmware Update 30.3 thread.

I have three FGMS-001 one FGDW-002 & two FGK-10x Z5 that all report temperature correctly (he says reaching for his phone to check)

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 :frowning:

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.

Kianoosh_KaramiSmartThings Staff

9h

Hey All,

We are releasing 0.30.4 firmware to our external beta users Today (Friday, May 8th) which includes the fix for the Z-Wave issue in 0.30.3.

If you are interested in receiving the firmware, please sign up using the following link https://goo.gl/Gw4cEK . You can always opt out afterwards.

I would appreciate if those with the affected hubs and devices could sign up and provide feedback over the weekend.

Thanks again for your help and patience!

Got the beta but it didn’t bring temp readings back on my 101’s :face_with_symbols_over_mouth:

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…

1 Like

That post took my breath away :rofl:

Well said, hope they have a reasonable response and comply with opening up the other endpoints. Thanks again for your work on this.

I mean, you even included a ++JUST DO IT!++ :rofl:

A third thread has been created to specifically discuss Z-Wave Backwards Compatibility, and all the posts I entered about the broken FGK-10x in the previous Z-Wave Issues with Firmware Update 30.3 have been moved there.
Not sure it is a good omen…

2 Likes

Based on the limited numbers of users posting, I’d guess ST is going through a Recall calculation and deciding it’s not worth it. We’re on our own.

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 :star_struck:).

1 Like

I like your style :rofl:

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.