FGS223 Timeouts

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
Plugin/Hardware: 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
borcon
Posts: 15
Joined: Thursday 05 January 2017 12:15
Target OS: Raspberry Pi
Domoticz version: BETA
Contact:

FGS223 Timeouts

Postby borcon » Tuesday 10 January 2017 21:00

Version: 3.6328 (BETA)
Platform: RaspberryPi3

I've got some issues with timeouts in z wave, since i have the 3x FGS223 included.
Without the FGS223, the zwave network has no timeouts.
I have currently 10x Fibaro Dimmer 2 and 3x Fibaro FGS223 included.

I switch the lights very often with scenes and since the FGS223, the scenes have some time delays up to 5-30 seconds.

From Domoticz log:
2017-01-10 19:33:20.719 OpenZWave: Received timeout notification from HomeID: 3681674579, NodeID: 6 (0x06)
2017-01-10 19:33:35.464 OpenZWave: Received timeout notification from HomeID: 3681674579, NodeID: 12 (0x0c)
2017-01-10 19:33:45.938 OpenZWave: Received timeout notification from HomeID: 3681674579, NodeID: 13 (0x0d)

From ozwcp log:
2017-01-10 19:51:38.770 Error, Node006, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-01-10 19:54:00.508 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)

Is this a problem from ozw?
Any ideas?

Thanks

ogroot
Posts: 9
Joined: Sunday 13 March 2016 23:49
Target OS: Raspberry Pi
Domoticz version:
Location: Netherlands
Contact:

Re: FGS223 Timeouts

Postby ogroot » Wednesday 11 January 2017 21:39

I noticed similar issue with qubino double relay switch. Recently there have been some code and config xml changes, due to notification problems with these double relay switches (multi instance).
Since these change I have frequent timeouts.....

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

Re: FGS223 Timeouts

Postby gizmocuz » Thursday 12 January 2017 13:10

ogroot wrote:I noticed similar issue with qubino double relay switch. Recently there have been some code and config xml changes, due to notification problems with these double relay switches (multi instance).
Since these change I have frequent timeouts.....


Please be specific.... code changes ? from domoticz or openzwave ? which changes ?
config changes ? from openzwave ? what changed ?
Quality outlives Quantity!

ogroot
Posts: 9
Joined: Sunday 13 March 2016 23:49
Target OS: Raspberry Pi
Domoticz version:
Location: Netherlands
Contact:

Re: FGS223 Timeouts

Postby ogroot » Thursday 12 January 2017 19:01

Hi gizmocuz,

The timeouts with 3 Qubino ZMNHBD1 switches, appeared after switching from Domoticz 3.4834 --> 3.6325 (both self compiled).
I updated to this version because the ZMNHBD1 has problem reporting switching wall button to domoticz, very similar to FGS223.
With version 3.4834 (and 3.6325) the ZMNHBD1 switches have following behavior:

Case 1: [ Q1 input/switch = OFF ]
Q2 input/switch change: off --> on is reported to domoticz
Q2 input/switch change: on --> off is reported to domoticz
Case 2: [ Q1 input/switch = ON ]
Q2 input/switch change: off --> on is reported to domoticz
Q2 input/switch change: on --> off is NOT ALWAYS reported to domoticz (+/- 70% of the cases it is not)

I upgraded to 3.6325, because I saw many similar reports and several (MultiInstanceAssociation ) changes in the Domoticz code base and OpenZwave config:

Other similar reports/issues:
https://github.com/OpenZWave/open-zwave/issues/880
https://github.com/OpenZWave/open-zwave/issues/862
https://github.com/OpenZWave/open-zwave/issues/857
https://github.com/OpenZWave/open-zwave/issues/857
https://github.com/Nico0084/open-zwave/commit/c49a955900af34589d808f584314694bee9bdc30
OZW Changes
I saw several MultiInstanceAssociation related changes. E.g.:
  • cpp/src/Driver.h
  • cpp/src/command_classes/MultiInstanceAssociation.cpp
  • cpp/src/command_classes/MultiInstanceAssociation.h
OZW Changes in config/qubino/ZMNHBDx.xml

Code: Select all

Added:
        <CommandClass id="37">
                <TriggerRefreshValue Genre="user" Index="0" Instance="1">
                        <RefreshClassValue CommandClass="37" RequestFlags="0" Index="0" Instance="2" />
                        <RefreshClassValue CommandClass="37" RequestFlags="0" Index="0" Instance="3" />
                </TriggerRefreshValue>
        </CommandClass>
