Zone Bypass

Plugins & Plugin Development Unmaintained
1

I have successfully installed the Caddx plugin version 72 on UI5. Thanks for the great plugin!

I have one problem. I have disabled Zone Bypass on the NX584 chip. The configure panel also shows zone bypass being unchecked. However, when I try to change a zone from armed to bypass, nothing happens on Vera. Is there something I am doing incorrectly? I just want to arm and disarm zones locally on Vera.

Thanks.

2

That feature was only introduced in version 80.

See here for upgrading the plugin without uninstalling and reinstalling: http://forum.micasaverde.com/index.php?topic=26553.15

3

I have actually tried to upgrade to version 81 in the past, and it didn’t work. I keep getting a Lua Failure message.

Looking at the logs, I saw this message:
FileUtils::ReadURL 28/resp:0 size 0 https://plugin1.mios.com/sync_plugins2.php?PK_AccessPoint=XXXXXXXX&HW_Key=XXXXXXXX&Plugins=1018, LEAK this:110592 start:147456 to 0xa5f000 <0x2bf41680>
01 03/07/15 21:21:21.117 RAServerSync::SyncPlugins failed to sync https://plugin1.mios.com/sync_plugins2.php?PK_AccessPoint=XXXXXXXX&HW_Key=XXXXXXXX&Plugins=1018, <0x2bf41680>"

What’s wrong? Version 72 works just fine. I have not tried using versions 73-80.

I have attached a screenshot showing what happens when I first install the plugin, and then what it displays once the serial port is connected.

4

Right, well, let’s solve that, since that’s the real problem.

Looking at the logs, I saw this message:

I will need more of the log, not just a couple of lines from it. Start catching the logs, then restart the Luup engine, then wait until you get the Luup error. That’ll ensure that the actual error is in the log that you’ve captured. Please don’t worry that you’ll supply too much information. I’d prefer to trawl through hundreds of lines of logs than have to extract the information I need from half a dozen forum posts spaced over several days.

5

Sorry about the short log, here is the full log when i restarted Luup.

6

So I did some testing and I now know that version 80 works fine, with no errors. Version 81 creates the Lua failure error.

7

Since version 81 supplies only a feature you probably don’t care about (X10 control) you can safely stay on version 80 and get everything you need.

Unfortunately the log you captured was truncated and doesn’t show any Lua error on the plugin (in fact, it shows the plugin successfully starting and setting state on devices). If you are up to installing the broken version 81 again and catching a longer log, I’d be grateful (or if you just want to stay on the version that works for you, that’s fine with me too).

8

Wow, I suck at log captures! ;D I copied everything before and after a reload until the log stopped.

This is what I thought I had done before, but hopefully I got it this time!!

BTW, I upgraded by just uploading the version 81 files, is that the proper way to upgrade?

9

Still no luck. Have you enabled verbose logging (“Debug to Luup log”) on the Configure tab? You might have to downgrade to version 80 to get to the tab to turn it on, then upgrade to 81 again.

BTW, I upgraded by just uploading the version 81 files, is that the proper way to upgrade?

Yep.

10

Here it is with verbose logging.

11

… sorry … there are still no errors in that log. The log shows the plugin happily starting up and scanning all 22 of your zones.

I can’t tell if you need to wait longer before stopping the capture, or if the error isn’t being reported in the log at all. Normally when you get a Lua Startup error like the one you posted the screen capture of, it’s because there is a really prominent error message in the log. But in this case, I’m not seeing an error like that.

Thanks, sincerely, for trying. If you’re running happily on version 80, just stay there. There are unlikely to be new releases of this plugin anyway, so you won’t be missing out on anything.