forum

I'm wondering if it's a Razberry thing or a Z-wave thing that you can't include a device via a repeating node in the network?

I have a razberry that talks to a ac switch that is shown as a active repeater.
I put the razberry in inclusion mode and try to include a device that does not reach the razberry but it does reach the ac switch.

Nothing happens. So is this the correct behavior?

I thought you should be able to include via a routing node since it's at inclusion the route list is created. Having to be close to the razberry to include and then move the device will create a bad route list that you have to heal.

Any insight is appreciated.

I am having the same problem, trying to include a Danfoss thermostat via a Aeon Labs repeater.

Henrietta wrote:I am having the same problem, trying to include a Danfoss thermostat via a Aeon Labs repeater.

That is not a good idea. Either move the Razberry closer to the Danfoss and try to include there, or move the Danfoss to Ras.
If you place them back to the intended places you can perform a routing update with the Expert UI

What I have done so far:

- Included the Aeon repeater in Raz's range (Force Unsecure Inclusion)
- Included the Danfoss in Raz's range (Force Unsecure Inclusion)
- Moved the Danfoss out of Raz's range, but in four-meter line-of-sight with the repeater
- Ran network reorganization with mains+battery devices
Reorganization didn't go as planned Routing table still says that Raz can connect to the Danfoss, which - judging by commands getting stuck in the job queue - is not true anymore.

What am I doing wrong?

Can you produce with the Old Expert UI a routing table image like this snippet:
To get the numbers in the image select expert mode in the lower right corner of your screen. Please indicate which number represents which device?

In this particular image device 13 is located in an adjacent building via an Aeon extender. Distance is more than 30 meters. several walls between. I does communicate however.

Also try to find a relevant portion aroung Danfoss inclusion from log file
/var/log/z-way-server.log

Here's what I did

• Include the Aeon repeater (Raz's range)
• Include a Danfoss 014G0013 (thermostat that claims to be "open" and work with all Z-Wave controllers, claims to support NWI and Explorer Frame) - Raz's range
• Include a Danfoss 014G0012 (claims no support for NWI and Explorer, told by Danfoss to work only with their Z-Wave gate, has a DDR) - Raz's range
• Move both Danfosses outside Raz's range, but line-of-sight with the repeater

It's 17:34 as I'm writing this. I associated all devices with the Aeon (Association), I don't know if that will help. Routing table is: Nothing even remotely suspicious in the logs. New Expert UI says the following about the devices: Right now all update commands sent to Danfosses are stuck in the queue, and both signal on-screen that they can't get a connection.

I quess you have tried some short push(es) on the Danfosses to force wake up during rearrange routes? (I don't remember exactly how they should work as I thrown mine a way almost 2 years ago).
Does Force re-interview help?

I tried doing so. Then it got interesting. The repeater got flagged as dead by Raz (mashing buttons in expert interface helped), the 014G0012 reported E5 on the display (no connectivity), and 014G0013 kept on complaining how it has no signal.

Not for long. As I forcibly excluded Danfosses (Mark Battery as Failed + Factory Reset) AND reincluded them, the problem resurfaced. Job queue did a "removing job due to too much retransmitions" for the Aeon repeater, and soon it was flagged as failed again.

Got to make a phone call tomorrow :/

I attached a server log for anyone interested. The last parts are, in sequence - Aeon failing, me mashing buttons to recover it, failure-removing Danfosses, reincluding them, and Aeon failing again.

Aeon repeater repeatedly failed to interview after. Resetting the Z-Wave chip seems to have fixed that, for now.

I finally got to a place where there is reliably no communication between the Raz and the Danfosses, and yet they will not use the repeater.
Device 2 is the Aeon repeater.

//update: There seems to be some kind of a problem with the Danfoss thermostats. Some guy at Vera's forum noted that they don't seem to use repeaters, which my observations would confirm. Danfoss seems to have a shady history as a Z-Wave device developer, I'll keep you posted.

OK. So, now that I have things worked out, I feel obliged to report what I've come up with.

Danfoss 014G0012 loves being directly connected to Z-Way (direct connection). You can place it a hop away - it will miss every 1 or 2 wake-up cycles, sometimes just disappearing altogether. You need to manually wake it up then. Rock-solid if connected directly.

Danfoss 014G0013 is very fine with being placed hops away from the target, and will work reasonably.

Playing with Wakeup times on both Danfosses breaks stuff, and they start behaving very poorly on non-direct connections. Best leave it alone.

When you attach a Danfoss, let it complete the interview and wait until next wakeup time appears in the Device Status section. When time appears, and the device is asleep, is the time to put it in place. In next two wakeups it should discover a route and start working. This seems to be very important - placing it sooner broke stuff in random ways.

My issue's resolved at this point. Testing StellaZ's now