Author Topic: Is this a ZWave mesh problem?  (Read 2337 times)

Domodude

  • Guest
Is this a ZWave mesh problem?
« on: April 10, 2012, 09:49:44 pm »
Hi,
Can this be caused by a bad zwave mesh?
Code: [Select]
01 04/10/12 18:42:10.608 ERROR: Dropping command, no callback received after three resends <0x40a70b70>
05 04/10/12 18:42:10.712 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:42:13.816 No callback received: await_callback: 137 timer: 31 <0x40a70b70>
05 04/10/12 18:42:13.921 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:42:17.026 No callback received: await_callback: 137 timer: 31 <0x40a70b70>
05 04/10/12 18:42:17.130 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:42:20.234 No callback received: await_callback: 137 timer: 31 <0x40a70b70>
01 04/10/12 18:42:20.234 ERROR: Dropping command, no callback received after three resends <0x40a70b70>
05 04/10/12 18:42:20.338 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:42:23.442 No callback received: await_callback: 138 timer: 31 <0x40a70b70>
05 04/10/12 18:42:23.547 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:42:26.651 No callback received: await_callback: 138 timer: 31 <0x40a70b70>
05 04/10/12 18:42:26.755 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:42:29.859 No callback received: await_callback: 138 timer: 31 <0x40a70b70>
01 04/10/12 18:42:29.859 ERROR: Dropping command, no callback received after three resends <0x40a70b70>
36 04/10/12 18:42:59.996 We have been idle for 30 seconds, polling device states <0x40a70b70>
05 04/10/12 18:43:00.101 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:43:03.205 No callback received: await_callback: 139 timer: 31 <0x40a70b70>
05 04/10/12 18:43:03.309 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:43:06.413 No callback received: await_callback: 139 timer: 31 <0x40a70b70>
05 04/10/12 18:43:06.518 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:43:09.621 No callback received: await_callback: 139 timer: 31 <0x40a70b70>
01 04/10/12 18:43:09.621 ERROR: Dropping command, no callback received after three resends <0x40a70b70>
05 04/10/12 18:43:09.726 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:43:12.829 No callback received: await_callback: 140 timer: 31 <0x40a70b70>
05 04/10/12 18:43:12.934 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:43:16.038 No callback received: await_callback: 140 timer: 31 <0x40a70b70>
05 04/10/12 18:43:16.143 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:43:19.247 No callback received: await_callback: 140 timer: 31 <0x40a70b70>
01 04/10/12 18:43:19.247 ERROR: Dropping command, no callback received after three resends <0x40a70b70>
05 04/10/12 18:43:19.352 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:43:22.456 No callback received: await_callback: 141 timer: 31 <0x40a70b70>
05 04/10/12 18:43:22.561 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:43:25.664 No callback received: await_callback: 141 timer: 31 <0x40a70b70>
05 04/10/12 18:43:25.769 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:43:28.873 No callback received: await_callback: 141 timer: 31 <0x40a70b70>
01 04/10/12 18:43:28.874 ERROR: Dropping command, no callback received after three resends <0x40a70b70>
01 04/10/12 18:43:28.874 ERROR: Three dropped commands in a row, soft-resetting controller <0x40a70b70>
36 04/10/12 18:43:59.010 We have been idle for 30 seconds, polling device states <0x40a70b70>
05 04/10/12 18:43:59.115 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:44:02.219 No callback received: await_callback: 142 timer: 31 <0x40a70b70>
05 04/10/12 18:44:02.323 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:44:05.427 No callback received: await_callback: 142 timer: 31 <0x40a70b70>
05 04/10/12 18:44:05.532 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/10/12 18:44:08.636 No callback received: await_callback: 142 timer: 31 <0x40a70b70>

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: Is this a ZWave mesh problem?
« Reply #1 on: April 13, 2012, 12:23:11 am »
what stick do you use? Does it affect all nodes or just specific ones?
rock your home - http://www.agocontrol.com home automation

Domodude

  • Guest
Re: Is this a ZWave mesh problem?
« Reply #2 on: April 13, 2012, 01:36:40 pm »
Tricklestar at the moment.

As far as I can tell, the entire zwave network is non-responsive! I have not tried all lights throughout the house though, there are 4 floors :(

seth

  • Guru
  • ****
  • Posts: 485
  • A day w/o LinuxMCE is like a day w/o sunshine!
    • View Profile
Re: Is this a ZWave mesh problem?
« Reply #3 on: April 13, 2012, 06:39:16 pm »
 :)
