Fibaro FGS223 is not working well Topic is solved

Please use template to report bugs and problems. Post here your questions when not sure where else to post
Only for bugs in the Domoticz application! other problems go in different subforums!
Forum rules
Before posting here, make sure you are on the latest Beta or Stable version.
If you have problems related to the web gui, clear your browser cache + appcache first.

Use the following template when posting here:

Version: xxxx
Platform: xxxx
Description:
.....

If you are having problems with scripts/blockly, always post the script (in a spoiler or code tag) or screenshots of your blockly

If you are replying, please do not quote images/code from the first post
User avatar
rolandbreedveld
Posts: 37
Joined: Wednesday 09 March 2016 12:25
Target OS: Raspberry Pi
Domoticz version: stable
Contact:

Fibaro FGS223 is not working well

Postby rolandbreedveld » Saturday 03 September 2016 14:43

my Fibaro FGS223, Domoticz recognise it as "FIBARO System Unknown: type=0203, id=1000"
is not working well, on the Stable version.
After installing the latest beta, most of the functionality, like switching and power measurement is working after using the Z-Wave control panel.
but when creating an Activity the switch Device (input) isn't recognized, for both channels.
(lights are switching on, also recognized by Domoticz)
also the setup menu of the FGS223 is limited to trhe "3001 Protection value"
Domoticz - FGS223 communication feels also much, much slower than al my other devices.
Using beta 3.5597

In the Z-Wave control panel I see lots of messages like these:
2016-09-03 15:47:05.800 Error, Node012, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-09-03 15:47:05.800 Always,
2016-09-03 15:47:05.800 Always, Dumping queued log messages
2016-09-03 15:47:05.800 Always,
2016-09-03 15:47:05.801 Always,
2016-09-03 15:47:05.801 Always, End of queued log message dump
2016-09-03 15:47:05.801 Always,
2016-09-03 15:47:21.326 Error, Node012, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-09-03 15:47:21.326 Always,
Raspberry Pi2+3 | P1 SmartMeter | Z-Wave Razberry 2.0 | 4 Greenwave devices | FIBARO FGS223 +FGRM222 | Aerotec MultiSensor 6 | 2 x Gembird Siver-Shield with sispmctl | Logitech Harmony Hub | FritzBox
Interface to 123Solar + PowerOne 3.0 and SMA SB1200

User avatar
gizmocuz
Posts: 7699
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi
Domoticz version: beta
Location: Top of the world
Contact:

Re: Fibaro FGS223 is not working well

Postby gizmocuz » Saturday 03 September 2016 17:47

You have to use the beta version from yesterday, its working there, got two myself
switch ID's ending on 01 and 03 are switch 1 and 2 (fibaro logic)
First test in the devices tab, if that works (you have the correct switch (do not use the level switches)), then add them to the system
Quality outlives Quantity!

User avatar
rolandbreedveld
Posts: 37
Joined: Wednesday 09 March 2016 12:25
Target OS: Raspberry Pi
Domoticz version: stable
Contact:

Re: Fibaro FGS223 is not working well

Postby rolandbreedveld » Saturday 03 September 2016 18:22

Hi gizmocuz
I use the latest beta.
That's right using the 01 and 03 work as switch 1 and 2,
These are working, also the power measurement, but some slower than my other devices.

I'm working with Scenes, and when I try to ad the input swith as "Activation Devices" it wont recognize, and show the timeout
perhaps because it's slower ?
Raspberry Pi2+3 | P1 SmartMeter | Z-Wave Razberry 2.0 | 4 Greenwave devices | FIBARO FGS223 +FGRM222 | Aerotec MultiSensor 6 | 2 x Gembird Siver-Shield with sispmctl | Logitech Harmony Hub | FritzBox
Interface to 123Solar + PowerOne 3.0 and SMA SB1200

User avatar
gizmocuz
Posts: 7699
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi
Domoticz version: beta
Location: Top of the world
Contact:

Re: Fibaro FGS223 is not working well

