I have been back and forth on this with the EVL4 and Vera on making this plugin work. I have tried to reconfigure this several times without success. If I login to the EVL4 Website http:// of the EVL4, I can arm and disarm without issue. When I do the same from Vera, I get errors in the execution of the of commands to arm/disarm.
Does anyone know why I cannot send the command from the Vera to the EVL4? There is no firewall between the two devices and all shows configured properly.
I have been back and forth on this with the EVL4 and Vera on making this plugin work. I have tried to reconfigure this several times without success. If I login to the EVL4 Website http:// of the EVL4, I can arm and disarm without issue. When I do the same from Vera, I get errors in the execution of the of commands to arm/disarm.
Does anyone know why I cannot send the command from the Vera to the EVL4? There is no firewall between the two devices and all shows configured properly.
Yes, I have seen this before. I am not sure why, but the LuaUPnP.log is showing the delays in sending the commands. Everything in the document I have configured exactly this way. It is just odd that I am get 20+ second delays in the logs which leads me to believe the command is not leaving Vera to get to the EVL4.
What leads me to believe this is that the plugin is showing this message in the logs.
50 09/27/17 7:35:00.030 luup_log:220: DSCAlarmPanel: debug cannot send command: ‘030’ <0x72786520>
01 09/27/17 7:35:00.030 LUAINTERFACE::CALLFUNCTION_JOB DEVICE 220 FUNCTION SALARMPARTITION2_ALARMPARTITION2_REQUESTARMMODE_RUN TOOK 30 SECONDS <0X72786520>
And I think this has something to do when I install after removal as it says “Config: config data was not found. Waiting for it…” Attached screenshot
[quote=“gibby”]Did you change the default user/pass of the evl4?
Do the zones show up and do the trip like they should?[/quote]I did not change the username and password. I will after I get this working. Zones show up, but vera does not allow me to change the status of the alarm. I get these errors in the logs which makes me think the command is timing out and not leaving Vera controller.
If I open a door, it does not update the Arm/disarm status in Vera. Furthermore, when I arm the alarm, it does not update the status on partition 1 as seen inn the picture.
I keep coming back to this in the LuaUPNP.log file as the Web UI does not give me any hints to what the error is, but this log does.
50 09/27/17 7:35:00.030 luup_log:220: DSCAlarmPanel: debug cannot send command: ‘030’ <0x72786520>
I have configured this many times, and have installed the DSC plugin at least a dozen times trying to get this one working. I have even added a NAT and Any/any rules to ensure the two devices can communicate. What I am missing is that I don’t see the command leaving Vera which corresponds to the error above.
I have added a few screenshots of the configuration to show that everything is configured according to the link you sent previously.
[quote=“bmurph213, post:7, topic:197278”]If I open a door, it does not update the Arm/disarm status in Vera. Furthermore, when I arm the alarm, it does not update the status on partition 1 as seen inn the picture.
I keep coming back to this in the LuaUPNP.log file as the Web UI does not give me any hints to what the error is, but this log does.
50 09/27/17 7:35:00.030 luup_log:220: DSCAlarmPanel: debug cannot send command: ‘030’ <0x72786520>
I have configured this many times, and have installed the DSC plugin at least a dozen times trying to get this one working. I have even added a NAT and Any/any rules to ensure the two devices can communicate. What I am missing is that I don’t see the command leaving Vera which corresponds to the error above.
I have added a few screenshots of the configuration to show that everything is configured according to the link you sent previously.[/quote]
So Arm/disarm status will not update when a zone is open, the zone just goes tripped/secured.
Why would you need to add a NAT or Any/any rules? Are these not on the same subnet/network?
Login to vera via ssh and see if can ping or telnet to the EVL4.
[quote=“gibby”][quote=“bmurph213, post:7, topic:197278”]If I open a door, it does not update the Arm/disarm status in Vera. Furthermore, when I arm the alarm, it does not update the status on partition 1 as seen inn the picture.
I keep coming back to this in the LuaUPNP.log file as the Web UI does not give me any hints to what the error is, but this log does.
50 09/27/17 7:35:00.030 luup_log:220: DSCAlarmPanel: debug cannot send command: ‘030’ <0x72786520>
I have configured this many times, and have installed the DSC plugin at least a dozen times trying to get this one working. I have even added a NAT and Any/any rules to ensure the two devices can communicate. What I am missing is that I don’t see the command leaving Vera which corresponds to the error above.
I have added a few screenshots of the configuration to show that everything is configured according to the link you sent previously.[/quote]
So Arm/disarm status will not update when a zone is open, the zone just goes tripped/secured.
Why would you need to add a NAT or Any/any rules? Are these not on the same subnet/network?
Login to vera via ssh and see if can ping or telnet to the EVL4.[/quote]They are not on the same network. I can ping from the Vera to the EVL4 over the NAT or the real ip address.
[quote=“bmurph213, post:9, topic:197278”][quote=“gibby”][quote=“bmurph213, post:7, topic:197278”]If I open a door, it does not update the Arm/disarm status in Vera. Furthermore, when I arm the alarm, it does not update the status on partition 1 as seen inn the picture.
I keep coming back to this in the LuaUPNP.log file as the Web UI does not give me any hints to what the error is, but this log does.
50 09/27/17 7:35:00.030 luup_log:220: DSCAlarmPanel: debug cannot send command: ‘030’ <0x72786520>
I have configured this many times, and have installed the DSC plugin at least a dozen times trying to get this one working. I have even added a NAT and Any/any rules to ensure the two devices can communicate. What I am missing is that I don’t see the command leaving Vera which corresponds to the error above.
I have added a few screenshots of the configuration to show that everything is configured according to the link you sent previously.[/quote]
So Arm/disarm status will not update when a zone is open, the zone just goes tripped/secured.
Why would you need to add a NAT or Any/any rules? Are these not on the same subnet/network?
Login to vera via ssh and see if can ping or telnet to the EVL4.[/quote]They are not on the same network. I can ping from the Vera to the EVL4 over the NAT or the real ip address.
Sent from my Nexus 6P using Tapatalk[/quote]
From vera can you telnet to EVL4 on port 4025 or 80.
On 4025 you should get the following:
Connection closed by foreign host