Hi.

Firstly: /me Drools at four floors of Zwave........

Secondly: Do you happen to have a thermostat in your installation?

If so, was it added during the intelligent mesh layout, i.e. starting at the core and working out geographically?

If not, when was it added, and how far is it from the core?

I added a knock off version of the Wayne Dalton version, but, I added it at the end of my chain. As I did not want to unlearn and relearn all of my devices. It worked well for some time, however I started getting messages like what you are, and my timed scenarios stopped firing. Like at sunset, turn on perimeter lighting, and such.

What I had to do was in fact delete my zwave devices, reset my Aeon Labs stick, and start from scratch, capturing the thermostat geographically from my core.

If you don't have a thermostat, then disregard this mad raving, and go back to the Firstly point, and ignore me  :D

Hope you figure it out.

Best Regards,

Seth
".....Because Once you've LinuxMCE'd....."
System stats located at my user page:

http://wiki.linuxmce.org/index.php/User:Seth

JaseP

  • Addicted
  • *
  • Posts: 526
    • View Profile
    • JaseP's LinuxMCE Wiki User page
Re: Is this a ZWave mesh problem?
« Reply #4 on: April 13, 2012, 07:05:51 pm »
I use a MCV Vera as my primary controller. The Vera handles running a mesh network "heal" on a regular basis. I have a second Aeon Labs stick for LinuxMCE, for it to act a a secondary controller.

What is supposed to happen with z-wave is that the primary controller has the devices ping one another so that the mesh network can be hashed out, in terms of what devices talk to which neighbors, for routing commands. If you move, delete, or add devices, the controller is supposed to re-hash the network.  The more devices, the better the mesh, the more likely signals will reach their destination,  etc.

In the event that you get the kind of mesh network problems indicated above, and cannot successfully initiate a mesh network "heal," you almost have to rebuild the z-wave network by deleting everything and starting over. It sucks, but that's the way it is sometimes. But before you go to that extreme, look in theLinuxMCE web admin panel to see what z-wave admin options are there. If there's a network heal option, try that. I really haven't looked at what z-wave options are in the web panel, since my setup only requires that LinuxMCE can talk to the primary controller through the secondary Aeon Labs stick.
See my User page on the LinuxMCE Wiki for a description of my system configuration (click the little globe under my profile pic).

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: Is this a ZWave mesh problem?
« Reply #5 on: April 13, 2012, 09:27:33 pm »
no we don't have a hail/heal in LMCE. Domodude, would you mind to test what happens when you do a *soft* reset (search if you don't know how). If that does not help, unplug the stick, shut down the core, plug it back in and then startup again? I suspect that the firmware of the stick crashed. We've seen some occurrences of this.

ps: don't do a regular reset, that will erase all network info. The soft reset is something different. It will just "reboot" the zensys chip
rock your home - http://www.agocontrol.com home automation

JaseP

  • Addicted
  • *
  • Posts: 526
    • View Profile
    • JaseP's LinuxMCE Wiki User page
Re: Is this a ZWave mesh problem?
« Reply #6 on: April 14, 2012, 02:17:24 am »
@ hari

Is the firmware crash associated with any particular controller stick hardware? If so, what hardware?
See my User page on the LinuxMCE Wiki for a description of my system configuration (click the little globe under my profile pic).

Domodude

  • Guest
Re: Is this a ZWave mesh problem?
« Reply #7 on: April 14, 2012, 02:10:34 pm »
no we don't have a hail/heal in LMCE. Domodude, would you mind to test what happens when you do a *soft* reset (search if you don't know how). If that does not help, unplug the stick, shut down the core, plug it back in and then startup again? I suspect that the firmware of the stick crashed. We've seen some occurrences of this.

ps: don't do a regular reset, that will erase all network info. The soft reset is something different. It will just "reboot" the zensys chip

Hi Hari,
I did a softreset which should be an early step of report nodes. In fact, I report nodes every few hours using a timed event to make sure that this kind of thing did not happen. Useless, it appears. I will try your suggestion above.
« Last Edit: April 16, 2012, 09:26:14 am by Domodude »

Domodude

  • Guest
