New Fibaro Switch FGS-223 is driving me nuts

smee204 · January 7, 2017, 1:45pm

I have just checked and I am seeing the same as @vossivossi, it is only using it for the GET not the SET.

chris · January 7, 2017, 1:48pm

Ok- thanks - at least it’s consistent. I’ve had a look at the code - I need to think it through a little more but I’ll likely make a change to try at some stage - probably later tonight, but let’s see how it goes as I’ve been travelling for the past 24 hours so without much sleep…

smee204 · January 7, 2017, 1:53pm

I think I have spotted the bug in the code. If I can work out how to get the dev environment setup I will make a change and test it!

chris · January 7, 2017, 1:54pm

I know what is stopping it working - the question is how to solve it in a way that is compliant to the spec since there are some specific requirements on how this is used.

chris · January 7, 2017, 2:03pm

Please can you post the XML for the new FGS223 (@smee204), and also for the Qubino (@vossivossi). I want to check that the information ties in with the slightly complex conditions imposed on this in the standards.

smee204 · January 7, 2017, 2:21pm

This is the FGS223.
node9.xml (30.5 KB)

chris · January 7, 2017, 4:49pm

I’ve made a change, but I’m not sure it will work for you yet. Since this only affects group 1, and there are other problems preventing you changing group 1, this change may not actually do anything. If you exclude the device and add it back it might work. Make sure you keep a log so we can see what happened during the initialisation if it didn’t work.

vossivossi · January 7, 2017, 7:56pm

Sure, here is the Qubino XML-File.
node101.xml (24.9 KB)

Seaside · January 18, 2017, 9:13pm

@chris
I recently got an FGS-213 to use to monitor my floor heating, I’ve noticed some stuff were missing.
For openhab2 I’ve updated the database for the Single switch 2 FGS-213 the same updates should probably be done for FGS-223 (if they are correct)

Added the Sensor_power command class and added the meter_reset, please review when you have the chance.

Regards, S

sihui · February 6, 2017, 5:45pm

Are those issues above solved? @Lyve, @Woutch, @ossostborn?
I’m thinking about buying three of those devices and don’t like to burn my money
Thx.

Woutch · February 6, 2017, 7:55pm

Hello @sihui,

I can confirm that the input for the scene value now works. But I’m not able to test it at the moment.

For the rest, I have no issue with my FGS223, but I have only one in use now driving 4 LED spots.

If you need more info, please ask!

Best regards,

Wouter

sihui · February 6, 2017, 8:02pm

Thanks a lot!

vossivossi · February 17, 2017, 10:27pm

Which version (OH2 and Zwave binding) do you use? The official 2.0 packages?

Woutch · February 18, 2017, 9:24am

Hello @vossivossi,

I’m followoing the snapshots for openhab 2. And update around every week / 2 weeks.

Last update was from yesterday I think

vossivossi · February 18, 2017, 12:51pm

Thank you for this information. So I should also move from the release version to snapshot. Do you download it from cloudbees? (As I am running OH on Windows I need to install and update manually).

vossivossi · February 18, 2017, 11:41pm

@chris:
I also can confirm that the Fibaro FGS223 now works correctly (reporting correctly the different endpoints for Switch1 and Switch2).
BUT: The Qubino ZMNHBD is still NOT working (I tested tonight with Z-Wave binding build 2.1.0.201702181609). I excluded and freshly reincluded 2 of the devices to be sure. The results:

When only the lifeline association is set, no reporting is done to endpoints 1 and 2 (neither for Switch 1/2 nor Power(Watts)1/2).
Even when the association groups for Switch binary or Basic On/Off are set (or both, also tested), NO update comes to the controller for Switch 1/2.
When the assocation groups for power reporting are set, the Power Consumption (Watts) is reported correctly for both endpoints separately(!)

Is there a chance to also get the status reporting of the switches correctly? I have moren than 10 of them installed and can provide any kind of debug log if you tell me what you need. Thanks for your help!

Woutch · February 21, 2017, 8:28am

Hello @vossivossi

Im using this script:

github.com

xsnrg/OpenHAB2-tools/blob/master/makeHAB

#!/bin/bash
#
# This script will update your OpenHAB 2 installation.
# The script assumes that the OpenHAB 2 is already installed.  Please shut it down and then run the script
# If OpenHAB 2 is not already installed, create the directories ahead of time, and it will install OpenHAB 2
#
# This script will also update or install Smarthome Designer if desired.  Please make sure your work is saved
#  before updating.
#
# v2.3 updated for OpenHAB version number changes
# v2.2 updated for OpenHAB version number changes
# v2.1 some files in userdata/etc need to be removed to support updates to karaf
# v2 Greatly simplified for the new OpenHAB2 Karaf online distribution
# v1.1 Jim Howard
#

#The SNAPSHOT version to pull from cloudbees
vHAB=2.3.0
# The location for archive downloads
DOWN="/opt/DOWN"

This file has been truncated. show original

Running on Debian linux.

