Message in LuaUPnP log: NO ROUTE

Community Playground General Discussions
1

Hi,

Every few minutes I see this message in the LuaUPnP logs:

02 08/15/11 0:12:57.015 ZW_Send_Data node 48 NO ROUTE (nil) <0xc04>
04 08/15/11 0:12:57.184 <0x803>
02 08/15/11 0:13:27.015 ZW_Send_Data node 43 NO ROUTE (nil) <0xc04>
04 08/15/11 0:13:27.924 <0x803>

I was wondering what it means and if this needs fixing?

The devices 43 and 48 are the two closest to the Vera box and can be controlled by Vera just fine. The devices are mains powered switches.

Any thoughts?

2

Are you using 2.78 or 3.20?

This is a normal log if you are using 2.78

JOD.

3

I’m using Z-Wave version 3.20 instead of 2.78
Also, I have disabledthe “Use MiOS routing instead of Z-Wave (requires 4.5)” option to stop it from trying to repair my network … because I read this seems to fail with battery operated devices.

It’s a Vera2 and the network has been built from scratch using version 3.20 (no upgrade).

4

@pebu,

I’m using 2.78 and don’t know the answer, but maybe someone using 3.20 can chime in.

If I had to take a guess, the NO ROUTE (nil) question “ZW_Send_Data node 43 NO ROUTE (nil)” may only show data when used when a manual route is selected?? OR, it means it’s a direct hop to Vera and does not require a route.

JOD.

5

@pebu,

what kind of devices are node 43 & 48?!?

Unticking the Mios routing option does stop nightly heals.
But heals only take place when Vera detects problems in the Zwave routing during the day.

Judging from your log there ARE issues with either unconfigured or misconfigured devices (node 43 j 48). Please bear in mind the node ID and device# are not the same when checking!

For devices that ARE configured correctly you could select the “do not configure” option on those devices.

From what we learned so far, especially battery operated devices with long sleeping times are affected by the automated 2am healing process. The devices that are not discovered then get deleted from the local matrix in surrounding devices.

This results in Vera being unable to find a path to the device and vice versa.
When this happens the device shows “not configured”.

Henk

6

As @JOD stated, it may be related to running Vera without MiOS routing enabled (i.e. either running 2.78, or 3.20 with the option for MiOS routing turned off (as in your case)). Vera doesn’t do any route discovery in this case / she does not know the route to a node.

You probably have polling enabled (default) with a 30 second polling interval (default), which would explain the periodicity of what you are seeing. Those traces are probably related to Vera sending out a poll command to those nodes.

7

I think the whole ‘vera doesn’t know the routing’ is exactly what was happening.

I switched to MIOS routing and did a network heal.
After that I see messages like:

02 08/15/11 17:20:20.015 ZW_Send_Data node 43 USING ROUTE 48.0.0.0 <0xc04>
04 08/15/11 17:20:20.333 <0x803>

It seems the 48.0.0.0 is the 4-hop route notation to the endpoint, or in this case a single hop.

Device #43 and #48 are both binary power switches for lamps with routing functionality (duwi).

So it seems there’s nothing to worry about after all.