Z-Wave Issues with Firmware Update 30.3

[byteguy]

I’m also have problems with the Fibaro FGS-222 double switches, mine no longer work, cant even switch them from ST.
As far as I can see my FGS-223 switches are still working.

[mpikounis (Michael Pikounis)]

Same here.

[HeMan]

So, bearing in mind there seems to be some quite serious issues with this release, that are causing an entire device category (multi-channel switches it seems) to fail, how do we report this for a fix or roll-back?

[GSzabados (Gabor Szabados)]

@HeMan, @immortal, @byteguy, @mpikounis - Could one of you open a new topic to the Fibaro issue and post some reasonable live logging there?

It has been known for a while that those Fibaro devices tend to do weird thing regarding message encapsulation. There were other topics with similar issues before. So, it might not the firmware, but the device playing up.

[mpikounis (Michael Pikounis)]

@GSzabados it is definitely an issue with the firmware. My hub update at 12:04 and that was the exact point in time that my switch stopped reporting temperature readings. For a device that has worked flawlessly for the past 3 years I doubt this is a coincidence.

[HeMan]

I’m not using Fibros, I am using Philio PAN06s, and all of them have started doing the same thing (i.e. not working) since just after midnight last night, so almost certainly the firmware…

[GSzabados (Gabor Szabados)]

All of you can post here, not working statements, but it would be useful if any of you would post logs from the live logging, what might would give some clue what is the problem.

Otherwise there is the support email address where you can report this.

[sOckhamSter]

I’m also having the same trouble with two Fibaro FGS-223 / child devices, straight after the firmware update. I’ve removed and readded both devices, tried stock and custom DTH.

[Kianoosh_Karami]

@HeMan

I’m not using Fibros, I am using Philio PAN06s, and all of them have started doing the same thing (i.e. not working) since just after midnight last night, so almost certainly the firmware…

Can you PM me and let me know what exactly is not working?

[Kianoosh_Karami]

@sOckhamSter

I’m also having the same trouble with two Fibaro FGS-223 / child devices, straight after the firmware update. I’ve removed and readded both devices, tried stock and custom DTH.

Let’s move this in to PM, so we can work together to find a resolution for your problem

[mpikounis (Michael Pikounis)]

@GSzabados I’ve opened a ticket. I am using the Fibaro UBS by Chris Charles DTH. This is what I get in my logs when I turn the switch on:

[86e4f2cd-60fa-49e3-94ac-f6460af540b8](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#86e4f2cd-60fa-49e3-94ac-f6460af540b8) 10:46:50 PM: debug parsed 'zw device: 05, command: 2003, payload: FF ' to result: [descriptionText:Z-Wave Device Multichannel: BasicReport(value: 255), linkText:Z-Wave Device Multichannel, isStateChange:false, displayed:false]

[86e4f2cd-60fa-49e3-94ac-f6460af540b8](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#86e4f2cd-60fa-49e3-94ac-f6460af540b8) 10:46:50 PM: debug Catchall reached for cmd: BasicReport(value: 255)}

[86e4f2cd-60fa-49e3-94ac-f6460af540b8](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#86e4f2cd-60fa-49e3-94ac-f6460af540b8) 10:31:44 PM: debug parsed 'zw device: 05, command: 2003, payload: FF ' to result: [descriptionText:Z-Wave Device Multichannel: BasicReport(value: 255), linkText:Z-Wave Device Multichannel, isStateChange:false, displayed:false]

[86e4f2cd-60fa-49e3-94ac-f6460af540b8](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#86e4f2cd-60fa-49e3-94ac-f6460af540b8) 10:31:44 PM: debug Catchall reached for cmd: BasicReport(value: 255)}

[86e4f2cd-60fa-49e3-94ac-f6460af540b8](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#86e4f2cd-60fa-49e3-94ac-f6460af540b8) 10:16:44 PM: debug parsed 'zw device: 05, command: 2003, payload: FF ' to result: [descriptionText:Z-Wave Device Multichannel: BasicReport(value: 255), linkText:Z-Wave Device Multichannel, isStateChange:false, displayed:false]

[86e4f2cd-60fa-49e3-94ac-f6460af540b8](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#86e4f2cd-60fa-49e3-94ac-f6460af540b8) 10:16:44 PM: debug Catchall reached for cmd: BasicReport(value: 255)}

[86e4f2cd-60fa-49e3-94ac-f6460af540b8](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#86e4f2cd-60fa-49e3-94ac-f6460af540b8) 10:16:44 PM: debug parsed 'zw device: 05, command: 2003, payload: FF ' to result: [descriptionText:Z-Wave Device Multichannel: BasicReport(value: 255), linkText:Z-Wave Device Multichannel, isStateChange:false, displayed:false]

[86e4f2cd-60fa-49e3-94ac-f6460af540b8](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#86e4f2cd-60fa-49e3-94ac-f6460af540b8) 10:16:44 PM: debug Catchall reached for cmd: BasicReport(value: 255)}

[GSzabados (Gabor Szabados)]

That looks like the switch reports on (FF) with a BasicReport, but the DH has only a CatchAll defined for this kind of messages, so it is just logging it to the live logging.

@Kianoosh_Karami, thanks for joining in.

There was no mention of any Z-wave changes for this release, what has been changed in the device reports?

[HeMan]

In case anyone else has them, I can confirm the MCO S314 switch (which has four channels) is also now not working!

[Marco_Raimondi (Marco)]

Same issue here

Ciao, same issue on my fibaro fgs222 and also on my fibaro binary sensor. When it update the status, this don’t arrive to SmartThings hub…
Please fix
Thanks a lot

[Kianoosh_Karami]

The current status of the Z-Wave issue is that affected multi channel devices are sending unsolicited messages to endpoint 1 instead of endpoint 0. In the 0.30.X release, we upgraded our Z-Wave middleware (minor version bump) which included various fixes, needless to say in the latest SDK, there was a change to drop messages sent to hub with destination endpoint that was not 0 (Following the specification) and this change is now impacting these selected multi channel devices.

We are investigating the issue further, we’d like to be Z-Wave compliant as much as we can so we need to understand what prompted these devices to be sending a message to endpoint 1. The DTHs could potentially tell the device (Via association) to send unsolicited messages to different points other than 0.

I will keep you in the loop, if you have a Fibaro device that is affected, I have a potential fix that I would like you to validate for me (Self publishing a modified DTH). So if you are up for it, please PM me.

[GSzabados (Gabor Szabados)]

@Kianoosh_Karami, that issue has been raised months ago with some Fibaro devices.

Fibaro Single Switch 2 no longer responds to status (January 2020)

@steven.green, any idea why are those devices reporting any status from sourceEndpoint 1? So far, the Switch 2 sends MultiChannel message with sourceEndpoint 1, what cannot be handled with the current if sourceEndpoint == 0, what is a reasonable condition. The Dimmer Switch 2 sends also MultiChannel encapsulated messages and also with sourceEndpoint 1. More interestingly the destinationEndpoint is 1 as well, is that correct? Is the Firmware development on a downhill at Fibaro or have they changed something with some newer firmwares and that’s why all these happening?

[djh_wolf (Daz)]

Exactly the same for me, with 2 fibaro UBS’s and a double switch. Since monday night, completely unusable.

[djh_wolf (Daz)]

Hi - My fibaro UBS and my Fibaro double-switch have ceased to function after monday night’s hub update. Could you possibly assist please? It’s removed the functionality of the majority of my home system (central heating and outdoor motion detection).

Kind regards,
Darren

[siwilson (Simon)]

I have this issue and I am using the stock device handlers for Fibaro FGS-223 Dual Relay.

Fibaro Double Switch 2 ZW5 - For the main (parent) device
Fibaro Double Switch 2 - USB - For the secondary (child) device.

[yahav]

I have a problem with Fibaro FGS-223 double switches I can turn on and off but the status is not updated automatically I have to Refresh in every time.