Removed:
<!-- Map endpoints to instances --> <CommandClass id="96" mapping="endpoints" />

So, I upgraded to 3.6325, which did NOT solve the problem.
However, timeouts appeared (while z-wave mesh coverage is very good).

There is still something to improve with these double (Multi Instance) switches like ZMNHBD1 and FGS223.
Maybe I can help troubleshooting. Just let me know!

zwaver
Posts: 5
Joined: Saturday 14 January 2017 1:09
Target OS: Windows
Domoticz version:
Contact:

Re: FGS223 Timeouts

Postby zwaver » Saturday 14 January 2017 1:18

Hi All,

This issue is doing my head in. I had 1 working FGS-223, it would turn the lights on/off. I then had the great idea of updating Domoticz and since then I've added another 3 FGS-223 and all of them produce time outs.


"OpenZWave: Received timeout notification from HomeID XXXXXXXXXXX"

"g command, expected response not received after 1 attempt(s)"


What I found strange is that the reported type for my first double switch when it was working was 0x000 and not 0x203.

I'm so close to just getting a fibaro home centre.

zwaver
Posts: 5
Joined: Saturday 14 January 2017 1:09
Target OS: Windows
Domoticz version:
Contact:

Re: FGS223 Timeouts

Postby zwaver » Saturday 14 January 2017 8:16

Running the latest beta of domoticz and still no joy. The lights connected to the fgs223 won't switch on through domoticz. They work perfectly using the openzwave control panel but domoticz is just ending up with timeouts.

al15
Posts: 3
Joined: Tuesday 10 January 2017 23:09
Target OS: -
Domoticz version:
Contact:

Re: FGS223 Timeouts

Postby al15 » Sunday 15 January 2017 12:22

Hi,

i have the same problem - in FHEM the FGS223 is working fine but in DOMOTICZ only one switch can be controlled the other one is simply not reacting. I am using the latest beta on windows.

THANKS
lg
AL

Petermet
Posts: 3
Joined: Thursday 12 January 2017 21:56
Target OS: OS X
Domoticz version:
Contact:

Re: FGS223 Timeouts

Postby Petermet » Sunday 15 January 2017 13:47

I can't operate either channel. I have tried on both a rpi install and on Synology. On both it works fine in the control panel.

Keen to find a solution to this as I only have these switches.

borcon
Posts: 15
Joined: Thursday 05 January 2017 12:15
Target OS: Raspberry Pi
Domoticz version: BETA
Contact:

Re: FGS223 Timeouts

Postby borcon » Sunday 29 January 2017 19:52

@gizmocuz or domo admins or openzwave admins:
How can we help to solve that problem?
How can we set a higher priority for this issue?
I think timeouts are not good for zwave and that problem should be fixed soon if possible.
Only multinstance devices have the timeouts.

Many people use domoticz to control zwave devices.
But at the moment, the support for new devices is not really good.
I know that zwave is not opensource and so it's not easy to support new devices.

Is the timeout problem from domoticz or openzwave?
Please help to solve the problem.

Thanks

al15
Posts: 3
Joined: Tuesday 10 January 2017 23:09
Target OS: -
Domoticz version:
Contact:

Re: FGS223 Timeouts

Postby al15 » Sunday 29 January 2017 20:14

Hi,

i am sure its Domoticz related as i have them running on FHEM and OpenZwave2.0 without problems only on Domoticz (windows) its not working.. so i also hope someone could solve it ...

Thanks
lg
AL

micha_pr
Posts: 342
Joined: Friday 24 October 2014 12:26
Target OS: Raspberry Pi
Domoticz version: Beta
Location: Germany, Berlin
Contact:

Re: FGS223 Timeouts

Postby micha_pr » Sunday 29 January 2017 20:29

What OpenZwave version you are using - with problems?
maybe in FHEM is other version implemented?

Please add the version like "Version: 1.4-2380-g72d9110-dirty" from hardware.
Michael Pruefer
----------------------------
http://www.zwave-review.com (German only)
http://www.SmartHome-BB.de (German only)

borcon
Posts: 15
Joined: Thursday 05 January 2017 12:15
Target OS: Raspberry Pi
Domoticz version: BETA
Contact:

Re: FGS223 Timeouts