Best regards

andreasBCN · February 26, 2017, 11:42pm

Hi Nils,
I have now spent a week trying to get my Fibaro FGS-223 Switch to work with OpenHAB2 on my MacBook Air with UZB stick. I tried to add it through Paper UI on openHAB2 and when I do so, I see the UZB stick flashing blue. Clicking the B-button 3 times on the FGS-223 should usually start the inclusion process, but I only hear the relais click three times (and switch the light), but it does not do anything on openHAB. I have already excluded the security feature for the inclusion process in HABmin. I really don’t know if this is a problem with the FGS 223 or with my openHAB configuration or with the UZB stick. In principle on the Mac with the UZB stick everything looks fine - except for that it does not receive any signal from the FGS-223. I have already reset the FGS 223 various times, but that did not change anything. The Fibaro support team seems tu have no idea. I wonder if you could help me understand the problem?

Please find below the log.

Best regards and many thanks in advance!

Andreas

ZWAVE Log

05:26:25.457 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/tty.usbmodemFA131’
05:26:25.503 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
05:26:25.507 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - Update networkKey
05:26:25.518 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
05:26:25.519 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
05:26:28.669 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 1: Node found
05:26:28.670 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller using Controller API
05:26:28.670 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller is Primary Controller
05:26:28.670 [INFO ] [age.SerialApiGetInitDataMessageClass] - ------------Number of Nodes Found Registered to ZWave Controller------------
05:26:28.670 [INFO ] [age.SerialApiGetInitDataMessageClass] - # Nodes = 1
05:26:28.671 [INFO ] [age.SerialApiGetInitDataMessageClass] - ----------------------------------------------------------------------------

23:52:16.180 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - Starting ZWave inclusion scan for zwave:serial_zstick:0ce9f183
23:52:16.181 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller start inclusion - mode 2
23:52:16.182 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Setting controller into INCLUSION mode, highPower:true networkWide:true.
23:52:16.182 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
23:52:16.182 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
23:52:16.186 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A C1 01 70
23:52:16.186 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A C1 01 70
23:52:16.189 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A 01 01 00 00 B2
23:52:16.191 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
23:52:16.191 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 4A 01 01 00 00 B2
23:52:16.191 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 4A 01 01 00 00 B2
23:52:16.192 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 01 00 00
23:52:16.192 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: Learn ready.
23:52:16.192 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInclusionEvent
23:52:16.193 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=C1 01
23:52:16.193 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 01 00 00
23:52:16.194 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=AddNodeToNetwork, callback id=0, expected=AddNodeToNetwork, cancelled=false transaction complete!
23:52:16.194 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
23:52:16.195 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 8ms/169ms.
23:52:46.184 [DEBUG] [ve.internal.protocol.ZWaveController] - Stopping inclusion timer.
23:52:46.185 [DEBUG] [ve.internal.protocol.ZWaveController] - Ending inclusion mode.
23:52:46.185 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.
23:52:46.185 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
23:52:46.186 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
23:52:46.186 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller end inclusion
23:52:46.186 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 05 01 B4
23:52:46.186 [DEBUG] [ve.internal.protocol.ZWaveController] - Stopping inclusion timer.
23:52:46.186 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 01 B4
23:52:46.187 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!
23:52:46.345 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A 01 06 00 00 B5
23:52:46.346 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
23:52:46.347 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 4A 01 06 00 00 B5
23:52:46.347 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 4A 01 06 00 00 B5
23:52:46.348 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 06 00 00
23:52:46.348 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: Done.
23:52:46.348 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInclusionEvent
23:52:46.349 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=05 01
23:52:46.350 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 06 00 00
23:52:46.350 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=AddNodeToNetwork, callback id=0, expected=AddNodeToNetwork, cancelled=false transaction complete!
23:52:46.350 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
23:52:46.351 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 164ms/169ms.

sihui · February 27, 2017, 5:57am

I bought one of those devices two weeks ago and I can confirm that it works fine with openHAB2 (RPi, Zwave.me USB stick)

You should not hear the relay clicking while pressing the B-Button three times! Either the device is faulty or maybe you did not reset the device correctly (I also had to reset the FGS223 before inclusion worked).

Reset: Apply power, hold the B-button until the yellow light turns on, while the yellow light is on (that is only the case for 2 or 3 seconds), release the button and click it again once. After successful reset the red light comes on for some seconds.
Then try the inclusion again …
BTW, it is recommended to use HABmin for dealing with zwave devices, it is specifically designed for that.

vossivossi · February 27, 2017, 7:32am

I also spent several days to sort out the issues with these devices and OH2. It now works.
Make sure that you use the inclusion function from within OH2 (worked for me with both Paper UI and Habmin) when your Z-Wave stick is connected. I had trouble when I included the devices first decentrally with my Aeon Z-Stick5 and then started OH2, as in these cases the different endpoints were never usable.
Additionally I had to add the association group for lifeline to the OH controller (I did this with Habmin). Then it worked for me.