Postby gizmocuz » Saturday 03 September 2016 19:54

That is correct, i find them a bit slower as well.
Maybe try to include them non-secure ?

I expect them to word as learning device for a scene... never tried it... i use other remotes to activate scenes
But you should receive the changes from on to off, so it should work (in theory)
Quality outlives Quantity!

User avatar
rolandbreedveld
Posts: 37
Joined: Wednesday 09 March 2016 12:25
Target OS: Raspberry Pi
Domoticz version: stable
Contact:

Re: Fibaro FGS223 is not working well

Postby rolandbreedveld » Sunday 04 September 2016 12:22

Hi gizmocuz
I add them unprotected, I replaced the Scenes by an event
(if licht = on, put some other lichts on, etc)
Switching it from Domoticz is super fast, also the events, the same as using a scene.
but switching it by the switch in the 223, directly switches the light connected to the 223, but recognition by Domoticz takes sometimes 60 seconds.
My other (older type Fibaro's) are super fast.
Perhaps because the 223 isn't in the Domotics library, if so, can I provide you info for adding it, or do some debugging ?
In the logging I see a lot of the 223:
OpenZWave: Received timeout notification from HomeID: 3488259009, NodeID: 12 (0x0c)
Device is in the neighbourhood of the Pi and a lot of other devices
I see a difference in protocol version between my older Fibaro's en the new 223:
Example: an old one: Library:3 / Protocol 5.52 / Application 25.25
the new FGS-223 : Library:3 / Protocol 4.05 / Application 3.02
ps running Version: 3.5604 now
Is it possible to test with a longer timeout periode?
Last edited by rolandbreedveld on Sunday 04 September 2016 13:49, edited 1 time in total.
Raspberry Pi2+3 | P1 SmartMeter | Z-Wave Razberry 2.0 | 4 Greenwave devices | FIBARO FGS223 +FGRM222 | Aerotec MultiSensor 6 | 2 x Gembird Siver-Shield with sispmctl | Logitech Harmony Hub | FritzBox
Interface to 123Solar + PowerOne 3.0 and SMA SB1200

User avatar
gizmocuz
Posts: 7699
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi
Domoticz version: beta
Location: Top of the world
Contact:

Re: Fibaro FGS223 is not working well

Postby gizmocuz » Sunday 04 September 2016 13:39

Update to the latest beta, the 223 is already in domoticz.
Maybe your switch is just too far away ?
Quality outlives Quantity!

User avatar
rolandbreedveld
Posts: 37
Joined: Wednesday 09 March 2016 12:25
Target OS: Raspberry Pi
Domoticz version: stable
Contact:

Re: Fibaro FGS223 is not working well

Postby rolandbreedveld » Sunday 04 September 2016 13:52

Hi gizmocuz

I tested with the latest one, which is availiable,
distance is verry close, and a 3 devices close to the 223.
I saw the 223 xml file, but on domotics it said :
FIBARO System Unknown: type=0203, id=1000
whats the reason of that ?
is it possible to test with a longer timetout ?
Raspberry Pi2+3 | P1 SmartMeter | Z-Wave Razberry 2.0 | 4 Greenwave devices | FIBARO FGS223 +FGRM222 | Aerotec MultiSensor 6 | 2 x Gembird Siver-Shield with sispmctl | Logitech Harmony Hub | FritzBox
Interface to 123Solar + PowerOne 3.0 and SMA SB1200

User avatar
rolandbreedveld
Posts: 37
Joined: Wednesday 09 March 2016 12:25
Target OS: Raspberry Pi
Domoticz version: stable
Contact:

Re: Fibaro FGS223 is not working well

Postby rolandbreedveld » Sunday 04 September 2016 14:09

The timeouts are not to much, when switching the device from Domotics it's fast,
but reading a changed state takes a long time, sometimes 2 seconds sometimes 60 seconds
Raspberry Pi2+3 | P1 SmartMeter | Z-Wave Razberry 2.0 | 4 Greenwave devices | FIBARO FGS223 +FGRM222 | Aerotec MultiSensor 6 | 2 x Gembird Siver-Shield with sispmctl | Logitech Harmony Hub | FritzBox
Interface to 123Solar + PowerOne 3.0 and SMA SB1200

User avatar
gizmocuz
Posts: 7699
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi
Domoticz version: beta
Location: Top of the world
Contact:

Re: Fibaro FGS223 is not working well

Postby gizmocuz » Sunday 04 September 2016 19:33

What is the latest one ? Which version?
Quality outlives Quantity!

User avatar
rolandbreedveld
Posts: 37
Joined: Wednesday 09 March 2016 12:25
Target OS: Raspberry Pi
Domoticz version: stable
Contact:

Re: Fibaro FGS223 is not working well

Postby rolandbreedveld » Monday 05 September 2016 8:45

I saw the new Version: 3.5607 , Gizmocuz
same result, extreem slow on reading states, switching from Domoticz is fast.
sometimes a timeout in the logging but not frequently
After deleting and adding the device it's now recognized as:
FIBARO System FGS223 Double Relay
Raspberry Pi2+3 | P1 SmartMeter | Z-Wave Razberry 2.0 | 4 Greenwave devices | FIBARO FGS223 +FGRM222 | Aerotec MultiSensor 6 | 2 x Gembird Siver-Shield with sispmctl | Logitech Harmony Hub | FritzBox
Interface to 123Solar + PowerOne 3.0 and SMA SB1200

User avatar
rolandbreedveld
Posts: 37
Joined: Wednesday 09 March 2016 12:25
Target OS: Raspberry Pi
Domoticz version: stable
Contact:

Re: Fibaro FGS223 is not working well

Postby rolandbreedveld » Monday 05 September 2016 13:17

Hi gizmocuz
found something interesting
The problem occurs only on channel 2
(in my case 00000C03)
channel 1 (00000C01) is working fine
so I swithed the wires ;)
Raspberry Pi2+3 | P1 SmartMeter | Z-Wave Razberry 2.0 | 4 Greenwave devices | FIBARO FGS223 +FGRM222 | Aerotec MultiSensor 6 | 2 x Gembird Siver-Shield with sispmctl | Logitech Harmony Hub | FritzBox
Interface to 123Solar + PowerOne 3.0 and SMA SB1200

