Scenes in VeraPlus will not Fire from Triggers from Device or Schedule

Community Playground Getting Started & Initial Setup
1

So I bit my bottom lip and took the plunge into Vera Plus. Put the old Vera 3/UI5 in Controller Shift, the Vera Plus in Copy Z Wave Network From Primary Controller, and then uploaded the Vera 3 Backup to Vera Plus. Everything according to the steps provided by MCV. After I cleared up all the “Can’t Detect Devices” and updated the plugins I thought I was ready to go. Well, no I wasn’t by a long shot. None of my scenes are firing after a trigger from a device or schedule, none of them. I can run them manually just like I can command my devices but nothing from a device or schedule trigger. When I walk by a motion sensor or trigger a door/window sensor normally I get a little blip on the red LED on the device, now they just stay on when they get triggered. My Vera 3/UI5 is still working like a champ. My Vera 3 has been off when I experienced this problem.

Has anyone else experienced this issue? Any help is appreciated but I have put in a support ticket with MCV

2

My Vera Plus is working just fine for all the things you stated.
-scenes running off device and schedule triggers
-motion detectors and door/window sensors triggering scenes

But I started with a blank slate, so maybe the problem is with the migration (although that really doesn’t seem likely).

3

Your battery operated devices need to be awakened and then configured by the new Vera with the “Configure node right now” option. Additionally, a heal may be necessary after that. See below.

The curious thing is the schedules not working. I’d recommend using SSH to connect to Vera and verify the time and date by issuing the date command. The clock in the GUI is your PC’s clock. The next step would be to look at the Vera log and see what, if anything is happening to the scenes that are not running at their scheduled time.

Manually initiate a network heal in UI7.

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]

Using the above request or luup code will mess up the mesh network and nodes will stop working correctly. This method is in contradiction to our currently implemented Z-Wave healing process that updates the route and lets the chip itself manage the routing table as opposed to the previous method where the gateway kept the routing table.

  • Vera official
4

[quote=“Z-Waver, post:3, topic:191440”]Your battery operated devices need to be awakened and then configured by the new Vera with the “Configure node right now” option. Additionally, a heal may be necessary after that. See below.

The curious thing is the schedules not working. I’d recommend using SSH to connect to Vera and verify the time and date by issuing the date command. The clock in the GUI is your PC’s clock. The next step would be to look at the Vera log and see what, if anything is happening to the scenes that are not running at their scheduled time.

Manually initiate a network heal in UI7.

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]
@Z-Waver… thanks and I’ll try what you suggest. So I understand about what could be happening with schedules and why you are investigating this route but what about device triggers not being executed? I created a brand new simple Scene using the one motion detector I have that didn’t have the “Can’t Detect Device” error to turn on a light. The scene will not fire from the motion trigger yet if I performed a manual Run Scene then it works.

@MCV or anyone representing them…Things should be easier than this at this point in Vera’s life.

Using the above request or luup code will mess up the mesh network and nodes will stop working correctly. This method is in contradiction to our currently implemented Z-Wave healing process that updates the route and lets the chip itself manage the routing table as opposed to the previous method where the gateway kept the routing table.

  • Vera official
5

In all of this you have not yet stated whether or not the motion sensor displays that it has been tripped in the GUI, let alone the log file.

I suspect that the motion sensor is unable to communicate with Vera. This may be due to a communication/routing issue, but it can also be due to Vera not having configured the battery operated device to inform Vera when tripped. I suspect, though I don’t have enough information, that the old devices have not been configured/reconfigured to point to the new Vera and that the new device hasn’t been healed and is unable to route to Vera, even though it knows it should.

You must first get the motion sensors to notify Vera of their trip/untrip state. Then the scenes should work and if they don’t you can troubleshoot further.

Basic troubleshooting steps for every Z-Wave device:

[ul][li]Exclude then include the device, next to Vera.[/li]
[li]Does the device work next to Vera? [/li]
[li]Use the device in your scene, next to Vera. If it works, you’ve proven that the device and scene are fine. Otherwise, you need to find out why they failed.[/li]

[li]After everything is working, then you need to install the device in its final location and allow the network to heal, or you need to exclude the device and include it in its final location and may still need to allow the network to heal. [/li][/ul]

6

I have a similar issue, my two Philio 3in1 sensors migrated across from VeraEdge to VeraPlus but did not register any updates, even after leaving them alone for at least 2 days. I ended up unpairing them from Vera, and then trying to re-pair them a number of times (Security Key exchange kept failing). Finally got them paired, but now, even though the TEMP & LUX are working correctly, the PIR is being triggered in the master device only, but the PIR sensor device is not picking up a trip, and a scene can only be configured for the PIR Sensor not the master device… This is happening on both my sensors.

Getting this message at each trip
[size=8pt]24 03/07/16 18:17:16.986 ZWaveJobHandler::DoReceivedFrame m_iFrameID 158 inc_enc_fr node 55 command 0x4 data <0x7724a520>
24 03/07/16 18:17:16.987 ZWaveNode::HandlePollUpdate node 55 device 102 class 0x8f command 0x1 m_iFrameID 158/21830896 data 0x4 0x3 0x80 0x3 0x64 0x4 0x30 0x3 0xff 0xc 0x5 0x31 0x5 0x3 0x1 0x2 0x6 0x31 0x5 0x1 0xa 0x0 0x3a (####d#0####1#####1##\n#:slight_smile: <0x7724a520>
02 03/07/16 18:17:16.987 ZWaveNode::HandlePollUpdate node 55 device 102 Ignoring secure command for unsecure command class 0x8f command 0x1 m_iFrameID 158/21830896 data 0x4 0x3 0x80 0x3 0x64 0x4 0x30 0x3 0xff 0xc 0x5 0x31 0x5 0x3 0x1 0x2 0x6 0x31 0x5 0x1 0xa 0x0 0x3a (####d#0####1#####1##\n#:slight_smile: <0x7724a520>
24 03/07/16 18:17:16.987 ZWaveJobHandler::DoReceivedFrame m_iFrameID 158 done 1 <[/size]

7

In all of this you have not yet stated whether or not the motion sensor displays that it has been tripped in the GUI, let alone the log file.

I suspect that the motion sensor is unable to communicate with Vera. This may be due to a communication/routing issue, but it can also be due to Vera not having configured the battery operated device to inform Vera when tripped. I suspect, though I don’t have enough information, that the old devices have not been configured/reconfigured to point to the new Vera and that the new device hasn’t been healed and is unable to route to Vera, even though it knows it should.

You must first get the motion sensors to notify Vera of their trip/untrip state. Then the scenes should work and if they don’t you can troubleshoot further.

Basic troubleshooting steps for every Z-Wave device:

[ul][li]Exclude then include the device, next to Vera.[/li]
[li]Does the device work next to Vera? [/li]
[li]Use the device in your scene, next to Vera. If it works, you’ve proven that the device and scene are fine. Otherwise, you need to find out why they failed.[/li]

[li]After everything is working, then you need to install the device in its final location and allow the network to heal, or you need to exclude the device and include it in its final location and may still need to allow the network to heal. [/li][/ul][/quote]

This is what I found out after a conversation with MCV technical support. The reason that none of my Scenes are firing from Device or Schedule triggers is because no “House Mode” was selected. When you transfer the system From Vera 3/UI5 to Vera Plus, no House Mode is selected as the default for each Scene. It is obvious NOW that no Scene will ever fire from any trigger is you haven’t checked Away, Home, Vacation, etc. This isn’t something that was in any instruction provided by MCV and I’m sure it isn’t widely known. Another thing that happened was all of my device triggers on the Vera Plus were put in the Armed state but they were never in that state on Vera 3/UI5.

Also had a conversation about the “Can’t Detect Device” issues. MCV is fully aware now about this issue and is working on a patch for hopefully the next version of update for UI7. MCV says there is a workaround that can be run that ignores all the Can’t Detects.

8

I was surprised by house modes too last week. I figured it out after my evening lights on scene didn’t fire. They should set the modes to “true” when doing a UI5 conversion.

I’m not wild about ui7, but I do like the Vera Plus hardware and zwave performance.