Postby borcon » Sunday 29 January 2017 20:32

Domo Version: 3.6544 (BETA)
Platform: RaspberryPi 3
My OpenZwave Version: 1.4-2363-g1f10253-dirty
Last edited by borcon on Sunday 29 January 2017 22:50, edited 1 time in total.

Ericv
Posts: 45
Joined: Saturday 28 January 2017 13:09
Target OS: Raspberry Pi
Domoticz version: 3.5877
Location: Netherlands
Contact:

Re: FGS223 Timeouts

Postby Ericv » Sunday 29 January 2017 21:59

I have a similar issue with my FGS222.

Discussed about this elsewere on the forum, but there is not an explanation yet, as far as i am concerned.

I get the same reports.

from the domoticz log:
2017-01-29 19:28:47.916 OpenZWave: Received timeout notification from HomeID: 4002166290, NodeID: 3 (0x03)

and from the OpenZwave log
2017-01-29 19:28:47.915 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)


My Domoticz: V3.5877
OpenZwave: OpenZWave USB Version: 1.4-2228-gbce4a88-dirty
Platform RPI 2B
Raspberry Pi3; Razberry V2; RFlink; OTGW: PIco UPS HV3.0

Ericv
Posts: 45
Joined: Saturday 28 January 2017 13:09
Target OS: Raspberry Pi
Domoticz version: 3.5877
Location: Netherlands
Contact:

Re: FGS223 Timeouts

Postby Ericv » Wednesday 01 February 2017 22:41

After some searching i read that there maybe some interference between Pi and Razberry, when they are close to each other. So I have separated the razberry board from the pi. Connected the two with a jumper cable of about 20 cm.

And now the time-outs have disappeared, at least when i do fast switching. Will continue testing
Raspberry Pi3; Razberry V2; RFlink; OTGW: PIco UPS HV3.0

borcon
Posts: 15
Joined: Thursday 05 January 2017 12:15
Target OS: Raspberry Pi
Domoticz version: BETA
Contact:

Re: FGS223 Timeouts

Postby borcon » Thursday 02 February 2017 23:29

I have a aeotec gen5 zwave stick and only timeouts with multinstance devices.
So my problems with the timeouts have nothing to do with the pi.

I have upgraded the openzwave in domoticz to the newest version 1.4-2382-g450c4a5-dirty.
But the timeouts still exist. Some people report that in other smart home systems with openzwave have no timeouts.

It would be great if a domoticz admin take part in this topic and help to solve this issue.
Many people have the problems with multinstance devices and some of them change to other smart home systems like openhab2, because they get no response.
Look here: viewtopic.php?p=117392#p117392

annegerben
Posts: 6
Joined: Wednesday 03 August 2016 12:34
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: FGS223 Timeouts

Postby annegerben » Friday 03 February 2017 20:41

Sadly I have to report I have the same issue I'm now running latest beta v3.6595 on rpi2
And I use a aeotec Z-Stick Gen5


Code: Select all