PVG555
Posts: 8
Joined: Sunday 01 May 2016 18:02
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Fibaro FGS223 is not working well

Postby PVG555 » Saturday 10 September 2016 17:23

Mine doesn't work at all operating it from Domoticz.
Switches are *01 and *02, unlike 01 and 03 as gizmocus said. I can switch them manually with the switch, no problem. However Domoticz does not get a state change if I do it manually and also switching from domoticz is not working at all. Don't hear the relays clicking...so completely inoperable.

I'm on the latest Beta and tried a second FGS-223 to see if it is not faulty... No change.

Node is recognised as FGS-223 double switch relay.

Anything I'm overseeing or just have to wait for a new update?

Thanks in advance,
P

Bart4Domoticz
Posts: 1
Joined: Sunday 11 September 2016 11:49
Target OS: Linux
Domoticz version:
Contact:

Re: Fibaro FGS223 is not working well

Postby Bart4Domoticz » Sunday 11 September 2016 13:51

I have the same problem.
I Have looked a little bit further.
When i switch in the OZW control panel it works fine.
In domoticz it wil not switch.

When i look in the log i see this when i switch form domoticz:
2016-09-11 13:37:08.459 Info, Node069, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Level - 0 - 1 - �

en when i switch from de OZW control panel ik see this:

2016-09-11 13:37:46.412 Info, Node069, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True

So you can see there is een difference in command class.

I run domotic on a debian system. Update to V3.5634

Bart

User avatar
gizmocuz
Posts: 7699
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi
Domoticz version: beta
Location: Top of the world
Contact:

Re: Fibaro FGS223 is not working well

