After update to 0.10.7 and PTP - Fibaro 222's won't switch off

Eternity

Strange, all experimental updates worked out nicely, but now I have a strange issue. I have a Fibaro double switch (FGS-222) and it does't switch off anymore; not via the Homey interface (although the slider is in the OFF position) *nor* via the actual wall switch!

bvdbos

Do other zwave-devices work? Not something overflooding the network?

Eternity

Yes, other stuff seems to work.
I will PTY a couple of times and restart the Fibaro App.


BTW
Thanks Bas :-)

bvdbos

Seeing nothing really changed in FGS-222 it seems like the switch broke? I'd try to reset it. Fibaro Switch provides two methods for resetting.

Method I :

Reset by removing Double Relay Switch from the existing Z-Wave network. The device may be removed using the

controller that has the ability to include/exclude devices from/to Z-Wave network (see the manual of controller).

Method II:
Reset by holding B button for 3 sec. after connecting mains voltage to the Switch

Eternity

Hm, after several re-boots and PTP all seems to work again....


Will do a better check tomorrow

Fire69

I had the same problem with a FGS-212.
Apparently the switch type gets reset from pulse to toggle...  I've had it happen twice this week.

Maybe something @caseda can have a look at?

caseda

whoo, i feel special now.  

i don't think @Eternity's issue is the same issue, it's more that homey's z-wave chip lost the connection to FGS-222, most of the time will fix itself in time or reboot.

