GE Outdoor Switch Module

Other Devices & Integrations Lighting & Load Control
1

I have a GE Outdoor Switch Module that pairs with my VeraLite within 4 feet without any issue. I can turn it off and on. But, when I move is out into “mesh” network, the VeraLite has no contact with it. Other Z-Wave devices in the network work fine. Just bringing back within 4 feet of the VeraLite and it operates fine.

Any suggestions as to what my issue might be?

Thanks!!!

2

When you relocate a Z-Wave device, the network must recalculate routing information in order to be able to communicate with the relocated device. Vera initiates a network heal each night at around 2:00am.

I’ve recently found an unsupported means of triggering a heal on demand. As stated, this is not supported by Vera and if you use it you are on your own. Access the following URL from your browser:

http://:3480/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:ZWaveNetwork1&action=HealNetwork&BatteryMinutes=30&StressCycles=2&StartStage=1&StopStage=3

This Lua code accomplishes the same task.

[code]

– Initiate Z-Wave network heal.
– Intended for starting heal after adding new devices.

– Depending on the size of your network, a heal can take a very long time.

local URN = “urn:micasaverde-com:serviceId:ZWaveNetwork1”
local ACT = “HealNetwork”
local BATT = {BatteryMinutes=30} – Default 30. Nightly 60.
local ITR = {StressCycles=2} – Default probably ample.
local START= {StartStage=1}
local STOP = {StopStage=3} – Default 7. UI7.10 or greater probably needs to go no further than 3.

luup.call_action(URN, ACT, BATT, ITR, START, STOP)[/code]

3

[quote=“Z-Waver, post:2, topic:191050”]When you relocate a Z-Wave device, the network must recalculate routing information in order to be able to communicate with the relocated device. Vera initiates a network heal each night at around 2:00am.

I’ve recently found an unsupported means of triggering a heal on demand. As stated, this is not supported by Vera and if you use it you are on your own. Access the following URL from your browser:

http://:3480/data_request?id=lu_action&serviceId=urn:micasaverde-com:serviceId:ZWaveNetwork1&action=HealNetwork&BatteryMinutes=30&StressCycles=2&StartStage=1&StopStage=3

This Lua code accomplishes the same task.

[code]

– Initiate Z-Wave network heal.
– Intended for starting heal after adding new devices.

– Depending on the size of your network, a heal can take a very long time.

local URN = “urn:micasaverde-com:serviceId:ZWaveNetwork1”
local ACT = “HealNetwork”
local BATT = {BatteryMinutes=30} – Default 30. Nightly 60.
local ITR = {StressCycles=2} – Default probably ample.
local START= {StartStage=1}
local STOP = {StopStage=3} – Default 7. UI7.10 or greater probably needs to go no further than 3.

luup.call_action(URN, ACT, BATT, ITR, START, STOP)[/code][/quote]

Your HTTP code worked “like a charm”. By viewing the “Devices” tab on UI7, I saw, for the first time, the mesh network healing/repair process in action - just the tool I needed. By watching the healing process on the UI, I learned a lot, too. For instance, I have a number of devices the VeraLite knows about (paired), but are powered down - this slows down the healing process greatly are they are searched out. For anyone following this forum topic, when given the HTTP healing command, the response in your Internet browser will be similar to the following:

<?xml version="1.0"?>

-<u:HealNetworkResponse xmlns:u=“urn:schemas-micasaverde-org:service:ZWaveNetwork:1”>
1168
</u:HealNetworkResponse>

One question, is there a reporting tool that gives the status of the mesh network, showing nodes/devices, routing, etc., in a concise table format?

Thanks!

4

I’m glad that it worked for you.

There are a few posts on the forums of code that will collect device lists for you. I’ve also heard that AltUI does a nice job of collecting and displaying such information.