I have been using this plugin for awhile now. To the developer- thank you!
I am trying to set up a scene that triggers a certain state, let’s say “stay”, which I need to reverse to the original after let’s say 8 hours. The plugin panel shows 2 arrows for the reversing action with a delay but nothing happens after the time passes.
Has anybody been able to accomplish this?
[quote=“MikeH”]The back light stays on and the it keeps flashing between the faulted zone & the “Alarm Canceled” message. I punch my code in and the off button multiple times, but
it doesn’t do anything. Then when I use vera U15 on my computer and click on the “DisArm” button it clears it.[/quote]
I had the same issue. Exactly as you describe above. If I want to clear the fault from the keypad, I enter my code and hit “Away” instead of off. I don’t know why it works, but it does.
Did you set the serial port baud rate to 115200 in the UI? Also make sure you list every keypad address in-use. If either of those aren’t correct it won’t respond. That was what was giving me the same error.
http://code.mios.com/trac/mios_vista-alarm-panel-ad2usb/wiki/UI5
[/quote]
I made sure the baud rate was correct and tried to add the KeyPad Address, but the variable that was there is “locked” and won’t allow entry… I added a new variable, but not sure its working properly if its listed twice… I can’t add screen prints because the forum says the upload folder is full…
Edit: January 02, 2015
Ok… I uninstalled and re-installed the plug-in. I am now able to enter the KeyPadAddress, but it doesn’t save. I see it there after entering it, but when I navigate away from the advanced tab and come back, it is gone…
Edit: January 04, 2015
Ok… Not sure what has happened, but the plug-in is now working… The KeyPadAddress is showing the correct address, and I can arm and disarm the alarm… I will now start testing some of the advanced features…
So…I have a Vera 3 and when I upgraded to UI7 the alarm functions still work except I have an error on the panel. I cannot seem to get rid of the error (see screen shot).
If I click on Away the alarm goes to Away. This is the only thing that isn’t working.
Please help.
Any updates on the status of usb drivers issue patch for Vera Edge? There was a mention that it should release in the first weeks of January, so with today being about mid-January I was wondering if anyone heard any updates? I sent an inquiry to Vera support but haven’t heard back yet.
Read up a few posts… the kernel driver hasn’t been the problem since at least late December and I posted a workaround for the remaining issues.
Read up a few posts… the kernel driver hasn’t been the problem since at least late December and I posted a workaround for the remaining issues.[/quote]Thanks, I will give it a shot again, I am pretty sure it didn’t work for me and was saying device not found (or something like that) but I will re-check tonight and update.
I must agree. UI5 was more or less rock solid and stable, UI6 and 7 have been really subpar. Not what I would expect from a products rolling out to the masses. This is base functionality. The home automation market is rapidly becoming mainstream. My advice would be for the Vera team to focus on quality vs. features right now and stabilize the platform. Just my thoughts. Hope the Vera Team takes it into consideration.
Got a reply from support regarding the USB issue:
As far as I’m aware the issue with the USB has a high priority and should be available in the January software release, which is typically release in the last week of January. So you should expect it to be available in the next two weeks.
sound-mind: Thanks for posting a workardound, but I don’t want to go messing with scripts. Plus I think you mentioned that settings were lost after reboot, right?
[quote=“ykamenet, post:889, topic:168766”]Got a reply from support regarding the USB issue:
As far as I’m aware the issue with the USB has a high priority and should be available in the January software release, which is typically release in the last week of January. So you should expect it to be available in the next two weeks.
sound-mind: Thanks for posting a workardound, but I don’t want to go messing with scripts. Plus I think you mentioned that settings were lost after reboot, right?[/quote]
The serial port baud rate and associated device are lost on reboot.
I rely pretty heavily on the alarm to perform a lot of tasks, like turning on internal security cameras when we set the alarm to away. Without this, I have to manually trigger a scene to turn them on, so the workaround adds enough value for me to maintain it across reboots, which to-date have only happened when I reboot the device after, e,g, moving close to a device to pair with it.
When a full fix comes out I’ll review it and unpatch my Vera if it is functional. However, I have very little faith in the Vera team to do it correctly.
Personally, I don’t know how they were planning on fixing it but I think my approach is pretty solid. They’re going to have to modify that script regardless due to a syntax error that leads to a segfault. The approach also addresses differences in USB product IDs ensuring the kernel module gets loaded across variances. I think relying on the vendor ID is suddicient for these devices. They could fix that part in other ways in userspace, though comments from support indicate they’re trying to fix it in kernel space which seems like the wrong approach since the module is already perfectly functional.
FWIW, I understand mucking about in the firmware image on an embedded device is off-putting. I’ve been using Linux for 20 years, some of that time in embedded Linux environment including OpenWRT. If I break something, I can fix it, whereas following some random person’s ramblings on a forum could put others in a bad place. I probably should have caveated the script post with something along those lines.
Sound-Mind: I completely agree and am in the same boat. I’m exploring other solutions but haven’t been able to find any platforms that support ademco. Please let me know if you go with a different platform.
Sent from my iPhone using Tapatalk
sound-mind - I don’t have any issues with a reboot… I don’t lose any of my setting…
I have since added 6 new devices, and 2 new plug-ins… DataYours2 required a number of re-boots mostly to able to get my NAS mounted… My settings have remained throughout…
Next up is to get my logs sent over to the NAS mount…
[quote=“Vandamme23, post:892, topic:168766”]sound-mind - I don’t have any issues with a reboot… I don’t lose any of my setting…
I have since added 6 new devices, and 2 new plug-ins… DataYours2 required a number of re-boots mostly to able to get my NAS mounted… My settings have remained throughout…
Next up is to get my logs sent over to the NAS mount…[/quote]
Funny that you mention that - I soft rebooted last night via the web UI. I had added a device and the UI refused to store the room I was selecting, it was always showing up in No Room (reboot fixed that problem). Regardless, the serial port info was retained across a soft boot. I wonder if it is either fixed, or only occurs across a hard boot. I haven’t tried yet, but I wonder if it is being stored in a RAM-backed memory region that contains persistent data until power loss.
I’ll try a cold boot today and post back.
[quote=“sound-mind, post:893, topic:168766”][quote=“Vandamme23, post:892, topic:168766”]sound-mind - I don’t have any issues with a reboot… I don’t lose any of my setting…
I have since added 6 new devices, and 2 new plug-ins… DataYours2 required a number of re-boots mostly to able to get my NAS mounted… My settings have remained throughout…
Next up is to get my logs sent over to the NAS mount…[/quote]
Funny that you mention that - I soft rebooted last night via the web UI. I had added a device and the UI refused to store the room I was selecting, it was always showing up in No Room (reboot fixed that problem). Regardless, the serial port info was retained across a soft boot. I wonder if it is either fixed, or only occurs across a hard boot. I haven’t tried yet, but I wonder if it is being stored in a RAM-backed memory region that contains persistent data until power loss.
I’ll try a cold boot today and post back.[/quote]
I finally got around to doing a cold boot and I no longer see the behavior in which the serial settings are lost. I’m still running the same firmware version, so I have no idea what was possibly causing that before, and why it is no longer happening. But with things 100% functional, I also don’t care 
The only time the serial port settings are lost is when vera boots up and does not see the AD2USB, like when you unplug it and boot it up somewhere else to include a device. this is one of the reasons I try to always include devices using full power inclusion.
I have a scene set up in vera to turn the lights on when I go downstairs and get a drink of water or something late at night. It uses my wired motion detector connected to a Vista 20P alarm panel. A AD2USB is connected to the panel also. It works great except when I have the alarm set in “Stay” mode. When its in “Stay” mode it doesn’t report anything to the keypads or the AD2USB. Is there a way to have the Vista 20P report a fault on the motion detector when its armed in “Stay” mode?
Mike, I use PLEG for this. It has the option to set INPUTS, CONDITIONS, and ACTIONS. Together these act like scenes. I have one setup to activate when ‘Motion Detector detects motion whether is armed or disarmed’. This allows me to use all my Alarms sensors as triggers to control actions whether or not the alarm is actually armed…
Vandamme23,
I use PLEG also. Are you sure it works when the system is armed? What alarm panel do you have? When my system is armed “stay” it doesn’t appear to send
any messages to my keypads or the AD2USB. It just shows “Armed in Stay” Mode.
No… The Vista panels will not report faults on any partition that is armed. It will only report alarms and troubles for armed partitions (this is a limitation of the panel not of the interface - AD2USB, EVL3, VAM, etc)
A workaround is to place any sensors that are used JUST for monitoring purposes into a partition that is never armed (assuming your panel supports partitions - Vista 20P or higher)…
Cybrmage,
I have the Vista 20P. Would that be difficult to setup? I pretty much have everything setup the way I like it, except for the motion detector not working when in stay mode. Would it involve just going into zone programming and switch the partition to “2”? Could the AD2USB be used for 2 partitions? I would want the motion detectors to arm in “away” mode.