but if this is the issue (at least it's for you @Fire69 an issue that needs fixing),
i first need to know if there is something that could trigger it, i don't think it will happen just out of nowhere.
did the type change in homey's settings as well?
did it happen on a certain moment.?
did it start happening after a certain (homey) update?

and some more info would also be nice, like homey's FW you are on now and app version

Fire69

caseda said:

whoo, i feel special now.  

i don't think @Eternity's issue is the same issue, it's more that homey's z-wave chip lost the connection to FGS-222, most of the time will fix itself in time or reboot.

but if this is the issue (at least it's for you @Fire69 an issue that needs fixing),
i first need to know if there is something that could trigger it, i don't think it will happen just out of nowhere.
did the type change in homey's settings as well?
did it happen on a certain moment.?
did it start happening after a certain (homey) update?

and some more info would also be nice, like homey's FW you are on now and app version

 I do think it's the same issue, because of this remark

Eternity said:

 *nor* via the actual wall switch!

I had the same thing.  Because it's set as a toggle switch, when you push the switch it turns off, but automatically turns back on when you release the switch.

caseda said:

but if this is the issue (at least it's for you @Fire69 an issue that needs fixing),
i first need to know if there is something that could trigger it, i don't think it will happen just out of nowhere.
did the type change in homey's settings as well?
did it happen on a certain moment.?
did it start happening after a certain (homey) update?

and some more info would also be nice, like homey's FW you are on now and app version

The switch type was shown correctly in the device settings, so I had to change it to toggle, then save, then change to pulse and save again.
Not sure about a specific moment, it's a switch that's not used on a daily basis.
I've had it the beginning of the week when I was still on 0.10.3 and then the day (or day after) I was on 0.10.7.
Fibaro app is 1.0.16.

caseda

the state will still change even if the switch type is in momentary mode instead of its default toggle mode.
he probably didn't just toggle it just once (most people do it twice if they notice that it doesn't respond), so that definitely changes the state inside homey, if it doesn't that means the connection to homey was lost.

EDIT:
we actually don't even know if he even needed to change the type, if he has a toggle switch attached to it

The switch type was shown correctly in the device settings, so I had to change it to toggle, then save, then change to pulse and save again.

if the switch type inside homey is still the proper one then it's not caused by homey,
it only sends the parameter value when a setting of the parameter was changed from previous state (just like you told us you first need to change the setting, save, then set it back and save again)
it won't happen just on its own.

and it's not a full reset of the module (the only thing homey also could do), that will make the module completely unresponsive.

So i think it's your module itself that loses it's parameter(s), maybe you can try to change any of the other settings and see if they revert back in due time to it original state, if it does, you can almost say for certain it's the module itself.

Fire69

caseda said:

So i think it's your module itself that loses it's parameter(s), maybe you can try to change any of the other settings and see if they revert back in due time to it original state, if it does, you can almost say for certain it's the module itself.

Not much to change except for the Auto Off Timer, but that rather annoying to test over several days, my kids use that light when doing their homework 

I just read back the thread and saw if was OK for Eternity after some PTP's (missed that post earlier...)

I'll see if it happens again, I'll do some more testing then.

caseda

@Fire69 ;
then your kids lack learning skills  if not used daily (or just still young)

and true that for not much to change, just switch the switch out for a toggle switch  then you won't have the problem anymore

Fire69

caseda said:

@Fire69 ;
then your kids lack learning skills  if not used daily (or just still young)

Both 

caseda said:

and true that for not much to change, just switch the switch out for a toggle switch  then you won't have the problem anymore

I hate toggle switches!  I replaced them all for a good reason 

Eternity

Guys, did some testing and ... I don't have a clue what's wrong...

I am on firmware 10.10.7 and Fibaro App v1.0.16 (so, both latest releases) and have several 222's in my house. In this situation a 222 is used to switch 2 individual lights in my bathroom on the second floor in my house. Homey is located on the ground floor. This setup has been working for weeks, after including the 222's sucessfully. I have disabled FLOWS that control the relay, just to make sure nothing else is confusing the setup.

The relay is mounted behind a double momentary switch (so, pressing it will automatically return the switch again to the most outside position, the relay S1 is set to 'pulse schakelaar' and *not* 'tuimel schakelaar'.

- in Chrome altering the relay does not work
- in CHrome i set the S1 to the other operating mode, saved and returned the pulse mode and saved
- the lights still can't be operated with the relay in Chrome

- if i use the wall switch, I can switch both lights ON, but OFF does no longer work
- the state of the relay is - however -  reported back to Homey correctly

- after a time out (set to 3000) I see the correct status in Chrome.
- if I use the wall switch, I can switch both lights ON
- Chrome reposrt the correct status
- I can't use the Chrome interface *NOR* the wall switch to turn the lights OFF
- I have to wait till the timer switched them off...
- I have disabled the auto-switch off timer; still can't use Chrome or the wall switches to control the lights






 

Eternity

Best to remove and re-include the relay, I guess...

caseda

@Eternity
Just noticed the description in the settings is wrong of "auto off"
but that's not the reason though.. the way you have it now should work like you want it too

how the parameter really works:

Auto off relay after specified time, with the possibility of manual override - immediate Off after button push.
Default value: off
Available settings:
off - manual override disabled. After single button push the relay turns on and automatically turns off after specified time.
on - manual override enabled. After single button push the relay turns on and automatically turns off after specified time. Another button push turns the relay off immediately.

maybe something changed around with this and that setting works the other way around (off = enabled, on = disabled)
so maybe you can try to turn off this checkbox and see if it still doesn't turn off when you press the button for the second time.

Eternity

Just double checkin'

Which Fibaro to pick as the 222:

caseda

Hover your mouse over the name, it will show you the full name (Fibaro Double Relay 2)

but even if you choose the wrong one, it will auto select the right driver for you, the selection is just needed for the "learn mode" if you need it, which is chosen by the type you select here.

Eternity

Thnx @caseda ;
 
I find the names a bit confusing, but I picked the 2nd from the 2nd row. Included nicely, but I still get weird behavior (Chrome doesn't control the switch, but I can update settings...).

 Will PTP and restart the Fibaro App 

viktor

Having probs here to pair one fibaro door window sensor, pretty old firmware, 2.1. Any suggestions?

caseda

@viktor ;
little bit more information please

1. Homey's FW
2. Apps' version
3. describe the problem you encouter

viktor

  

0.10.7
1.0.16
Interview timeout. 

Reseted, removed 1000 times, no luck.

caseda

@viktor ;
on which step does it timeout (the last step that is shown before timeout is given)

Eternity

My 222 is working again. After a couple of power cycles,.... bingo.
Weird, but happy that is is working again.

I have a feeling that the 222 was not updated, after altering the settings. I saw that the lights switched off automatically after 5 seconds (I had set that previously for testing purposed) and after increasing the value to 3000 and saving, it still switched off after 5 seconds . A reboot did the trick...

caseda

@Eternity ;
must have happend a miss communication between the FGS-222 and homey, otherwise i'm not sure what could cause this.

And names used are the names that are specified by Fibaro themselves they aren't just "sucked out of my thumb"
FGS-221 = Fibaro Double Relay (the previous version) 
FGS-222 = Fibaro Double Relay 2
FGS-223 = Fibaro Double Switch 2 (its a 2 even though there was never a v1...)

They are all specified in the read-me (app description), type numbers combined with their Fibaro Official Name, if you just want to be sure which 1 is which

Eternity

@caseda ;

I am still messing around with the FGS-222. I even checked the order I placed to see if a have the correct relay installed and in my wall. It is a "FIB_FIBEFGS-222". So, that should be OK.

The wall switches work, but the Chrome interface does not work. I can slide the on-screen button, nothing happens. However, if I manually press the wall switch, the Chrome interface gets updated!!!

So, the 222 does communicate with Homey, but the interface (and the flows with this relay) don't work anymore. The worked fine in a previous firmware.

caseda

ah i think i found the issue, i'll have to test it if my guess is right.. i can only test it when i get home this evening, but i'll change the SET parser already so if you (or someone else) wants to test it you can.

there is some more untested code in there for the FGD-211, FGD-212 FGS-213 & FGS-223 so be careful if you have one of those

EDIT: i have not found the issue yet... will keep you posted when i have tested more @ home why set doesn't work, if it doesn't for you, then it won't for me as well
i have a small feeling.. but i don't hope so, many devices would have the issue then as well.

Eternity

Thanks @caseda ;;

Happy bug hunting!

PS
Just checked; my 2 other FGS-222's are not working either. The wall switches *do* work, controlling them via Homey doesn't. The actual / physical status does get updated.

caseda

@Eternity ;;
Hmm, so weird that yours are not working, just tested mine and they are working fine.

what association group settings are being set in your fgs-222's
and if you switch in homey, close the card and open it again, does the state go back to the previous state?
and other z-wave devices do work?

Eternity

Guess what... it is working again...; I can switch the 222's via the Homey web  interface again (desktop and smartphone).

It is weird and not reproducible, let's hope it stays working.

caseda

Great that it is working, let's hope it stays that way

Eternity

Back to the same weird behavior, after a z-wave reset. S1 won't switch off... Will PTP

Sorry for cross posting. After doing a Google search I found this old thread. Seems a couple of PTP's might help.