Announcement

Collapse
No announcement yet.

Vers 3_1_13_2 ready for testing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • vasrc
    replied
    Originally posted by mattm55 View Post
    Captured the Low Battery for me without an event on this one.

    -Matt
    Right, the event is just for external notification (ie SMS, email, Speaker, etc)

    I've had 3 low batteries now (about right considering the install date), and one Sensor obfuscated on the Smoke detector.

    Z

    Leave a comment:


  • mattm55
    replied
    Captured the Low Battery for me without an event on this one.

    -Matt
    Attached Files

    Leave a comment:


  • ramarnat
    replied
    Linux and Concord4 and SQLite error.
    I am getting the sqlite errors with the plugin on a pi2 running raspbian. Of interest is that there are two instances of the System.Data.SQLite.dll with different owners and compile dates.
    To fix copy the dll in bin to bin/CONCORD so they are the same version (overwriting the one in the concord directory)

    Checking the assembly info shows the dlls to have the same version, but obviously something is different

    Leave a comment:


  • sesykes71
    replied
    Linux and Concord4 and SQLite error.

    I am getting the sqlite errors with the plugin on a pi2 running raspbian. Of interest is that there are two instances of the System.Data.SQLite.dll with different owners and compile dates.



    pi@raspberrypi ~/HomeSeer/bin/CONCORD $ ls -l
    total 936
    -rw-r--r-- 1 root root 700928 Jul 24 2013 SQLite.Interop.dll
    -rw-r--r-- 1 root root 251392 Jul 24 2013 System.Data.SQLite.dll
    pi@raspberrypi ~/HomeSeer/bin/CONCORD $ cd ..
    pi@raspberrypi ~/HomeSeer/bin $ ls -l
    total 512
    drwxr-xr-x 2 root root 4096 Nov 7 12:30 BLLock
    drwxr-xr-x 2 root root 4096 Nov 7 16:53 CONCORD
    -rwxr-xr-x 1 pi pi 261632 Jun 1 08:49 HomeSeerUtil.dll
    -rw-r--r-- 1 pi pi 249856 Nov 13 2014 System.Data.SQLite.dll
    drwxr-xr-x 2 root root 4096 Nov 7 12:32 Z-Wave
    pi@raspberrypi ~/HomeSeer/bin $

    Steve

    Leave a comment:


  • mattm55
    replied
    Looks good to me. Haven't had much time to debug but no errors here.

    Been working out a GEM > Dashbox com problem all weekend.

    ~Oh, if you think its a stable, final version, send me over the source so I can have a backup and get in git someday.
    Thanks.

    Matt

    Leave a comment:


  • vasrc
    replied
    Originally posted by vasrc View Post
    Need someone to test 3_1_13_2 on Linux (Telefragger is doing Windows).
    Since the updater is "broken" with Dropbox links, PM me and I'll give you the direct link.

    More cleanup to address Panel comm lost and restarts. Also now displays Trouble alarms on the device page as well as the previously supported Log page.

    Thanks,
    Z
    Thanks for the feedback.
    Last chance for comments. I'm going to release tonight.. I believe I've worked out all the bugs, especially the ones on Linux.

    Z

    Leave a comment:


  • vasrc
    replied
    Originally posted by TeleFragger View Post
    Weirdest part is there is no * at touchpad and when anything is tripped there always is...

    anyway... I will replace batteries tonight...

    here is a few things to look over...

    did the stop/enable plugin and this is stuff from the logs..
    Sorry wrong debug msg

    You need Concord Debug Log to HS checked and then restart the plugin. You'll need to know the devRef of the device as well.
    What you're looking for looks like this (There's a lot in Debug)
    Date/time CONCORD Debug ZoneStatus(devRef)-myZoneCondition = xxxx, bit0=x, bit1=x, bit2=x, bit3=x, bit4=x
    It's bit3 I need.
    You'll also get:
    Date/time CONCORD Debug ZoneStatus() - Set Trouble alarm for Zone "Zone#"
    or
    Date/Time CONCORD Debug ZoneStatus() - Trouble is clear on Zone "Zone#"

    Z

    Leave a comment:


  • TeleFragger
    replied
    Originally posted by vasrc View Post
    To troubleshoot, turn on the Comm Debug and then stop and start the plugin (to re-init the manual device lookup and not wait for the internal timer to kick off). Look for that device in the HS log (assuming you turned on Debug to HS) You'll be looking for a line that has that device name and ends with .... Sts= X.. If X is 0, then the trouble alarm should be reset. If it's 8, then there's still a trouble.

    What is the device value currently (look at the device Advanced page to find out.

    Did you check the Status Graphics values I sent earlier?

    Typically, the smoke detectors (wireless at least) use 2- lithium CR123 batteries.

    Z
    Weirdest part is there is no * at touchpad and when anything is tripped there always is...

    anyway... I will replace batteries tonight...

    here is a few thi8ngs to look over...

    did the stop/enable plugin and this is stuff from the logs..
    Attached Files

    Leave a comment:


  • vasrc
    replied
    Originally posted by TeleFragger View Post
    so this is weird...

    I went into the plugin and panel and don't see the trouble anymore. I then went into configuration and checked off all 4 logs...

    item still shows troubled on device screen...

    and this is all I can find in one of the log files..

    10/30/2015 1:36:47 PM~CONCORD~|Oct 30, 2015 1:36:47 PM|Trouble|Zone 17 Foyer Smoke Detector|1
    10/30/2015 1:36:52 PM~CONCORD~|Oct 30, 2015 1:36:52 PM|Communications Restored|Zone 205 Connection Status|1

    I cant find anywhere what the fault is.. batteries? going to get some and replace them just in case... I don't have any 9v right now...
    To troubleshoot, turn on the Comm Debug and then stop and start the plugin (to re-init the manual device lookup and not wait for the internal timer to kick off). Look for that device in the HS log (assuming you turned on Debug to HS) You'll be looking for a line that has that device name and ends with .... Sts= X.. If X is 0, then the trouble alarm should be reset. If it's 8, then there's still a trouble.

    What is the device value currently (look at the device Advanced page to find out.

    Did you check the Status Graphics values I sent earlier?

    Typically, the smoke detectors (wireless at least) use 2- lithium CR123 batteries.

    Z

    Leave a comment:


  • TeleFragger
    replied
    so this is weird...

    I went into the plugin and panel and don't see the trouble anymore. I then went into configuration and checked off all 4 logs...

    item still shows troubled on device screen...

    and this is all I can find in one of the log files..

    10/30/2015 1:36:47 PM~CONCORD~|Oct 30, 2015 1:36:47 PM|Trouble|Zone 17 Foyer Smoke Detector|1
    10/30/2015 1:36:52 PM~CONCORD~|Oct 30, 2015 1:36:52 PM|Communications Restored|Zone 205 Connection Status|1

    I cant find anywhere what the fault is.. batteries? going to get some and replace them just in case... I don't have any 9v right now...

    Leave a comment:


  • vasrc
    replied
    Originally posted by knr View Post
    The panel is connected to a RS-232 to USB adapter into one of the USB ports on the HomeTroller Zee (/dev/ttyUSB1).


    Current Date/Time: 10/30/2015 10:34:28 AM
    HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.208
    Linux version: Linux HomeTrollerZeeS2 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux System Uptime: 0 Days 13 Hours 21 Minutes 55 Seconds
    IP Address: 192.168.0.161
    Number of Devices: 170
    Number of Events: 12

    Enabled Plug-Ins
    3.0.0.4: CM15A
    3.1.13.1: CONCORD
    3.0.0.68: HSTouch Server
    3.0.1.25: Z-Wave
    PM me your email address and I'll send you the link to download a new EXE to use that has some more specific debug statements related to the timer. I'm wondering if Mono on Linux isn't handling the System timers the same way as vanilla MS does.

    Thanks,
    Z

    Leave a comment:


  • knr
    replied
    The panel is connected to a RS-232 to USB adapter into one of the USB ports on the HomeTroller Zee (/dev/ttyUSB1).


    Current Date/Time: 10/30/2015 10:34:28 AM
    HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.208
    Linux version: Linux HomeTrollerZeeS2 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12 17:20:48 GMT 2015 armv7l GNU/Linux System Uptime: 0 Days 13 Hours 21 Minutes 55 Seconds
    IP Address: 192.168.0.161
    Number of Devices: 170
    Number of Events: 12

    Enabled Plug-Ins
    3.0.0.4: CM15A
    3.1.13.1: CONCORD
    3.0.0.68: HSTouch Server
    3.0.1.25: Z-Wave

    Leave a comment:


  • vasrc
    replied
    Originally posted by knr View Post
    Should this plug-in work on a HomeTroller Zee2? I can connect to the Concord4 panel but then I keep losing my connection and then reconnecting...

    Oct-29 9:26:44 PM CONCORD Comm TimerHB: Communications Lost
    Oct-29 9:26:44 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175604, mSec=642, Event=Communications Lost
    Oct-29 9:26:44 PM CONCORD Debug Setting Connection Status to: 0
    Oct-29 9:26:43 PM CONCORD Comm TimerHB: Communications Restored
    Oct-29 9:26:43 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175603, mSec=941, Event=Communications Restored
    Oct-29 9:26:43 PM CONCORD Debug Setting Connection Status to: 1
    Oct-29 9:26:40 PM CONCORD Comm TimerHB: Communications Lost
    Oct-29 9:26:40 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175600, mSec=640, Event=Communications Lost
    Oct-29 9:26:40 PM CONCORD Debug Setting Connection Status to: 0
    Oct-29 9:26:39 PM CONCORD Comm TimerHB: Communications Restored
    Oct-29 9:26:39 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175599, mSec=938, Event=Communications Restored
    Oct-29 9:26:39 PM CONCORD Debug Setting Connection Status to: 1
    Oct-29 9:26:36 PM CONCORD Comm TimerHB: Communications Lost
    Oct-29 9:26:36 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175596, mSec=635, Event=Communications Lost
    Oct-29 9:26:36 PM CONCORD Debug Setting Connection Status to: 0
    Oct-29 9:26:35 PM CONCORD Comm TimerHB: Communications Restored
    Oct-29 9:26:35 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175595, mSec=934, Event=Communications Restored
    Oct-29 9:26:35 PM CONCORD Debug Setting Connection Status to: 1
    Oct-29 9:26:32 PM CONCORD Comm TimerHB: Communications Lost
    Oct-29 9:26:32 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175592, mSec=631, Event=Communications Lost
    Oct-29 9:26:32 PM CONCORD Debug Setting Connection Status to: 0
    Oct-29 9:26:31 PM CONCORD Comm TimerHB: Communications Restored
    Oct-29 9:26:31 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175591, mSec=934, Event=Communications Restored
    Oct-29 9:26:31 PM CONCORD Debug Setting Connection Status to: 1
    Oct-29 9:26:28 PM CONCORD Comm TimerHB: Communications Lost
    Oct-29 9:26:28 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175588, mSec=629, Event=Communications Lost
    Oct-29 9:26:28 PM CONCORD Debug Setting Connection Status to: 0
    Oct-29 9:26:27 PM CONCORD Comm TimerHB: Communications Restored
    Oct-29 9:26:27 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175587, mSec=930, Event=Communications Restored
    Oct-29 9:26:27 PM CONCORD Debug Setting Connection Status to: 1
    Oct-29 9:26:24 PM CONCORD Comm TimerHB: Communications Lost
    Oct-29 9:26:24 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175584, mSec=627, Event=Communications Lost
    Not sure it's ever been tested on that platform.
    What is the serial comm interface (ie USB, serial, etc) the panel is connected to?
    Which version of HS and Concord Plugin?

    Looking at the log, it looks like an issue with the system timer, as it should be timing out every 100 secs, and fail after 10 mins, not after 1 sec.

    Thanks
    Z
    Last edited by vasrc; October 30th, 2015, 09:51 AM.

    Leave a comment:


  • knr
    replied
    Should this plug-in work on a HomeTroller Zee2? I can connect to the Concord4 panel but then I keep losing my connection and then reconnecting...

    Oct-29 9:26:44 PM CONCORD Comm TimerHB: Communications Lost
    Oct-29 9:26:44 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175604, mSec=642, Event=Communications Lost
    Oct-29 9:26:44 PM CONCORD Debug Setting Connection Status to: 0
    Oct-29 9:26:43 PM CONCORD Comm TimerHB: Communications Restored
    Oct-29 9:26:43 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175603, mSec=941, Event=Communications Restored
    Oct-29 9:26:43 PM CONCORD Debug Setting Connection Status to: 1
    Oct-29 9:26:40 PM CONCORD Comm TimerHB: Communications Lost
    Oct-29 9:26:40 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175600, mSec=640, Event=Communications Lost
    Oct-29 9:26:40 PM CONCORD Debug Setting Connection Status to: 0
    Oct-29 9:26:39 PM CONCORD Comm TimerHB: Communications Restored
    Oct-29 9:26:39 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175599, mSec=938, Event=Communications Restored
    Oct-29 9:26:39 PM CONCORD Debug Setting Connection Status to: 1
    Oct-29 9:26:36 PM CONCORD Comm TimerHB: Communications Lost
    Oct-29 9:26:36 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175596, mSec=635, Event=Communications Lost
    Oct-29 9:26:36 PM CONCORD Debug Setting Connection Status to: 0
    Oct-29 9:26:35 PM CONCORD Comm TimerHB: Communications Restored
    Oct-29 9:26:35 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175595, mSec=934, Event=Communications Restored
    Oct-29 9:26:35 PM CONCORD Debug Setting Connection Status to: 1
    Oct-29 9:26:32 PM CONCORD Comm TimerHB: Communications Lost
    Oct-29 9:26:32 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175592, mSec=631, Event=Communications Lost
    Oct-29 9:26:32 PM CONCORD Debug Setting Connection Status to: 0
    Oct-29 9:26:31 PM CONCORD Comm TimerHB: Communications Restored
    Oct-29 9:26:31 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175591, mSec=934, Event=Communications Restored
    Oct-29 9:26:31 PM CONCORD Debug Setting Connection Status to: 1
    Oct-29 9:26:28 PM CONCORD Comm TimerHB: Communications Lost
    Oct-29 9:26:28 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175588, mSec=629, Event=Communications Lost
    Oct-29 9:26:28 PM CONCORD Debug Setting Connection Status to: 0
    Oct-29 9:26:27 PM CONCORD Comm TimerHB: Communications Restored
    Oct-29 9:26:27 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175587, mSec=930, Event=Communications Restored
    Oct-29 9:26:27 PM CONCORD Debug Setting Connection Status to: 1
    Oct-29 9:26:24 PM CONCORD Comm TimerHB: Communications Lost
    Oct-29 9:26:24 PM CONCORD Debug InsertTracking() Enqueue: Zone (205), Now=1446175584, mSec=627, Event=Communications Lost

    Leave a comment:


  • vasrc
    replied
    Originally posted by TeleFragger View Post
    sorry life has had me so busy but I i will get back to this soon...
    promise..

    weird thing is even though my smoke says tripped... so does the panel log (didnt screenshot it but saw it)... so not sure why i do not have a * on the keypad
    Not a problem. I coincidentally had a Trouble alarm on our Iso Room smoke detector and the Log showed it as Low Battery (and they were), so I'm pretty sure it's working OK.

    Z

    Leave a comment:

Working...
X