2017-02-03 19:29:55.699 OpenZWave: Received timeout notification from HomeID: 3757259393, NodeID: 21 (0x15)
2017-02-03 19:30:04.042 OpenZWave: Alarm Level: Secure
2017-02-03 19:30:14.049 OpenZWave: Received timeout notification from HomeID: 3757259393, NodeID: 19 (0x13)
2017-02-03 19:30:14.432 OpenZWave: Alarm Level: Secure
2017-02-03 19:30:14.477 OpenZWave: Alarm Level: Secure
2017-02-03 19:30:24.483 OpenZWave: Received timeout notification from HomeID: 3757259393, NodeID: 20 (0x14)
2017-02-03 19:30:24.890 OpenZWave: Alarm Level: Secure
2017-02-03 19:30:24.934 OpenZWave: Alarm Level: Secure
2017-02-03 19:30:34.950 OpenZWave: Received timeout notification from HomeID: 3757259393, NodeID: 21 (0x15)
2017-02-03 19:30:35.336 OpenZWave: Alarm Level: Secure
2017-02-03 19:30:35.379 OpenZWave: Alarm Level: Secure
2017-02-03 19:30:45.386 OpenZWave: Received timeout notification from HomeID: 3757259393, NodeID: 22 (0x16)
2017-02-03 19:30:45.775 OpenZWave: Alarm Level: Secure
2017-02-03 19:30:45.819 OpenZWave: Alarm Level: Secure
2017-02-03 19:30:55.826 OpenZWave: Received timeout notification from HomeID: 3757259393, NodeID: 25 (0x19)
2017-02-03 19:30:56.212 OpenZWave: Alarm Level: Secure
2017-02-03 19:30:56.258 OpenZWave: Alarm Level: Secure
2017-02-03 19:31:06.268 OpenZWave: Received timeout notification from HomeID: 3757259393, NodeID: 26 (0x1a)
2017-02-03 19:31:06.671 OpenZWave: Alarm Level: Secure
2017-02-03 19:31:06.713 OpenZWave: Alarm Level: Secure
2017-02-03 19:31:16.724 OpenZWave: Received timeout notification from HomeID: 3757259393, NodeID: 27 (0x1b)
2017-02-03 19:31:17.584 OpenZWave: Alarm Level: Secure
2017-02-03 19:31:17.629 OpenZWave: Alarm Level: Secure
2017-02-03 19:31:17.667 OpenZWave: Alarm Level: Secure
2017-02-03 19:31:27.674 OpenZWave: Received timeout notification from HomeID: 3757259393, NodeID: 28 (0x1c)
2017-02-03 19:31:29.508 OpenZWave: Alarm Level: Secure
2017-02-03 19:31:29.719 OpenZWave: Alarm Level: Secure
2017-02-03 19:31:39.727 OpenZWave: Received timeout notification from HomeID: 3757259393, NodeID: 29 (0x1d)
2017-02-03 19:31:41.393 OpenZWave: Alarm Level: Secure
2017-02-03 19:31:41.583 OpenZWave: Alarm Level: Secure
2017-02-03 19:31:51.591 OpenZWave: Received timeout notification from HomeID: 3757259393, NodeID: 30 (0x1e)
2017-02-03 19:31:53.277 OpenZWave: Alarm Level: Secure
2017-02-03 19:31:53.497 OpenZWave: Alarm Level: Secure
2017-02-03 19:32:03.505 OpenZWave: Received timeout notification from HomeID: 3757259393, NodeID: 31 (0x1f)
2017-02-03 19:32:03.931 OpenZWave: Alarm Level: Secure
2017-02-03 19:32:03.975 OpenZWave: Alarm Level: Secure
2017-02-03 19:32:05.003 OpenZWave: All Nodes queried

YcKe
Posts: 21
Joined: Sunday 03 July 2016 0:53
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: FGS223 Timeouts

Postby YcKe » Tuesday 07 February 2017 14:40

Hi @annegerben,

can you post a screenshot of your Groups & Network overview screen. (Including associations)

Greetz YcKe

skippy711
Posts: 12
Joined: Friday 20 January 2017 18:52
Target OS: Linux
Domoticz version: V3.6424
Contact:

Re: FGS223 Timeouts

Postby skippy711 » Thursday 09 February 2017 20:27

Hi there,

Perhaps a silly question, but can you operate the switches although they are reported as 'time out'?
In my log I see frequent ' time out notification' but as I am able to operate (and the timers work correctly) I do not bother with the notifications.
For example: a Fibaro Smoke sensor, which I also use as a thermometer, has sometimes time outs, which cause that the values don't come in every 5 minutes. After 30 minutes or so the 'connection' is restored and values start coming in every 5 minutes again.
Grtz

micha_pr
Posts: 342
Joined: Friday 24 October 2014 12:26
Target OS: Raspberry Pi
Domoticz version: Beta
Location: Germany, Berlin
Contact:

Re: FGS223 Timeouts

Postby micha_pr » Thursday 09 February 2017 21:04

Hi all,

the source of all FGS223 problems seems to be in a Fibaro firmware "issue".
Device is reporting that it is supporting "switch multilevel" - but it is not right,... it is a binary switch only.
In Fibaro FGS config XML was inserted that's why:

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"/>

But it does not help in any case for Domoticz installation - depending on different things may happen
    - Switch 1 does not response (in log you can see that want to use multilevel command class....)
    - timeouts

While here is not a final solution you can edit your ZWave config file zwcfg_0xxxxxxx.xml
For that:
1) stop domoticz service
2) make a copy of your current xml file
3) edit the XML
4) start domoticz at new.

in XML look for the right node number (<Node id="xxx">) from hardware settings.
Must look like this:

