Currently I see no pattern. I can change one sensor from bypassed to armed and the last tripped resets to now along with half the other sensors even tho non of them tripped. Any why only half vs all or just one i have no idea.
EDIT: it doesn’t do this with the virtual motion senor plugin im using for my camera’s. Those motions are working fine. But the motions from the alarm panel are the same screwy way the door sensors from the alarm are.
If LastTrip is changing while a zone is untripped then it can’t be the plugin doing it. The only place in the olugin code that updates LastTrip is in an “if tripped == 1” test.
A sensor doesn’t have to be tripped for it to update. For example no one is home now and all doors and windows were closed when I left, they still show that and no alerts or anything has went off that they changed state… But If I look threw the sensors and the times below more then 75% of them say last tripped was an hour ago and give the time of 8:30am which I was at work by then. Funny part is those 75% all show matching time of 8:30am but a few don’t and I’m unsure of the link or lack of between them.
I been using a unix timestamp converter and checking the “LastTripped” time to what imperihome is showing and that seems to match up.
The only other thing I need to test is the armed vs not armed. I used to run with all of them armed. But some interior doors always stay open and was causing my UI (that I don’t use much) to not look so pretty with the alerts. So I un armed all my sensors since PLEG is set for either and I do my own logic vs. arming them or not.
I noticed that in the advanced menu under the sensors there is both a “LastTrip” and a “ArmedTripped” along with a “IgnoreTripTime”
I have never used any but the “LastTrip” before.
Hi,
I’m new to the Vera, I have a Vera Edge with the latest firmware and the latest version of the plugin, connected via a USB to serial to my Caddx panel. I Know the Caddx panel very well, I wrote a plugin for Homeseer for it…
The problem I have is that I can not connect to the panel. I read to the forum but could not find a resolution.
I used the same cable and USB to serial cable as I use for my HomeSeer system, so that could not be an issue.
I configured the serial interface butI get errors:
GET_LANG(system_error,System error) : Device: 3. Fail to load implementation file D_Codeset_1091.xml.lzo
Caddx NX584 Security System[8] : Running Lua Startup
It looks like it never ends the Lua startup…
Any idea in what direction I have to look for a solution ?
[quote=“RdP, post:84, topic:182482”]Hi,
I’m new to the Vera, I have a Vera Edge with the latest firmware and the latest version of the plugin, connected via a USB to serial to my Caddx panel. I Know the Caddx panel very well, I wrote a plugin for Homeseer for it…
The problem I have is that I can not connect to the panel. I read to the forum but could not find a resolution.
I used the same cable and USB to serial cable as I use for my HomeSeer system, so that could not be an issue.
I configured the serial interface butI get errors:
GET_LANG(system_error,System error) : Device: 3. Fail to load implementation file D_Codeset_1091.xml.lzo
Caddx NX584 Security System[8] : Running Lua Startup
It looks like it never ends the Lua startup…
Any idea in what direction I have to look for a solution ?[/quote]
I don’t know those errors and I might be way outta line here but here’s my 2 cents.
I know some USB to Serials (depending on the chip in it) don’t work on VERA… But I think if you can see the usb to serial converter in Apps/develop apps/ serial port configuration your probley good to go. Also in that same window you need to make sure your setting are correct and you have it pointing to what device you using (in this case “Caddx NX584 Security System []” should be what you chose). Has all that been done and seem good? Buad rate is matching what you have set in the alarm panel, Data bits 8 stop bits 1
Annoyingly, I wrote a response but it has disappeared. I will try again.
Catch a Luup log while the plugin is starting up. This will tell you if it is in an infinite loop (and maybe what is looping) or if the bytes the plugin is sending out to the panel are just getting blackholed. Being permanently stuck in startup is symptomatic of the Vera not knowing how to communicate with, or not having enough power to drive, the USB to Serial adapter. I’ve talked about this before, so find any of my prior posts that recommend a powered USB hub.
I’m not convinced that the other error you are getting is related. It’s completely unfamiliar to me.
futzle - thank you for this plugin. It clearly represents a lot of personal time invested, and a ton of your personal time answer community questions. Over the holidays, I tried both Vera Edge and HS3 with an always on desktop over the holidays with my Caddx panel. I had no intention of trying HS3, but I found Vera use interface design decisions like the one you mention above to be deal breakers for the Vera. I also got the general impression that the Vera hardware specs hasn’t quite caught up with the ambitions of the platform. Ten years ago before three young kids at home, I would have enjoyed the challenge of reviewing logs or source to figure out an issue, but with time at a premium, the Vera platform is a bit frustrating. I don’t want my home control box owning zone behavior of my security system, and remote bypass control is a useful to me. The stability of UI7 serial connection to panel was marginal on Vera and 100% stable on PC with HS3. I tried Vera with and without a powered USB hub with no better luck. I’m sure it was solvable, but I just lost patience and switched to HS3. So anyways, I just wanted to sincerely thank you for contributing to the hobby. I’m not sure what to do with my Vera… perhaps someday it will support IFTTT and I can think of something clever.
[quote=“RdP, post:84, topic:182482”]Hi,
I’m new to the Vera, I have a Vera Edge with the latest firmware and the latest version of the plugin, connected via a USB to serial to my Caddx panel. I Know the Caddx panel very well, I wrote a plugin for Homeseer for it…
The problem I have is that I can not connect to the panel. I read to the forum but could not find a resolution.
I used the same cable and USB to serial cable as I use for my HomeSeer system, so that could not be an issue.
I configured the serial interface butI get errors:
GET_LANG(system_error,System error) : Device: 3. Fail to load implementation file D_Codeset_1091.xml.lzo
Caddx NX584 Security System[8] : Running Lua Startup
It looks like it never ends the Lua startup…
Any idea in what direction I have to look for a solution ?[/quote]
I picked up home automation hobby over holidays after a several year break from X10. I tried both the Vera and HS3 with the Caddx panel. I was able to get serial to connect on Vera and work for a while with the plugin, but the connection would drop sporadically (and I found the Vera interface to be difficult to wrestle into the behavior I wanted efficiently) so I ended up using HS3. I agree powered USB hub should help, and also check the chipset of the serial converter. I hesitate to tell you the one I am using because it has been 100% stable with HS3 on a PC for almost a month now, but was much less so on the Vera over a two day period. I am pretty sure changing the serial converter would have resolved the problem, but I just altogether lost patience with Vera.
I am using the Caddx Networx 8V2 with the NX-584E via the Wifi to Serial. I’ve updated to your latest 81 version and was able to add all the zones and able to arm/disarm/stay the system via GUI and iOS. However, I do not see a “bypass” option of each zone. Under Devices, I see all my 28 (skip 3-8) zones. For some reasons, zones 9-18 are always ARMED, and zones 1-2, 19-28 are always DISARMED. These DISARMED zones will not allow me a Arm. Regardless if I arm/disarm/stay the system, these status always be the same. Am I doing something wrong during the programming? I am using the latest UI7 and your plugin was download from the App. I did not change any files.
Tying the Vera sensor’s arm state to the Panel zone’s bypass state was an experiment which worked well in UI5 but broke in UI7. MCV added House Mode functionality to UI7 which asserts ownership of a sensor’s arm/bypass state. With UI7 I recommend disabling the configuration location for “toggle bypass” in the alarm panel settings. If you do this then the arm/bypass state of each sensor in Vera is independent of the zone’s bypass state in the panel. You can turn them on or off and have no effect at all on the corresponding zone in the panel.
The arm/stay/disarmed state of the partition is entirely separate. Don’t conflate it with Vera sensor arming.
I’ve talked about this before on the forum, at length. Go look at those discussions.
I have a couple of situations with my current VERA3 and also some comments on the new unit VERAEdge Plus which I will be planning to migrate to over the next couple of weeks if all works properly.
With the Vera3 unit UI5 i have a successful working system with my GE NX8e board and the RS232-USB interface to VERA3 using version 78 this has been working well all this time perfectly
However today when I tried to upgrade to the latest version 81, the VERA3 UI5 one app is loaded and connected to the system properly, on the GE App window where I can confiture it gives me a lua failure message. I had to restore the UI5 backup to get back on v78 to stay with a workable version.
Please let me know if there is something that I need to do different for this.
Separately I am upgrading to the new VERAEdge Plus and UI7 and version 81 is working ok i.e. arming/disarming etc, but I am not sure when I scanned for zones only Zone 1 was read correctly the others gave me an errorI will need to try this again and do a hardware reset to see if it solves, otherwise will confirm back to you if something is not working. Again my properly working baseline is my Vera3 UI5 v78.
I am planning over the next couple of weeks to migrate everything to the New Vera Edge Plus on UI7 and will continue to test the GE App for any anomalies. (The Vera Edge Plus server at Vera is officially out on 2/18 but using the Current Vera Edge software temporarily for another week)
This doesn’t surprise me greatly. I haven’t had a UI5 Vera for a couple of years. My advice is don’t upgrade. No new features are being added so unless you have a specific bug that a later version fixes, stay where you are.
2. Separately I am upgrading to the new VERAEdge Plus and UI7 and version 81 is working ok i.e. arming/disarming etc, but I am not sure when I scanned for zones only Zone 1 was read correctly the others gave me an error
Please report back on this. I can’t test zone scanning because it requires an LCD keypad which I don’t have.
I should have a response by the weekend once Vera set’s their servers up for this new model of Vera Edge Plus, then be able to run it and see how it tests out.
Basically Vera Edge Plus added additional RF capabilities like Zigbee and Bluetooth features.
Meanwhile if I had to go get a download of this previous version 78, where is the best way to download, used to be able to get prior versions from the MIOS store, but now that option is not available only showing to uninstall without a versioning drop down.
Futzle, sorry for one more clarifying question i linked to github but did not see a reference to get to V78 of your software as a download i am assuming its code for the latest version. could you point me there so i can save the necessary files to restore in the case my Vera3 UI5 crashes and I need to reload those version specific files.
Also if possible please provide as well the files I need to upload into vera manually for V78.
Thanks so much for you support to this great app!
As mentioned I am going to provide you full feedback on the latest version on the new Vera Plus using UI7.
That’s the second link in my previous post. GitHub doesn’t number its versions like apps.mios.com, but I know from inspection that revision 136cbe14a7 is the one you want. There’s a “download ZIP” button on that page which fetches that version of the files.
Hi,
I am really at a loss. I have had a Vera 2 running UI5 for 3 years working great with the serial to USP dongle and Futzle code.
Now i have upgraded to a Vera Edge with UI7 and went thru the conversion process but no success, shows that the NX584 is not available. I have read thru the forums and tried the 1018 update and then i tried downloading the files from the Github and loading them in but still doesnt work.
I moved back to the Vera2 and tried to upgrade from 69 to 81 and now that is broken. Any ideas?
Specifics:
Serial is pl2302
UI5 1.5.622
works with 69 but not 81
integlikewhoa did you find a solution for the LastTrip updating for multiple sensors, i see the same issue now, it was working fine for long time.
[quote=“integlikewhoa, post:77, topic:182482”]Anyone running the new 7.0.12 beta and have last tripped false times? I’m using imperihome and before beta ui7 it was reading right. I seem to have weird issues now where all sensors have similar tripped times of a few min ago even though they haven’t been triggered.
Using the device advanced tab in vera and the unix time that also seems to not match my imperihome app nor the last time the device was actually tripped.
My VeraLite running UI6 seems to be severly corrupted and I have no clean backup. I have a bunch of phantom devices that cannot be deleted, and some occasional unexpected restarts, but for the most part, the system is working O.K. I am considering purchasing a Vera Plus and installing UI7.
I consider the Caddx Plugin the most important part of my Vera system and am hesitant to upgrade to UI7 as the Caddx Plugin support is pretty quiet. Given the corruption of my current system, I would do a clean install rather than an upgrade.
Are there Caddx Plugin users on UI7, and is it working O.K.?
I understand from other posts, here, that the current Caddx Plugin files are on GitHub. I looked at them, but really don’t know what to do with them. Do I just download all of them (6+ files)? Then how do I load them into UI7? Does the order of loading them matter?
I would really appreciate any advise, suggestions, or support.