Postby gizmocuz » Sunday 11 September 2016 21:13

You should not have the multilevel switch when you use the latest beta version and exclude/include the node again.

This because in the latest domoticz version (the binary distribution that is, if you build from source, you have to update ozw too)
The multilevel is blocked.

Code: Select all

    <!-- COMMAND_CLASS_SWITCH_MULTILEVEL. This class is in the list reported by the device, but it does not respond to requests -->
    <CommandClass id="38" getsupported="false"/>


At least... i dont have them... could be because i removed them in the configuration file as well. (also mentioned here on the forum)

But.. i made a patch for these 213/223 relays in beta #5637

Also note, this only works when using openzwave, it will not work when using the razberry hardware. (a razberry in combination with openzwave works)

People reporting that they see "FIBARO System Unknown: type=0203, id=1000" are NOT using the latest beta (@rolandbreedveld)

Beta's should be available now or very shortly
Quality outlives Quantity!

Sieme
Posts: 5
Joined: Saturday 10 September 2016 11:53
Target OS: Raspberry Pi
Domoticz version: Beta
Location: Holland
Contact:

Re: Fibaro FGS223 is not working well

Postby Sieme » Sunday 11 September 2016 21:25

i just updated to latest beta version v3.5637 and can confirm its working now (for my FGS223)

thanks gizmocuz for the fix :D

User avatar
gizmocuz
Posts: 7699
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi
Domoticz version: beta
Location: Top of the world
Contact:

Re: Fibaro FGS223 is not working well

Postby gizmocuz » Sunday 11 September 2016 21:38

Yes, well fix... it is another 'special' rule i applied specifically for this sensor.
But you should not have the multi level sensors at all before... did you excluded the sensor with the previous beta ?
It also advertise that it contains a heat sensor... hmmmm
Glad it's working
Quality outlives Quantity!

Sieme
Posts: 5
Joined: Saturday 10 September 2016 11:53
Target OS: Raspberry Pi
Domoticz version: Beta
Location: Holland
Contact:

Re: Fibaro FGS223 is not working well

Postby Sieme » Sunday 11 September 2016 21:50

maybe they made 1 chip that can do it all?
and depending on what is connected to it, corresponding advertised values start working?

i understand that it is a "not so generic fix", but it seems to do the job.

I found the rule for the 213 and 223 at github :)
as i was searching for the openzwave cpp to see where the command was handled.
I then found out that 3 minutes before i found it, there was a rule made for it by you 8-)

User avatar
gizmocuz
Posts: 7699
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi
Domoticz version: beta
Location: Top of the world
Contact:

Re: Fibaro FGS223 is not working well

Postby gizmocuz » Sunday 11 September 2016 21:53

My previous fix/patch was nicer, but caused issued with fibaro roller shutters...
Always check when needing to switch on/off, if a binary sensor was available on the node, and if so, use the binary sensor.
This also worked on the special rule for the aeotec above the new patch...
Would have been great if all manufacturers implemented things the same....
Maybe as the zwave specifications are open now, there will be more knowledge about the inner workings
Quality outlives Quantity!

tohn
Posts: 28
Joined: Saturday 15 November 2014 18:30
Target OS: Raspberry Pi
Domoticz version: Beta
Contact:

Re: Fibaro FGS223 is not working well

Postby tohn » Sunday 11 September 2016 22:25

The new beta fixed my (Same) problem with FGS213 also!

Thanks!

tohn
Posts: 28
Joined: Saturday 15 November 2014 18:30
Target OS: Raspberry Pi
Domoticz version: Beta
Contact:

Re: Fibaro FGS223 is not working well

Postby tohn » Sunday 11 September 2016 22:52

Some other changes ? Beq after I while its seems that it cant communicate with the z-wave usb stick anymore..
It works for 10 min after upgrade to the new beta, and the FGS213 was working.. then all stoped working