Code: Select all

 <Node id="2" name="" location="" basic="4" generic="16" specific="1" roletype="5" devicetype="1792" nodetype="0" type="Binary Power Switch" listening="true" frequentListening="false" beaming="true" routing="true" max_baud
      <Manufacturer id="10f" name="FIBARO System">
            <Product type="203" id="1000" name="FGS223 Double Relay" />
        </Manufacturer>
        <CommandClasses>
            <CommandClass id="32" name="COMMAND_CLASS_BASIC" version="1" request_flags="5" mapping="37">
 ...
            </CommandClass>
            <CommandClass id="37" name="COMMAND_CLASS_SWITCH_BINARY" version="1" request_flags="5" innif="true">
 ...
            </CommandClass>
            <CommandClass id="38" name="COMMAND_CLASS_SWITCH_MULTILEVEL" version="3" request_flags="5" after_mark="true" getsupported="false" innif="true">
                <Instance index="1" endpoint="1" />
                <Instance index="2" endpoint="2" />
                <Value type="byte" genre="user" instance="1" index="0" label="Level" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
                <Value type="button" genre="user" instance="1" index="1" label="Bright" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
                <Value type="button" genre="user" instance="1" index="2" label="Dim" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
                <Value type="bool" genre="system" instance="1" index="3" label="Ignore Start Level" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="True" />
                <Value type="byte" genre="system" instance="1" index="4" label="Start Level" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
                <Value type="byte" genre="user" instance="2" index="0" label="Level" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
                <Value type="button" genre="user" instance="2" index="1" label="Bright" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
                <Value type="button" genre="user" instance="2" index="2" label="Dim" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
                <Value type="bool" genre="system" instance="2" index="3" label="Ignore Start Level" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="True" />
                <Value type="byte" genre="system" instance="2" index="4" label="Start Level" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
                <Value type="byte" genre="system" instance="2" index="5" label="Dimming Duration" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="255" />
                <Value type="byte" genre="user" instance="2" index="6" label="Step Size" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="0" />
                <Value type="button" genre="user" instance="2" index="7" label="Inc" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
                <Value type="button" genre="user" instance="2" index="8" label="Dec" units="" read_only="false" write_only="true" verify_changes="false" poll_intensity="0" min="0" max="0" />
            </CommandClass>
            <CommandClass id="39" name="COMMAND_CLASS_SWITCH_ALL" version="1" request_flags="5">
                <Instance index="1" />
....

REMOVE now all between
<CommandClass id="38" ... and next </CommandClass> - so all this wrong class.

Result should be like this:

Code: Select all

 <Node id="2" name="" location="" basic="4" generic="16" specific="1" roletype="5" devicetype="1792" nodetype="0" type="Binary Power Switch" listening="true" frequentListening="false" beaming="true" routing="true" max_baud
      <Manufacturer id="10f" name="FIBARO System">
            <Product type="203" id="1000" name="FGS223 Double Relay" />
        </Manufacturer>
        <CommandClasses>
            <CommandClass id="32" name="COMMAND_CLASS_BASIC" version="1" request_flags="5" mapping="37">
 ...
            </CommandClass>
            <CommandClass id="37" name="COMMAND_CLASS_SWITCH_BINARY" version="1" request_flags="5" innif="true">
 ...
            </CommandClass>
            <CommandClass id="39" name="COMMAND_CLASS_SWITCH_ALL" version="1" request_flags="5">
                <Instance index="1" />
....


After starting at new domoticz the FGS223 will work - at least at all our installations it was starting to work normal...

@gizmocuz: maybe we can pass this wrong command class in zwcfg file if the parameter " getsupported="false" " is inside?
It is inside the Fibaro config XML and - inside the zwcfg file.

Good luck!
Michael Pruefer
----------------------------
http://www.zwave-review.com (German only)
http://www.SmartHome-BB.de (German only)

annegerben
Posts: 6
Joined: Wednesday 03 August 2016 12:34
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: FGS223 Timeouts

Postby annegerben » Friday 10 February 2017 16:14

YcKe wrote:Hi @annegerben,

can you post a screenshot of your Groups & Network overview screen. (Including associations)

Greetz YcKe


Hi YcKe

as requested

2017-02-10 15_12_04-Domoticz.png
2017-02-10 15_12_04-Domoticz.png (229.8 KiB) Viewed 608 times


Return to “Bugs and Problems”

Who is online

Users browsing this forum: No registered users and 4 guests