Missed Events #82
Comments
|
Tell me some more. Ademco panel or DSC. Best |
|
Ademco. I’m using Hubitat but I’m referring to the events tab in the web app so I don’t think it’s related to the smart home stuff. I believe I’m fairly recently updated. Is there a quick way to pull the version to give you?
… On Nov 5, 2019, at 9:25 PM, Sean Mathews ***@***.***> wrote:
Tell me some more. Ademco panel or DSC.
Smartthings or ?
How updated is your AD2pi appliance software.
Best
Sean M.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
@f34rdotcom Firmware is 2.2a.8.8, webapp is v0.8.5-7-gbb5f032 Are there any other version #s that would be useful? |
|
Any thoughts? Happy to do whatever I can to track it down. |
|
Ok hubitat only uses ser2sock on port 10000.
So I expect if the events tab is not active the telnet will also have
issues.
Please test telnet using putty directly or from a shell on
alarmdecoder.local and then inside of raspbian 'telnet localhost 10000'
The default image for the pi after a few reboots has ser2sock already
running and connected to the AD2Pi so it would be zero conf for hubitat.
Just need to be sure the AD2 itself is setup with your panel via telent.
Sorry I dropped this. It happens just keep the thread alive and I will give
it cycles.
Best
Sean Mathews
On the webapp under settings advanced
…On Tue, Nov 5, 2019, 7:43 PM dcmeglio ***@***.***> wrote:
Ademco. I’m using Hubitat but I’m referring to the events tab in the web
app so I don’t think it’s related to the smart home stuff. I believe I’m
fairly recently updated. Is there a quick way to pull the version to give
you?
> On Nov 5, 2019, at 9:25 PM, Sean Mathews ***@***.***>
wrote:
>
>
> Tell me some more. Ademco panel or DSC.
> Smartthings or ?
> How updated is your AD2pi appliance software.
>
> Best
> Sean M.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82?email_source=notifications&email_token=AAPSWFFIWVYBJA6AV4AJ6ODQSI4MPA5CNFSM4JJOM3Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDFE6MI#issuecomment-550129457>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPSWFGE4IL4K4V7SOKR5E3QSI4MPANCNFSM4JJOM3ZQ>
.
|
|
@f34rdotcom now I'm the one taking forever to respond... Port 10000 is working. It's not that I miss ALL events, just SOME. Like I'll get an event saying a door was opened, but never closed... in Hubitat it screws up my rules for like "turn off heat if doors are left open" I'm not sure what you were asking for from the advanced menu. Let me know what you need and I'm happy to help. I'll upgrade whatever I need to I just don't know what. I have the latest webapp and library... Since the webapp seems wrong I doubt it's the Hubitat App/Drivers, but I just updated them to the latest dev version just to be safe. |
|
I am still having many missed events. Is there anyway to track this down? |
|
I need to connect in and play 20 questions with everything.
Busy weeks but I can find the time.
I hope to have time Saturday as well.
Best
Sean M
…On Thu, Nov 21, 2019, 5:27 AM dcmeglio ***@***.***> wrote:
I am still having many missed events. Is there anyway to track this down?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82?email_source=notifications&email_token=AAPSWFCYROBOTDR4GWVC3M3QU2EDFA5CNFSM4JJOM3Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE2G24I#issuecomment-557084017>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPSWFDNYMM77CUWV4I75O3QU2EDFANCNFSM4JJOM3ZQ>
.
|
|
I'm around all day Saturday. Let me know a time that works (I'm EST) and we can connect. |
|
@f34rdotcom any chance we can set a time? I'm still experiencing many (random) missed events. |
|
Sorry I have been crazy busy the past few days with an unexpected family
visit. Will tomorrow work? I have a few hours in the morning available. How
about 11AM PST.
I can also do something tonight at say 4PM PST.
Should be 40 minutes at most to go from stem to stern. Likely 20.
503 443 2000 x703.
|
|
11AM PST tomorrow works. Talk to you then. Thank you for your help.
…On Sat, Nov 23, 2019 at 5:37 PM Sean Mathews ***@***.***> wrote:
Sorry I have been crazy busy the past few days with an unexpected family
visit. Will tomorrow work? I have a few hours in the morning available. How
about 11AM PST.
I can also do something tonight at say 4PM PST.
Should be 40 minutes at most to go from stem to stern. Likely 20.
503 443 2000 x703.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#82?email_source=notifications&email_token=AFHQVAWQ534435KZ3QYP27LQVGWCHA5CNFSM4JJOM3Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE77HFQ#issuecomment-557839254>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFHQVAUJAGMSFF2I76Z2L33QVGWCHANCNFSM4JJOM3ZQ>
.
|
|
@f34rdotcom still no luck. I upgraded to buster, still missing events. I opened my garage door and closed it at 17:23 and neither event was recognized. However, opening/closing my inside door worked just about 30 seconds later. Is there somewhere I can email you the logs? I grabbed them at the time this occurred. |
|
Yes please. [email protected]
…On Sun, Nov 24, 2019, 5:36 PM dcmeglio ***@***.***> wrote:
@f34rdotcom <https://github.com/f34rdotcom> still no luck. I upgraded to
buster, still missing events. I opened my garage door and closed it at
17:23 and neither event was recognized. However, opening/closing my inside
door worked just about 30 seconds later. Is there somewhere I can email you
the logs? I grabbed them at the time this occurred.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82?email_source=notifications&email_token=AAPSWFBYNBAJJKFX6UIHPL3QVMTZXA5CNFSM4JJOM3Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFA3LQI#issuecomment-557954497>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPSWFALTVSBEX3EEBS4OB3QVMTZXANCNFSM4JJOM3ZQ>
.
|
|
sent |
|
I’m still having many missed events. Is there anyway to get ser2sock to log raw messages with timestamps? Then I can see if the messages are actually arriving or not. Might help focus the efforts.
Dominick Meglio
Sent from my iPhone
… On Nov 24, 2019, at 10:16 PM, Sean Mathews ***@***.***> wrote:
Yes please. ***@***.***
On Sun, Nov 24, 2019, 5:36 PM dcmeglio ***@***.***> wrote:
> @f34rdotcom <https://github.com/f34rdotcom> still no luck. I upgraded to
> buster, still missing events. I opened my garage door and closed it at
> 17:23 and neither event was recognized. However, opening/closing my inside
> door worked just about 30 seconds later. Is there somewhere I can email you
> the logs? I grabbed them at the time this occurred.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#82?email_source=notifications&email_token=AAPSWFBYNBAJJKFX6UIHPL3QVMTZXA5CNFSM4JJOM3Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFA3LQI#issuecomment-557954497>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAPSWFALTVSBEX3EEBS4OB3QVMTZXANCNFSM4JJOM3ZQ>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
Anything? I'm having a lot of issues. I've had the live logging running all day so far and it seems like the messages are there, but not triggering events. I'm going to do more debugging and logging but I'm thinking there is something up with the zone tracker. |
|
I agree. It is probably zone tracker. Trying to find a good way to
confirm. Ser2sock has logging but it is very verbose. I will review logging
for zone tracker maybe a simple log entry can be enabled to make it more
user friendly to debug. For ser2sock you can check args for debug level.
Set in init.d command line. I think level 2 will do?
…On Wed, Nov 27, 2019, 8:05 AM dcmeglio ***@***.***> wrote:
Anything? I'm having a lot of issues. I've had the live logging running
all day so far and it seems like the messages are there, but not triggering
events. I'm going to do more debugging and logging but I'm thinking there
is something up with the zone tracker.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82?email_source=notifications&email_token=AAPSWFFIMLONWIWZZD3YYZ3QV2LFZA5CNFSM4JJOM3Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFJ7LSA#issuecomment-559150536>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPSWFFJ73JTSVVJBS5N6VLQV2LFZANCNFSM4JJOM3ZQ>
.
|
|
Is there an easy way to see the serial # for zones? I’m thinking of converting to rfx for the wireless zones anyway.
Dominick Meglio
Sent from my iPhone
… On Nov 27, 2019, at 12:06 PM, Sean Mathews ***@***.***> wrote:
I agree. It is probably zone tracker. Trying to find a good way to
confirm. Ser2sock has logging but it is very verbose. I will review logging
for zone tracker maybe a simple log entry can be enabled to make it more
user friendly to debug. For ser2sock you can check args for debug level.
Set in init.d command line. I think level 2 will do?
On Wed, Nov 27, 2019, 8:05 AM dcmeglio ***@***.***> wrote:
> Anything? I'm having a lot of issues. I've had the live logging running
> all day so far and it seems like the messages are there, but not triggering
> events. I'm going to do more debugging and logging but I'm thinking there
> is something up with the zone tracker.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#82?email_source=notifications&email_token=AAPSWFFIMLONWIWZZD3YYZ3QV2LFZA5CNFSM4JJOM3Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFJ7LSA#issuecomment-559150536>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAPSWFFJ73JTSVVJBS5N6VLQV2LFZANCNFSM4JJOM3ZQ>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
Ya the log on hubitat will show them realtime when you trip them.
Also the live log on the webapp.
…On Wed, Nov 27, 2019, 2:02 PM dcmeglio ***@***.***> wrote:
Is there an easy way to see the serial # for zones? I’m thinking of
converting to rfx for the wireless zones anyway.
Dominick Meglio
Sent from my iPhone
> On Nov 27, 2019, at 12:06 PM, Sean Mathews ***@***.***>
wrote:
>
> I agree. It is probably zone tracker. Trying to find a good way to
> confirm. Ser2sock has logging but it is very verbose. I will review
logging
> for zone tracker maybe a simple log entry can be enabled to make it more
> user friendly to debug. For ser2sock you can check args for debug level.
> Set in init.d command line. I think level 2 will do?
>
> On Wed, Nov 27, 2019, 8:05 AM dcmeglio ***@***.***> wrote:
>
> > Anything? I'm having a lot of issues. I've had the live logging running
> > all day so far and it seems like the messages are there, but not
triggering
> > events. I'm going to do more debugging and logging but I'm thinking
there
> > is something up with the zone tracker.
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub
> > <
#82?email_source=notifications&email_token=AAPSWFFIMLONWIWZZD3YYZ3QV2LFZA5CNFSM4JJOM3Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFJ7LSA#issuecomment-559150536
>,
> > or unsubscribe
> > <
https://github.com/notifications/unsubscribe-auth/AAPSWFFJ73JTSVVJBS5N6VLQV2LFZANCNFSM4JJOM3ZQ
>
> > .
> >
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82?email_source=notifications&email_token=AAPSWFDOELLWKVMAQDSWXH3QV3VAFA5CNFSM4JJOM3Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFK3OWQ#issuecomment-559265626>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPSWFCIL2GLPZ3KI2NXXW3QV3VAFANCNFSM4JJOM3ZQ>
.
|
|
Looking more closely I notice that the live log sometimes misses messages. For example
When it was cycling through all the faults it didn’t see a message that my garage door was open so it said it was closed. On the next loop it saw it was actually open. Do you think my ad2pi could be going bad?
Dominick Meglio
Sent from my iPhone
… On Nov 27, 2019, at 7:23 PM, Sean Mathews ***@***.***> wrote:
Ya the log on hubitat will show them realtime when you trip them.
Also the live log on the webapp.
On Wed, Nov 27, 2019, 2:02 PM dcmeglio ***@***.***> wrote:
> Is there an easy way to see the serial # for zones? I’m thinking of
> converting to rfx for the wireless zones anyway.
>
> Dominick Meglio
> Sent from my iPhone
>
> > On Nov 27, 2019, at 12:06 PM, Sean Mathews ***@***.***>
> wrote:
> >
> > I agree. It is probably zone tracker. Trying to find a good way to
> > confirm. Ser2sock has logging but it is very verbose. I will review
> logging
> > for zone tracker maybe a simple log entry can be enabled to make it more
> > user friendly to debug. For ser2sock you can check args for debug level.
> > Set in init.d command line. I think level 2 will do?
> >
> > On Wed, Nov 27, 2019, 8:05 AM dcmeglio ***@***.***> wrote:
> >
> > > Anything? I'm having a lot of issues. I've had the live logging running
> > > all day so far and it seems like the messages are there, but not
> triggering
> > > events. I'm going to do more debugging and logging but I'm thinking
> there
> > > is something up with the zone tracker.
> > >
> > > —
> > > You are receiving this because you were mentioned.
> > > Reply to this email directly, view it on GitHub
> > > <
> #82?email_source=notifications&email_token=AAPSWFFIMLONWIWZZD3YYZ3QV2LFZA5CNFSM4JJOM3Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFJ7LSA#issuecomment-559150536
> >,
> > > or unsubscribe
> > > <
> https://github.com/notifications/unsubscribe-auth/AAPSWFFJ73JTSVVJBS5N6VLQV2LFZANCNFSM4JJOM3ZQ
> >
> > > .
> > >
> > —
> > You are receiving this because you authored the thread.
> > Reply to this email directly, view it on GitHub, or unsubscribe.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#82?email_source=notifications&email_token=AAPSWFDOELLWKVMAQDSWXH3QV3VAFA5CNFSM4JJOM3Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFK3OWQ#issuecomment-559265626>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAPSWFCIL2GLPZ3KI2NXXW3QV3VAFANCNFSM4JJOM3ZQ>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
Possibly but very rarely does the board fail other than catastrophically
such as ESD damage.
Also power supply issues can cause random problems but they usually show as
corrupt data from the serial port.
Another possibility is noise on the keypad bus from a bad device. With
debug mode @48 on beta firmware this is usually easy to see in a log from
ser2sock.
Did you send me logs of the raw panel messages during when the tracker
failed? It should show the FAULT messages for this zone and then it is
restored the FAULT will disappear from the fault list.
Does hubitat send * to the panel to force a zone fauly list? If so we need
to turn it off as the pi webapp is also doing this. That would cause a
conflict and zone tracker would be effected.
…On Sat, Nov 30, 2019, 8:17 PM dcmeglio ***@***.***> wrote:
Looking more closely I notice that the live log sometimes misses messages.
For example
When it was cycling through all the faults it didn’t see a message that my
garage door was open so it said it was closed. On the next loop it saw it
was actually open. Do you think my ad2pi could be going bad?
Dominick Meglio
Sent from my iPhone
> On Nov 27, 2019, at 7:23 PM, Sean Mathews ***@***.***>
wrote:
>
> Ya the log on hubitat will show them realtime when you trip them.
>
> Also the live log on the webapp.
>
> On Wed, Nov 27, 2019, 2:02 PM dcmeglio ***@***.***> wrote:
>
> > Is there an easy way to see the serial # for zones? I’m thinking of
> > converting to rfx for the wireless zones anyway.
> >
> > Dominick Meglio
> > Sent from my iPhone
> >
> > > On Nov 27, 2019, at 12:06 PM, Sean Mathews ***@***.***
>
> > wrote:
> > >
> > > I agree. It is probably zone tracker. Trying to find a good way to
> > > confirm. Ser2sock has logging but it is very verbose. I will review
> > logging
> > > for zone tracker maybe a simple log entry can be enabled to make it
more
> > > user friendly to debug. For ser2sock you can check args for debug
level.
> > > Set in init.d command line. I think level 2 will do?
> > >
> > > On Wed, Nov 27, 2019, 8:05 AM dcmeglio ***@***.***>
wrote:
> > >
> > > > Anything? I'm having a lot of issues. I've had the live logging
running
> > > > all day so far and it seems like the messages are there, but not
> > triggering
> > > > events. I'm going to do more debugging and logging but I'm thinking
> > there
> > > > is something up with the zone tracker.
> > > >
> > > > —
> > > > You are receiving this because you were mentioned.
> > > > Reply to this email directly, view it on GitHub
> > > > <
> >
#82?email_source=notifications&email_token=AAPSWFFIMLONWIWZZD3YYZ3QV2LFZA5CNFSM4JJOM3Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFJ7LSA#issuecomment-559150536
> > >,
> > > > or unsubscribe
> > > > <
> >
https://github.com/notifications/unsubscribe-auth/AAPSWFFJ73JTSVVJBS5N6VLQV2LFZANCNFSM4JJOM3ZQ
> > >
> > > > .
> > > >
> > > —
> > > You are receiving this because you authored the thread.
> > > Reply to this email directly, view it on GitHub, or unsubscribe.
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub
> > <
#82?email_source=notifications&email_token=AAPSWFDOELLWKVMAQDSWXH3QV3VAFA5CNFSM4JJOM3Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFK3OWQ#issuecomment-559265626
>,
> > or unsubscribe
> > <
https://github.com/notifications/unsubscribe-auth/AAPSWFCIL2GLPZ3KI2NXXW3QV3VAFANCNFSM4JJOM3ZQ
>
> > .
> >
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82?email_source=notifications&email_token=AAPSWFBWG7RITR3G3IASVJ3QWM3EHA5CNFSM4JJOM3Z2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFQ3PGI#issuecomment-560052121>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPSWFBWIQFY4Y3XRW3VLW3QWM3EHANCNFSM4JJOM3ZQ>
.
|
how do I enable debug mode 48 and where do I see these logs? Also the only wired devices I have are an overhead door sensor and one regular door sensor and 2 keypads. I'm moving most of my devices to RFX but I'm having issues with that on a few that I'm troubleshooting.
I haven't gotten a great capture in the logs yet. I do have one example here though that seems to be a missed event. Notice that it goes 44, 02, 41 but then 44, 41 then back to 44, 02, 41... 02 was open this whole time. It caused me to receive a notice that it closed and then reopened even though it never closed https://imgur.com/a/cAXmL7u
Not that I'm aware of. I'm using your smartthings integration so you'd know better than me. I did a quick search through the code and didn't find anything. |
|
@f34rdotcom i sent logs yesterday that show the issue. Any thoughts? All the wireless zones that I switched to rfx work flawlessly. It is only the wired zones that are an issue. |
|
@f34rdotcom were the logs at all helpful? In an attempt to resolve the issue I just upgraded my rpi to a 4 so brand new hardware now too. |
|
@f34rdotcom should I assume that there is no fix to this issue being investigated? All of my RFX sensors work perfectly. The wired ones do not. It's pretty clear to me it's the zone tracking. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@f34rdotcom I don't know if there is something I can do to track this down but I'm noticing missed events. At around 7am I see I opened and closed my garage door when I went to work. Perfect. At 7:30 my wife left for work. There is no log of the open/close for the garage door. I do see that she successfully armed the alarm before leaving though. Is there anything I can check to see why the event might have been missed? I've noticed this has happened quite a bit over the last few days.
The text was updated successfully, but these errors were encountered: