Fibaro Dimmer 2 S2 Status

Posted on
Sun Apr 08, 2018 2:16 am
colinpartridge offline
Posts: 373
Joined: Jan 13, 2014
Location: London, UK

Fibaro Dimmer 2 S2 Status

I have a newly installed Fibaro Dimmer 2 (firmware version 3.05) doesn't appear to be reporting the status of the second input switch S2 to Indigodomo. The status of s1 is reported immediately and also with scenes activated I'm getting a scene 26 ( reporting s2 in the event log). If I query the status of s2 manually then the status is updated as expected. Any ideas on how I can get the second input status updating correctly
Heres the Event log when the fibaro is being synced.

Code: Select all
Z-Wave                          Syncing - started for "119 - Kitchen dimmer"
   Z-Wave                          Syncing - retrieved module neighbors list: 4, 8, 9, 14, 24, 25, 29, 33, 35, 40, 53, 55, 60, 64, 75
   Z-Wave                          Syncing - assigning return route to "120 - 119 - Kitchen dimmer"
   Z-Wave                          Syncing - assigned return route
   Z-Wave                          Syncing - retrieved manufacture and model names: Fibaro System - 010F, Dimmer Switch (FGD212) - 01021000
   Z-Wave                          Syncing - retrieved protocol version 4.05, app version 3.05
   Z-Wave                          Syncing - retrieved class hierarchy: Routing Slave : Mulitlevel Switch : Dimmable Power Switch (04 : 11 : 01, base 26)
   Z-Wave                          Syncing - retrieved command classes: 20v1 85v1 86v1 71v1 8Ev1 56v1 98v1 59v1 5Av1 5Ev1 60v4 22v1 26v3 27v1 72v1 70v1 31v4 32v3 73v1 75v1 7Av1
   Z-Wave                          Syncing - retrieved encrypt commands: - none -
   Z-Wave                          Syncing - retrieved capabilities: routing, beaming, security
   Z-Wave                          Syncing - retrieved multi-endpoint types: 1:(11 : 01), 2:(11 : 01)
   Z-Wave                          Syncing - retrieved multi-endpoint classes: 1:[5E 20 86 26 85 59 8E 32 31 71], 2:[5E 20 86 26 85 59 8E]
   Z-Wave                          Syncing - retrieved group 1 associations: [1]
   Z-Wave                          Syncing - retrieved group 2 associations: [1]
   Z-Wave                          Syncing - retrieved group 3 associations: []
   Z-Wave                          Syncing - retrieved group 4 associations: []
   Z-Wave                          Syncing - retrieved group 5 associations: []
   Z-Wave                          Syncing - group 1 association to interface already exists (skipping)
   Z-Wave                          Syncing - group 2 association to interface already exists (skipping)
   Z-Wave                          Syncing - retrieved parameter 20 "Switch type" is 0 "Momentary"
   Z-Wave                          Syncing - retrieved parameter 28 "Enable scene commands" is true
   Z-Wave                          Syncing - retrieved parameter 23 "Enable double-click to full brightness" is true
   Z-Wave                          Syncing - retrieved parameter 9 "Power up to last known state" is true
   Z-Wave                          Syncing - retrieved parameter 26 "Enable 3-way switch mode" is false
   Z-Wave                          Syncing - retrieved parameter 1 "Minimum value" is 4
   Z-Wave                          Syncing - retrieved parameter 2 "Maximum value" is 99
   Z-Wave                          Syncing - retrieved parameter 7 "Local dim delta" is 1
   Z-Wave                          Syncing - retrieved parameter 8 "Local dim timer" is 5 * 10 milliseconds
   Z-Wave                          Syncing - retrieved parameter 5 "On/Off dim delta" is 1
   Z-Wave                          Syncing - retrieved parameter 6 "On/Off dim timer" is 1 * 10 milliseconds
   Z-Wave                          Syncing - retrieved parameter 50 "Immediate power threshold" is 10 %
   Z-Wave                          Syncing - retrieved parameter 52 "Periodic report delay" is 3600 seconds
   Z-Wave                          Syncing - complete

Posted on
Sun Apr 08, 2018 3:42 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Fibaro Dimmer 2 S2 Status

I'm not sure why it isn't updating, but the firmware version on yours is higher than some of the previous reports we've seen. Try turning on Indigo's Z-Wave debug logging checkbox via the Interfaces->Z-Wave->Configure... menu item, then toggle S2 a few times (pausing several seconds after each toggle). Copy/paste the Event Log window results into a reply so we can see what messages are being sent.

Image

