more G-Labs products

Author Topic: Losing Z-Wave Network  (Read 1608 times)

December 14, 2015, 03:46:40 PM
Read 1608 times

jjennings308

  • *
  • Information
  • Newbie
  • Posts: 9
Since R504, my Z-wave network quits responding and cannot discover and modes.  I am using a Aeon Z-Wave stick as my controller and I am not on R506.  I have been using the controller on Homegenie for about a year without this problem.

December 16, 2015, 08:23:14 PM
Reply #1

skl77

  • *
  • Information
  • Newbie
  • Posts: 12
I don't have a solution but same problem.
But i do not know really that this issue comes with a release of homegenie or my updates on OS. So which Operating System your are using?
BR
Sebastian

December 18, 2015, 05:41:46 AM
Reply #2

jjennings308

  • *
  • Information
  • Newbie
  • Posts: 9

December 18, 2015, 05:01:56 PM
Reply #3

rg2k

  • *
  • Information
  • Newbie
  • Posts: 10
There are a few posts that mention that Jessie is not recommended, you will need to go back to Wheezy for now...

December 19, 2015, 04:26:16 AM
Reply #4

jjennings308

  • *
  • Information
  • Newbie
  • Posts: 9
I have noticed that it I don't turn on upnp that I don't have the problem.  I turned it off for 3 days no issues turned upnp back on and the issue returned in less than 12 hours.

December 19, 2015, 02:05:26 PM
Reply #5

skl77

  • *
  • Information
  • Newbie
  • Posts: 12
Ok, i also try it with jessie (debian8) and wheezy (debian7) and both didn't work with armhf achitectre, so the key question from some older Information, is it neede to have an armel architectrue in case of some mono Bugs, as i've read in some older Posts.

December 19, 2015, 04:47:06 PM
Reply #6

skl77

  • *
  • Information
  • Newbie
  • Posts: 12
Know i brought back my whole System to Debian 7
After days and days to find the Problem within Debugging Source Code i am totally confused what happened.
So now following Situation:
- zwave Network with Aeon S2E
- OS identifies the Stick as SiLAB and regonise it as /ttyUSB0
- Homegenie V1.1 507
- i am able to get all node wake up Signals
- but on any Nodeaction Switch to On/off a "Node Timeout" occurs

I do the same with an parallel Windows 8.1 Tablet and everything is running.
It seems that the Response takes longer on my System as on other Systems.
no i am looking for the source Code but after 10-20h Failure Analysis i am Little tired.

BR

Sebastian

December 19, 2015, 07:26:24 PM
Reply #7

skl77

  • *
  • Information
  • Newbie
  • Posts: 12
Now some Outputs from HG about ZWave Response timeout