Log :
Spoiler: show
2016-09-11 22:43:21.207 Always, OpenZwave Version 1.4.340 Starting Up
2016-09-11 22:43:21.207 Info, Setting Up Provided Network Key for Secure Communications
2016-09-11 22:43:21.208 Info, mgr, Added driver for controller /dev/ttyUSB22
2016-09-11 22:43:21.208 Info, Opening controller /dev/ttyUSB22
2016-09-11 22:43:21.208 Info, Trying to open serial port /dev/ttyUSB22 (attempt 1)
2016-09-11 22:43:21.211 Info, Serial port /dev/ttyUSB22 opened (attempt 1)
2016-09-11 22:43:21.211 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2016-09-11 22:43:21.211 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2016-09-11 22:43:21.211 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2016-09-11 22:43:21.212 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2016-09-11 22:43:21.212 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2016-09-11 22:43:21.212 Detail,
2016-09-11 22:43:21.212 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2016-09-11 22:43:22.212 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-09-11 22:43:22.213 Always,
2016-09-11 22:43:22.213 Always, Dumping queued log messages
2016-09-11 22:43:22.213 Always,
2016-09-11 22:43:22.213 Always,
2016-09-11 22:43:22.213 Always, End of queued log message dump
2016-09-11 22:43:22.213 Always,
2016-09-11 22:43:22.213 Detail, contrlr, Removing current message
2016-09-11 22:43:22.214 Detail, contrlr, Notification: Notification - TimeOut
2016-09-11 22:43:22.214 Detail,
2016-09-11 22:43:22.214 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2016-09-11 22:43:23.214 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-09-11 22:43:23.215 Always,
2016-09-11 22:43:23.215 Always, Dumping queued log messages
2016-09-11 22:43:23.215 Always,
2016-09-11 22:43:23.215 Always,
2016-09-11 22:43:23.215 Always, End of queued log message dump
2016-09-11 22:43:23.215 Always,
2016-09-11 22:43:23.215 Detail, contrlr, Removing current message
2016-09-11 22:43:23.215 Detail, contrlr, Notification: Notification - TimeOut
2016-09-11 22:43:23.216 Detail,
2016-09-11 22:43:23.216 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2016-09-11 22:43:24.216 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-09-11 22:43:24.216 Always,
2016-09-11 22:43:24.217 Always, Dumping queued log messages
2016-09-11 22:43:24.217 Always,
2016-09-11 22:43:24.217 Always,
2016-09-11 22:43:24.217 Always, End of queued log message dump
2016-09-11 22:43:24.217 Always,
2016-09-11 22:43:24.217 Detail, contrlr, Removing current message
2016-09-11 22:43:24.217 Detail, contrlr, Notification: Notification - TimeOut
2016-09-11 22:43:24.218 Detail,
2016-09-11 22:43:24.218 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2016-09-11 22:43:25.218 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-09-11 22:43:25.218 Always,
2016-09-11 22:43:25.218 Always, Dumping queued log messages
2016-09-11 22:43:25.219 Always,
2016-09-11 22:43:25.219 Always,
2016-09-11 22:43:25.219 Always, End of queued log message dump
2016-09-11 22:43:25.219 Always,
2016-09-11 22:43:25.219 Detail, contrlr, Removing current message
2016-09-11 22:43:25.219 Detail, contrlr, Notification: Notification - TimeOut
2016-09-11 22:43:25.219 Detail,
2016-09-11 22:43:25.220 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2016-09-11 22:43:26.220 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-09-11 22:43:26.220 Always,
2016-09-11 22:43:26.220 Always, Dumping queued log messages
2016-09-11 22:43:26.220 Always,
2016-09-11 22:43:26.221 Always,
2016-09-11 22:43:26.221 Always, End of queued log message dump
2016-09-11 22:43:26.221 Always,
2016-09-11 22:43:26.221 Detail, contrlr, Removing current message
2016-09-11 22:43:26.221 Detail, contrlr, Notification: Notification - TimeOut


Return to “Bugs and Problems”

Who is online

Users browsing this forum: jeanpaulik and 3 guests