Posted on
Sun Apr 08, 2018 4:02 pm
mclass offline
Posts: 312
Joined: May 13, 2015
Location: Melbourne, Australia

Fibaro Dimmer 2 S2 Status

I’m also experiencing this issue but with firmware version 2.2

I have located this thread
viewtopic.php?f=58&t=18165&start=15
and understood this issue had been addressed.
I’ll watch with interest for an outcome!

mclass

EDIT: Whoops - my note refers to a Fibaro double relay - not a dimmer. My apologies!

Sent from my iPhone using Tapatalk

Posted on
Mon Apr 09, 2018 1:23 am
colinpartridge offline
Posts: 373
Joined: Jan 13, 2014
Location: London, UK

Re: Fibaro Dimmer 2 S2 Status

The s2 switch doesn't appear to be sending any messages when locally pressed. I know the switch is working because when scene commands are enabled I'm getting the following message back
Code: Select all
Z-Wave Debug                    RCVD sceneActivateCmd: 01 0A 00 04 00 78 04 2B 01 1A 00 BD
   Z-Wave Debug                    . .  sceneActivateCmd: node 120, scene: 26
   Z-Wave                          received "120 - Kitchen dimmer" scene 26


and when I manually request the status of s2 the status is updated correctly
Code: Select all
Z-Wave Debug                    SENT requestDimmerStatus: 01 0D 00 13 78 06 60 0D 01 02 26 02 25 B7 47
   Z-Wave Watcher Debug            Raw command sent (Node 120): 01 0D 00 13 78 06 60 0D 01 02 26 02 25 B7 47 (True)
   Z-Wave                          sent "120 - Switch 2" status request


A quick google search revealed this post on a different platform..https://www.domoticz.com/forum/viewtopic.php?t=15156 so I'm not on my own. Very frustrating. Maybe I'll try a Aeotec dimmer to see if I can get a device that actually works as advertised.

Colin

Posted on
Mon Apr 09, 2018 3:06 am
howartp offline
Posts: 4559
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Fibaro Dimmer 2 S2 Status

The code you’ve quoted there, second, is for the outgoing request (“Raw command sent”).

If you’re not receiving a “Raw Command received” then it’s not sending one.

What associations are set - I wonder if Group 2 needs an association to Node 1? (Completely off top of my head)


Sent from my iPhone using Tapatalk Pro

Posted on
Mon Apr 09, 2018 3:16 am
howartp offline
Posts: 4559
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Fibaro Dimmer 2 S2 Status

Right, I’ve just read the manual. Always a useful place to start. :-)

Set param 25 to 0, if it isn’t already.

And set association for groups 4 and 5 to Node 1.

That’s the reporting config for Switch 2.


Sent from my iPhone using Tapatalk Pro

Posted on
Tue Apr 10, 2018 12:49 am
colinpartridge offline
Posts: 373
Joined: Jan 13, 2014
Location: London, UK

Re: Fibaro Dimmer 2 S2 Status

howartp wrote:
Right, I’ve just read the manual. Always a useful place to start. :-)

Set param 25 to 0, if it isn’t already.

And set association for groups 4 and 5 to Node 1.

That’s the reporting config for Switch 2.
Sent from my iPhone using Tapatalk Pro

Hi Howard
Confirmed that parameter 25 is set to 0
Here's whats happening.
.
Code: Select all
>s1 pressed<
Z-Wave Debug                    RCVD dimmerSetLevel: 01 09 00 04 08 79 03 20 01 00 A1
 Z-Wave Debug                    . .  dimmerSetLevel: node 121, endpoint None, value 0
 Z-Wave                          received "121 - Dimmable Load" status update is off
>s1 pressed again<
Z-Wave Debug                    RCVD dimmerSetLevel: 01 09 00 04 08 79 03 20 01 FF 5E
Z-Wave Debug                    . .  dimmerSetLevel: node 121, endpoint None, value 255
Z-Wave                          received "121 - Dimmable Load" status update is on

>s2 pressed< with no association g4,g5
nothing..
>s2 pressed< with association g4
Z-Wave Debug                    RCVD dimmerSetLevel: 01 09 00 04 08 79 03 20 01 FF 5E
Z-Wave Debug                    . .  dimmerSetLevel: node 121, endpoint None, value 255
Z-Wave                          received "121 - Dimmable Load" status update is on

Z-Wave Debug                    RCVD dimmerSetLevel: 01 09 00 04 08 79 03 20 01 00 A1
Z-Wave Debug                    . .  dimmerSetLevel: node 121, endpoint None, value 0
Z-Wave                          received "121 - Dimmable Load" status update is off


