ZWAVE "No callback received". Is this bad? What does it mean?

[Domodude]

I still have messages like this in my logs:

Code: [Select]

05 04/28/12 21:25:51.665 No callback received: await_callback: 27 timer: 31 <0x40a70b70>
05 04/28/12 21:25:51.886 No callback received: await_callback: 27 timer: 31 <0x40a70b70>
05 04/28/12 21:25:55.075 ERROR: callback id is invalid! <0x40a70b70>
05 04/28/12 21:25:56.509 ERROR: callback id is invalid! <0x40a70b70>It looks bad, but is it? Sounds like a comm issue between the nodes but I am not sure. And an invalid callback id... That MUST be bad (since it has "error" in front of it 

And now that we are on the subject of understanding the log: many times a line has a hex value between <> like so: Got basic report from node 6, value: 99 <0x40a70b70>. This number is the same in all cases on my system! It does not refer to a node ID, but what does it refer to?

...and now I am getting these again too:

Code: [Select]

05 04/28/12 21:31:53.089 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/28/12 21:31:56.194 No callback received: await_callback: 46 timer: 31 <0x40a70b70>
05 04/28/12 21:31:56.298 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/28/12 21:31:59.403 No callback received: await_callback: 46 timer: 31 <0x40a70b70>
05 04/28/12 21:31:59.507 ERROR: ZW_SEND could not be delivered to Z-Wave stack <0x40a70b70>
05 04/28/12 21:32:02.611 No callback received: await_callback: 46 timer: 31 <0x40a70b70>

Grrr 

[hari]

are you bored?

[Domodude]

   Far from it. Frustrated is more like it...

[hari]

  Far from it. Frustrated is more like it...

you did not report any issues/problems relating to the log output.. so why are you frustrated?

[Domodude]

Because associations tend to not work, remote switches cannot be properly included (let alone be associated through LMCE), and because the zwave network is often non-responsive. To be honest, I don't even know where to start. I have an unpleasant feeling that my old merten stuff is the reason for these problems....

[davegravy]

There's likely several possible reasons for this. I had the same symptoms you describe and I ended up discovering the culprit to be a bad antenna (internal) on my AEON Z-stick USB dongle.

[hari]

the merten stuff works fine, I have dozen of devices here.

[Domodude]

Well that is good to hear, but you also wrote a few times about your bricked remote controller. Merten replaced yours, but so far they refuse to replace mine. I am not the only one with doubts about Merten. I'm sure that you have been following the MCV forum for a long time, for example.
Anyway, it does not really matter who has working stuff from which manufacturer. I have lotsa issues with Merten, and not with any other brand. So for me, Merten is not working like I wish it would.

[hari]

then you must be doing something wrong. The Merten units are high quality and work without issues.