Re: Is this a ZWave mesh problem?
« Reply #8 on: April 14, 2012, 02:12:34 pm »
Thanks Seth and JaseP! The floors are not so big... In any case, I do not have fancy stuff -- just dimmers, electronic switches and relay switches. One switch is connected to a mirror heating system, but it does not know that!
I do have a MCV V1 sitting on the shelf somewhere, but I hesitate to make the setup more compex than it already is.

Domodude

  • Guest
Re: Is this a ZWave mesh problem?
« Reply #9 on: April 14, 2012, 03:10:14 pm »
I will try your suggestion above.

The system works again. Let's see for how long....

EDIT: I did a "heal" on the minimote, hopefully that will improve things a bit, too.
« Last Edit: April 16, 2012, 09:25:40 am by Domodude »

Domodude

  • Guest
Re: Is this a ZWave mesh problem?
« Reply #10 on: April 16, 2012, 09:24:47 am »
I use a MCV Vera as my primary controller.
I am going to give this a try, anyway. How did you program the Vera stick (do you have one?)? I have  a Vera 1 which I flashed to the UI4 (Vera 2) software, and an Aeon Labs ZWave stick. I use a Minimote to include my network, and currently have LMCE setup as a SUC/SIS controller. I do not think I can have two SUC/SIS controllers, is that correct? And the Vera does not really want to accept the setup from the Tricklestar minimote... I am at a loss here, any hints?

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: Is this a ZWave mesh problem?
« Reply #11 on: April 16, 2012, 11:19:35 am »
the vera stick works fine.
rock your home - http://www.agocontrol.com home automation

Domodude

  • Guest
Re: Is this a ZWave mesh problem?
« Reply #12 on: April 16, 2012, 12:27:00 pm »
But if the minimote is already the inclusion controller for LinuxMCE (TS stick), can it also be one for my Vera+Aeon box? I am having problems configuring this.

I think I'll have to decide who is primary, and who is secondary controller. In the posts above, I see that LMCE could be secondary and vera primary. Hmmm.  :-\

JaseP

  • Addicted
  • *
  • Posts: 526
    • View Profile
    • JaseP's LinuxMCE Wiki User page
Re: Is this a ZWave mesh problem?
« Reply #13 on: April 16, 2012, 04:41:09 pm »
How did you program the Vera stick (do you have one?)?

I have the Vera acting as the primary controller, and do all inclusions through it's Aeon Labs stick. My LinuxMCE core has a second Aeon Labs stick that acts as secondary controller. The hardware detect wizard brought up the "Sarah" interface automatically. All I had to do was to set the Vera to copy the setup to that secondary controller, much like you would do if you had a z-wave enabled remote controller.

Quote
I do not think I can have two SUC/SIS controllers, is that correct?

One must be primary, and all inclusion and exclusion must be done through that one. The other will be a glorified remote control.

Quote
And the Vera does not really want to accept the setup from the Tricklestar minimote... I am at a loss here, any hints?

Make your Vera primary, and make the tricklestar the secondary attached to your LinuxMCE core. I have my Vera running as the external network Gateway, and everything internal talks to my LinuxMCE core through a Linksys router that has DHCP turned off (using LinuxMCE as the internal DHCP provider).

Vera always wants to be the primary controller for a z-wave network, by default at least. LinuxMCE will accept a role as a secondary controller without putting up much of a fuss. The reason I work my system out this way is that the Vera supplies a free internet connectivity service. If I wanted to do that through LinuxMCE, I would need to sign up with a static IP address service. That would represent another point of failure for controlling the system, and I already have a working Vera system (don't fix what ain't broke). Of course, I give up the ability to control LinuxMCE through the net, but I was only interested in doing home automation and surveillance remotely.



See my User page on the LinuxMCE Wiki for a description of my system configuration (click the little globe under my profile pic).

Domodude

  • Guest
Re: Is this a ZWave mesh problem?
« Reply #14 on: April 28, 2012, 09:24:49 pm »
I'm now redoing the network. Still getting "No callback received: await_callback: 60 timer: 31" messages though, so I am not sure if the network is ok now.

36   04/28/12 21:21:35.496      ZWave::CMD_Set_Association <0x40e72b70>
36   04/28/12 21:21:35.496      parsing node list <0x40e72b70>
36   04/28/12 21:22:07.122      We have been idle for 30 seconds, polling device states <0x40a70b70>

And setting associations: am I not supposed to get a message that the association succeeded?

Thanks,
Mark