s2 pressed with scene commands active

Z-Wave Debug                    RCVD sceneActivateCmd: 01 0A 00 04 00 79 04 2B 01 1A 00 BC
  Z-Wave Debug                    . .  sceneActivateCmd: node 121, scene: 26
  Z-Wave                          received "121 - Dimmable Load" scene 26


When pressing s2 with group 4 associated with Indigodomo it is sending the same message as if you had pressed s1.
However with scene commands active it is sending the correct scene numbers, Scene 16 for s1 and scene 26 for s2. So I guess I'll have to use that rather than status.

Colin

Posted on
Tue Apr 10, 2018 1:13 am
howartp offline
Posts: 4559
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Fibaro Dimmer 2 S2 Status

Matt - can you explain the multi endpoints in the sync log in post 1 of this thread?

What are 11 and 01?

Peter


Sent from my iPhone using Tapatalk Pro

Posted on
Wed Apr 11, 2018 10:54 am
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Fibaro Dimmer 2 S2 Status

Unfortunately, the Fibaro's are extremely fickle to get configured so they send the information Indigo (or any central controllers) wants. And to top it off, they change the behavior all the time in different firmware versions making it a moving target. For the time being I'd suggest just using the scene capability and triggers that catch the scene command (don't try to use S2's device state).

Peter: 11 01 just means that the both endpoints are of class/type Mulitlevel Switch (0x11 higher level) and Dimmable Power Switch (0x01 more specific). Indigo just uses that to know that it can send dim state requests via command 0x26 to both endpoints.

Image

Posted on
Thu Apr 12, 2018 3:16 am
colinpartridge offline
Posts: 373
Joined: Jan 13, 2014
Location: London, UK

Re: Fibaro Dimmer 2 S2 Status

matt (support) wrote:
Unfortunately, the Fibaro's are extremely fickle to get configured so they send the information Indigo (or any central controllers) wants. And to top it off, they change the behavior all the time in different firmware versions making it a moving target. For the time being I'd suggest just using the scene capability and triggers that catch the scene command (don't try to use S2's device state).


Thanks Matt
The scene commands work just fine, so I'll stick with those.

Colin

Posted on
Sun Jan 31, 2021 12:24 pm
juntta offline
Posts: 143
Joined: Oct 13, 2014
Location: Finland

Re: Fibaro Dimmer 2 S2 Status

I'm struggling to get these S2 scenes to work. I have Fibaro Switches with similar setup (normal PIR, which output L' connected to S2 input and PIR power feed is fed from SX terminal of Dimmer 2). With Switch 2 this setup & scenes just work but not now when I try the same with Dimmer 2.

So I have Parameter 28 set 1 and Indigo server in association group 4 but no cigar - no scene events when PIR motion event fired. Any ideas? I attached my Dimmer2 device properties below but version seems to be the same 3.05 as some have reported earlier.

Code: Select all
Indigo Z-Wave Version: 7.5.0
Node ID: 99
Model: Dimmer Switch (FGD212)
Model ID: 01021000
Manufacturer: Fibaro System
Manufacturer ID: 010F
Protocol Version: 4.24
Application Version: 3.05
Model Definition Version: 2
Library Type: 3
Class Name: Dimmable Power Switch
Class Hierarchy: 04 : 11 : 01
Command Class Base: 26
Command Versions: 20v1 60v4 22v1 26v3 86v1 27v1 7Av1 72v1 8Ev1 70v1 71v1 32v3 73v1 75v1 56v1 98v1 59v1 31v4 5Av1 5Ev1 85v1
Encryption Status: Supported but not Enabled
Multi-Endpoint Types: 1:(11 : 01), 2:(11 : 01)
Multi-Endpoint Classes: 1:[5E 20 86 26 85 59 8E 32 31 71], 2:[5E 20 86 26 85 59 8E]
Multi-Instance Counts: - none -
Features: routing, beaming, security, energyMeter
Neighbors: 22, 90, 91, 92, 93, 94, 95, 96, 101, 105, 108, 114, 116, 118, 120, 121, 122
Associations: 1:[1] 2:[1] 3:[] 4:[1] 5:[]
Config Values: 1:1 2:99 5:1 6:0 7:1 8:1 9:1 50:10 20:0 23:1 52:3600 26:0 28:1

Posted on
Sun Jan 31, 2021 12:40 pm
juntta offline
Posts: 143
Joined: Oct 13, 2014
Location: Finland

Re: Fibaro Dimmer 2 S2 Status

Some debugging with Zwave watcher:

Code: Select all
   Z-Wave                          received "Varaston kattovalot" scene 16
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 0A 00 04 00 63 04 2B 01 10 00 AC
   Z-Wave                          received "Varaston kattovalot" scene 16
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 0A 00 04 00 63 04 2B 01 10 00 AC
   Z-Wave                          received "Varaston kattovalot" status update brightness 100
   Trigger                         Varaston kattovalo päälle (Dimmer 2 S1 ON)
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 09 00 04 00 63 03 26 03 63 D4
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 0C 00 04 00 63 06 31 05 04 22 01 32 B3
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 0C 00 04 00 63 06 31 05 04 22 01 32 B3
   Z-Wave                          received "Varaston kattovalot" scene 12
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 0A 00 04 00 63 04 2B 01 0C 00 B0
   Z-Wave                          received "Varaston kattovalot" status update is off
   Trigger                         Varaston kattovalo pois päältä (Dimmer 2 S1 OFF)
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 09 00 04 00 63 03 26 03 00 B7
   Z-Wave                          received "Varaston kattovalot" scene 13
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 0A 00 04 00 63 04 2B 01 0D 00 B1
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 09 00 04 00 63 03 20 01 00 B3
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 09 00 04 00 63 03 26 03 00 B7
   Z-Wave                          received "Varaston kattovalot" scene 16
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 0A 00 04 00 63 04 2B 01 10 00 AC
   Z-Wave                          received "Varaston kattovalot" status update is on
   Trigger                         Varaston kattovalo päälle (Dimmer 2 S1 ON)
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 09 00 04 00 63 03 20 01 FF 4C
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 09 00 04 00 63 03 26 03 63 D4
   Z-Wave                          received "Varaston kattovalot" scene 16
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 0A 00 04 00 63 04 2B 01 10 00 AC
   Z-Wave                          received "Varaston kattovalot" status update is off
   Trigger                         Varaston kattovalo pois päältä (Dimmer 2 S1 OFF)
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 09 00 04 00 63 03 20 01 00 B3
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 09 00 04 00 63 03 26 03 00 B7
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 0C 00 04 00 63 06 31 05 04 22 01 2C AD
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 0C 00 04 00 63 06 31 05 04 22 00 00 80
   Z-Wave Watcher Debug            Raw command sent (Node 99): 01 0A 00 13 63 03 32 01 00 25 82 12 (True)
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 10 00 04 00 63 0A 32 02 21 44 00 00 01 37 00 00 E1
   Z-Wave Watcher Debug            Raw command sent (Node 99): 01 0A 00 13 63 03 32 01 10 25 83 03 (True)
   Z-Wave Watcher Debug            Raw command received (Node 99): 01 0E 00 04 00 63 08 32 02 21 32 00 00 00 00 BD

Posted on
Sat Feb 06, 2021 5:06 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Fibaro Dimmer 2 S2 Status

Your Event Log is showing that Indigo is detecting the scene buttons:

Code: Select all
   Z-Wave                          received "Varaston kattovalot" scene 16
   Z-Wave                          received "Varaston kattovalot" scene 16
   Z-Wave                          received "Varaston kattovalot" scene 12
   Z-Wave                          received "Varaston kattovalot" scene 13
   Z-Wave                          received "Varaston kattovalot" scene 16
   Z-Wave                          received "Varaston kattovalot" scene 16

so it looks like it is working? Did you device Triggers based on those scene commands?

Image

Posted on
Sun Feb 07, 2021 12:11 am
juntta offline
Posts: 143
Joined: Oct 13, 2014
Location: Finland

Re: Fibaro Dimmer 2 S2 Status

matt (support) wrote:
Your Event Log is showing that Indigo is detecting the scene buttons:

Code: Select all
   Z-Wave                          received "Varaston kattovalot" scene 16
   Z-Wave                          received "Varaston kattovalot" scene 16
   Z-Wave                          received "Varaston kattovalot" scene 12
   Z-Wave                          received "Varaston kattovalot" scene 13
   Z-Wave                          received "Varaston kattovalot" scene 16
   Z-Wave                          received "Varaston kattovalot" scene 16

so it looks like it is working? Did you device Triggers based on those scene commands?
On S1 input scenes do work but on S2 input there should be 26, 22 and 23 and those cannot be triggered at the moment.

Posted on
Sun Feb 07, 2021 1:00 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Fibaro Dimmer 2 S2 Status

I see. From the manual I don't see any other parameters besides #28 which should enable scenes for both S1 and S2. I think you'll need to contact Fibaro support to see what they say.

Image

Who is online

Users browsing this forum: No registered users and 8 guests