v3.0.0 Beta Testers

[mrjackyliang]

Creating a thread here for all beta testing issues.

[mrjackyliang]

Updated to v3.0.0-beta.7

[mrjackyliang]

Following the issues here:

Need to test Arm Instant Mode - #36 ADT Pulse Gateway Battery Support - #87

[mrjackyliang]

Updated to v3.0.0-beta.8 to partially support keypad

[sapireli]

FYI in beta 8. The issue with the sensors not being discovered is definitely persistent. It always happens, sometimes with more sensors and sometimes with less but there are always a random 5 or 6 that aren’t “discovered”.

[sapireli]

Also, quick question on the panic button support - does this mean you can trigger a panic or just register when the button gets pressed?

[mrjackyliang]

FYI in beta 8. The issue with the sensors not being discovered is definitely persistent. It always happens, sometimes with more sensors and sometimes with less but there are always a random 5 or 6 that aren’t “discovered”.

@sapireli I'm not surprised, this is one of the things that in the past caused random sensors to be removed at times.

[mrjackyliang]

Also, quick question on the panic button support - does this mean you can trigger a panic or just register when the button gets pressed?

@sapireli I think it's just a register as a press for now. I don't think HomeKit even has that kind of accessory to begin with.

BUT, if you can trigger it in the portal, I can definitely try to figure some way to add it in.

[sapireli]

BUT, if you can trigger it in the portal, I can definitely try to figure some way to add it in.

AFAIK there is no way to do it in the portal, but that be awesome, because in turn that would mean you can trigger it remotely alarm.com style.

[mrjackyliang]

BUT, if you can trigger it in the portal, I can definitely try to figure some way to add it in.

AFAIK there is no way to do it in the portal, but that be awesome, because in turn that would mean you can trigger it remotely alarm.com style.

@sapireli Definitely! Curious, can you trigger it in the official app? Maybe in the future I might not need to go through the portal if I am able to reverse engineer the app's communication.

[sapireli]

can you trigger it in the official app?

No, unfortunately.

[sapireli]

is the axios timeout something we can change? i got a few of these errors today...

[12/19/2023, 2:58:09 PM] [ADT Pulse] Keeping alive attempt has failed. Trying again later. { action: 'PERFORM_KEEP_ALIVE', success: false, info: { error: { message: 'timeout of 15000ms exceeded', name: 'AxiosError', description: undefined, number: undefined, fileName: undefined, lineNumber: undefined, columnNumber: undefined, stack: 'AxiosError: timeout of 15000ms exceeded\n' +

[mrjackyliang]

can you trigger it in the official app?

No, unfortunately.

@sapireli Ah, darnit.

[mrjackyliang]

is the axios timeout something we can change? i got a few of these errors today...

[12/19/2023, 2:58:09 PM] [ADT Pulse] Keeping alive attempt has failed. Trying again later. { action: 'PERFORM_KEEP_ALIVE', success: false, info: { error: { message: 'timeout of 15000ms exceeded', name: 'AxiosError', description: undefined, number: undefined, fileName: undefined, lineNumber: undefined, columnNumber: undefined, stack: 'AxiosError: timeout of 15000ms exceeded\n' +

@sapireli I can set the logs to debug mode if it happens often. I think I've seen a few of those, will work on that.

[mrjackyliang]

Updated to 3.0.0-beta.9 for some fixes related to HOOBS.

[sapireli]

FYI panic buttons aren't working when added to config, and also for some reason setting a custom name on a sensor makes that sensor unavailable

12/20/2023, 3:36:05 AM] [ADT Pulse] Failed to initialize Panic (id: adt-device-42, uuid: 1..) accessory services ... [12/20/2023, 3:36:05 AM] [ADT Pulse] Failed to initialize Panic (14) (id: adt-device-66, uuid: 1..) accessory services ... [12/20/2023, 3:36:05 AM] [ADT Pulse] Failed to initialize Panic (15) (id: adt-device-47, uuid: 1..

Updated to 3.0.0-beta.9 for some fixes related to HOOBS.

[mrjackyliang]

FYI panic buttons aren't working when added to config, and also for some reason setting a custom name on a sensor makes that sensor unavailable

12/20/2023, 3:36:05 AM] [ADT Pulse] Failed to initialize Panic (id: adt-device-42, uuid: 1..) accessory services ...

[12/20/2023, 3:36:05 AM] [ADT Pulse] Failed to initialize Panic (14) (id: adt-device-66, uuid: 1..) accessory services ...

[12/20/2023, 3:36:05 AM] [ADT Pulse] Failed to initialize Panic (15) (id: adt-device-47, uuid: 1..

Updated to 3.0.0-beta.9 for some fixes related to HOOBS.

@sapireli Yes, I haven't worked on implementing the code for that yet. The error is expected for now.

However, in the meantime, are you able to help trigger the panic buttons (in test mode via My ADT), so I can see the statuses when it rings? Thanks!

I believe I need just those before I can fully implement them, or probably try it once, and see if the scripts capture the info fast enough and I can see it.

[mrjackyliang]

Updated to v3.0.0-beta.10

[tr1um9h]

My sensors just show as no response in HomeKit I'm on beta10

[mrjackyliang]

My sensors just show as no response in HomeKit I'm on beta10

@tr1um9h Can I see the Homebridge logs? Sometimes it just takes a bit to sync up, and then you won't see these no responses anymore, but everyone's internet connection is different.

[tr1um9h]

My sensors just show as no response in HomeKit I'm on beta10

@tr1um9h Can I see the Homebridge logs? Sometimes it just takes a bit to sync up, and then you won't see these no responses anymore, but everyone's internet connection is different.

So I'm not seeing anything the logs I also feel the beta has been crashing my network lately I've had to restart my router daily and it started after using the beta

[mrjackyliang]

My sensors just show as no response in HomeKit I'm on beta10

@tr1um9h Can I see the Homebridge logs? Sometimes it just takes a bit to sync up, and then you won't see these no responses anymore, but everyone's internet connection is different.

So I'm not seeing anything the logs I also feel the beta has been crashing my network lately I've had to restart my router daily and it started after using the beta

@tr1um9h Where are you running Homebridge? Also tell me the versions printed out in the logs, specifically the OpenSSL version and your hardware config

[tr1um9h]

My sensors just show as no response in HomeKit I'm on beta10

@tr1um9h Can I see the Homebridge logs? Sometimes it just takes a bit to sync up, and then you won't see these no responses anymore, but everyone's internet connection is different.

So I'm not seeing anything the logs I also feel the beta has been crashing my network lately I've had to restart my router daily and it started after using the beta

@tr1um9h Where are you running Homebridge? Also tell me the versions printed out in the logs, specifically the OpenSSL version and your hardware config

I am running it on a raspberry pi OS: Linux 5.10.103-v7+ arm Node.js v20.10.0 /usr/local/bin/node Homebridge v1.7.0 OpenSSL 1.1.1n 15 Mar 2022

[mrjackyliang]

My sensors just show as no response in HomeKit I'm on beta10

@tr1um9h Can I see the Homebridge logs? Sometimes it just takes a bit to sync up, and then you won't see these no responses anymore, but everyone's internet connection is different.

So I'm not seeing anything the logs I also feel the beta has been crashing my network lately I've had to restart my router daily and it started after using the beta

@tr1um9h Where are you running Homebridge? Also tell me the versions printed out in the logs, specifically the OpenSSL version and your hardware config

I am running it on a raspberry pi

OS: Linux 5.10.103-v7+ arm

Node.js v20.10.0 /usr/local/bin/node

Homebridge v1.7.0

OpenSSL 1.1.1n 15 Mar 2022

@tr1um9h Hmm, if this is related to your router, can you try setting the synchronization speed to 0.25x? Maybe the plugin is generating too much traffic for older devices to process.

[tr1um9h]

My sensors just show as no response in HomeKit I'm on beta10

@tr1um9h Can I see the Homebridge logs? Sometimes it just takes a bit to sync up, and then you won't see these no responses anymore, but everyone's internet connection is different.

So I'm not seeing anything the logs I also feel the beta has been crashing my network lately I've had to restart my router daily and it started after using the beta

@tr1um9h Where are you running Homebridge? Also tell me the versions printed out in the logs, specifically the OpenSSL version and your hardware config

I am running it on a raspberry pi OS: Linux 5.10.103-v7+ arm Node.js v20.10.0 /usr/local/bin/node Homebridge v1.7.0 OpenSSL 1.1.1n 15 Mar 2022

@tr1um9h Hmm, if this is related to your router, can you try setting the synchronization speed to 0.25x? Maybe the plugin is generating too much traffic for older devices to process.

I'm using a linksys velop mesh router do you think it can cause issues?

[mrjackyliang]

My sensors just show as no response in HomeKit I'm on beta10

@tr1um9h Can I see the Homebridge logs? Sometimes it just takes a bit to sync up, and then you won't see these no responses anymore, but everyone's internet connection is different.

So I'm not seeing anything the logs I also feel the beta has been crashing my network lately I've had to restart my router daily and it started after using the beta

@tr1um9h Where are you running Homebridge? Also tell me the versions printed out in the logs, specifically the OpenSSL version and your hardware config

I am running it on a raspberry pi

OS: Linux 5.10.103-v7+ arm

Node.js v20.10.0 /usr/local/bin/node

Homebridge v1.7.0

OpenSSL 1.1.1n 15 Mar 2022

@tr1um9h Hmm, if this is related to your router, can you try setting the synchronization speed to 0.25x? Maybe the plugin is generating too much traffic for older devices to process.

I'm using a linksys velop mesh router do you think it can cause issues? and how would I set the sync speed?

@tr1um9h I don't think it has to do with routers specifically, it has to do with the processing power in consumer routers overall.

I have a pfSense/UniFi setup with an Intel Quad Core Celeron, and that's like corporate office power at home, not something I would recommend to everyone.

[mrjackyliang]

For the synchronization speed, that is changed in the General tab inside the config UI, or if you use config.json, it would be setting speed to 0.25

[tr1um9h]

My sensors just show as no response in HomeKit I'm on beta10

@tr1um9h Can I see the Homebridge logs? Sometimes it just takes a bit to sync up, and then you won't see these no responses anymore, but everyone's internet connection is different.

So I'm not seeing anything the logs I also feel the beta has been crashing my network lately I've had to restart my router daily and it started after using the beta

@tr1um9h Where are you running Homebridge? Also tell me the versions printed out in the logs, specifically the OpenSSL version and your hardware config

I am running it on a raspberry pi

OS: Linux 5.10.103-v7+ arm

Node.js v20.10.0 /usr/local/bin/node

Homebridge v1.7.0

OpenSSL 1.1.1n 15 Mar 2022

@tr1um9h Hmm, if this is related to your router, can you try setting the synchronization speed to 0.25x? Maybe the plugin is generating too much traffic for older devices to process.

I'm using a linksys velop mesh router do you think it can cause issues? and how would I set the sync speed?

@tr1um9h I don't think it has to do with routers specifically, it has to do with the processing power in consumer routers overall.

I have a pfSense/UniFi setup with an Intel Quad Core Celeron, and that's like corporate office power at home, not something I would recommend to everyone.

So I did that I'm still seeing no response from sensors, I know they are working because it shows in my history in the pulse portal

[mrjackyliang]

My sensors just show as no response in HomeKit I'm on beta10

@tr1um9h Can I see the Homebridge logs? Sometimes it just takes a bit to sync up, and then you won't see these no responses anymore, but everyone's internet connection is different.

So I'm not seeing anything the logs I also feel the beta has been crashing my network lately I've had to restart my router daily and it started after using the beta

@tr1um9h Where are you running Homebridge? Also tell me the versions printed out in the logs, specifically the OpenSSL version and your hardware config

I am running it on a raspberry pi

OS: Linux 5.10.103-v7+ arm

Node.js v20.10.0 /usr/local/bin/node

Homebridge v1.7.0

OpenSSL 1.1.1n 15 Mar 2022

@tr1um9h Hmm, if this is related to your router, can you try setting the synchronization speed to 0.25x? Maybe the plugin is generating too much traffic for older devices to process.

I'm using a linksys velop mesh router do you think it can cause issues? and how would I set the sync speed?

@tr1um9h I don't think it has to do with routers specifically, it has to do with the processing power in consumer routers overall.

I have a pfSense/UniFi setup with an Intel Quad Core Celeron, and that's like corporate office power at home, not something I would recommend to everyone.

So I did that I'm still seeing no response from sensors, I know they are working because it shows in my history in the pulse portal

@tr1um9h Give it a minute, let it sync up. I agree it's slow, gotta work on that.

[tr1um9h]

My sensors just show as no response in HomeKit I'm on beta10

@tr1um9h Can I see the Homebridge logs? Sometimes it just takes a bit to sync up, and then you won't see these no responses anymore, but everyone's internet connection is different.

So I'm not seeing anything the logs I also feel the beta has been crashing my network lately I've had to restart my router daily and it started after using the beta

@tr1um9h Where are you running Homebridge? Also tell me the versions printed out in the logs, specifically the OpenSSL version and your hardware config

I am running it on a raspberry pi

OS: Linux 5.10.103-v7+ arm

Node.js v20.10.0 /usr/local/bin/node

Homebridge v1.7.0

OpenSSL 1.1.1n 15 Mar 2022

@tr1um9h Hmm, if this is related to your router, can you try setting the synchronization speed to 0.25x? Maybe the plugin is generating too much traffic for older devices to process.

I'm using a linksys velop mesh router do you think it can cause issues? and how would I set the sync speed?

@tr1um9h I don't think it has to do with routers specifically, it has to do with the processing power in consumer routers overall.

I have a pfSense/UniFi setup with an Intel Quad Core Celeron, and that's like corporate office power at home, not something I would recommend to everyone.

So I did that I'm still seeing no response from sensors, I know they are working because it shows in my history in the pulse portal

@tr1um9h Give it a minute, let it sync up. I agree it's slow, gotta work on that.

Still showing no response

[mrjackyliang]

My sensors just show as no response in HomeKit I'm on beta10

@tr1um9h Can I see the Homebridge logs? Sometimes it just takes a bit to sync up, and then you won't see these no responses anymore, but everyone's internet connection is different.

So I'm not seeing anything the logs I also feel the beta has been crashing my network lately I've had to restart my router daily and it started after using the beta

@tr1um9h Where are you running Homebridge? Also tell me the versions printed out in the logs, specifically the OpenSSL version and your hardware config

I am running it on a raspberry pi

OS: Linux 5.10.103-v7+ arm

Node.js v20.10.0 /usr/local/bin/node

Homebridge v1.7.0

OpenSSL 1.1.1n 15 Mar 2022

@tr1um9h Hmm, if this is related to your router, can you try setting the synchronization speed to 0.25x? Maybe the plugin is generating too much traffic for older devices to process.

I'm using a linksys velop mesh router do you think it can cause issues? and how would I set the sync speed?

@tr1um9h I don't think it has to do with routers specifically, it has to do with the processing power in consumer routers overall.

I have a pfSense/UniFi setup with an Intel Quad Core Celeron, and that's like corporate office power at home, not something I would recommend to everyone.

So I did that I'm still seeing no response from sensors, I know they are working because it shows in my history in the pulse portal

@tr1um9h Give it a minute, let it sync up. I agree it's slow, gotta work on that.

Still showing no response

@tr1um9h Wait. Is your security panel showing statuses? My sensors aren't showing at all.

[mrjackyliang]

So for everyone who is beta testing the plugin, if you receive no response, please do ignore them for now.

Use the ADT system as you normally would, since I am collecting alarm statuses and will be able to better document this.

Please be patient (I also need a break, stressed out on this and a lot of other things lately), will work on it! Thanks☺️

[tr1um9h]

My sensors just show as no response in HomeKit I'm on beta10

@tr1um9h Can I see the Homebridge logs? Sometimes it just takes a bit to sync up, and then you won't see these no responses anymore, but everyone's internet connection is different.

So I'm not seeing anything the logs I also feel the beta has been crashing my network lately I've had to restart my router daily and it started after using the beta

@tr1um9h Where are you running Homebridge? Also tell me the versions printed out in the logs, specifically the OpenSSL version and your hardware config

I am running it on a raspberry pi

OS: Linux 5.10.103-v7+ arm

Node.js v20.10.0 /usr/local/bin/node

Homebridge v1.7.0

OpenSSL 1.1.1n 15 Mar 2022

@tr1um9h Hmm, if this is related to your router, can you try setting the synchronization speed to 0.25x? Maybe the plugin is generating too much traffic for older devices to process.

I'm using a linksys velop mesh router do you think it can cause issues? and how would I set the sync speed?

@tr1um9h I don't think it has to do with routers specifically, it has to do with the processing power in consumer routers overall.

I have a pfSense/UniFi setup with an Intel Quad Core Celeron, and that's like corporate office power at home, not something I would recommend to everyone.

So I did that I'm still seeing no response from sensors, I know they are working because it shows in my history in the pulse portal

@tr1um9h Give it a minute, let it sync up. I agree it's slow, gotta work on that.

Still showing no response

@tr1um9h Wait. Is your security panel showing statuses? My sensors aren't showing at all.

I am able to set the status of the panel through HomeKit but my sensors show as no response

[mrjackyliang]

My sensors just show as no response in HomeKit I'm on beta10

@tr1um9h Can I see the Homebridge logs? Sometimes it just takes a bit to sync up, and then you won't see these no responses anymore, but everyone's internet connection is different.

So I'm not seeing anything the logs I also feel the beta has been crashing my network lately I've had to restart my router daily and it started after using the beta

@tr1um9h Where are you running Homebridge? Also tell me the versions printed out in the logs, specifically the OpenSSL version and your hardware config

I am running it on a raspberry pi

OS: Linux 5.10.103-v7+ arm

Node.js v20.10.0 /usr/local/bin/node

Homebridge v1.7.0

OpenSSL 1.1.1n 15 Mar 2022

@tr1um9h Hmm, if this is related to your router, can you try setting the synchronization speed to 0.25x? Maybe the plugin is generating too much traffic for older devices to process.

I'm using a linksys velop mesh router do you think it can cause issues? and how would I set the sync speed?

@tr1um9h I don't think it has to do with routers specifically, it has to do with the processing power in consumer routers overall.

I have a pfSense/UniFi setup with an Intel Quad Core Celeron, and that's like corporate office power at home, not something I would recommend to everyone.

So I did that I'm still seeing no response from sensors, I know they are working because it shows in my history in the pulse portal

@tr1um9h Give it a minute, let it sync up. I agree it's slow, gotta work on that.

Still showing no response

@tr1um9h Wait. Is your security panel showing statuses? My sensors aren't showing at all.

I am able to set the status of the panel through HomeKit but my sensors show as no response

@tr1um9h Okay, let's work with that for now. We can first focus on the security panel. I am aware that some arms and disarms will take longer than needed. Still need to figure out how to properly display it in the Home app.

[Danimal4326]

Quick question, what is the purpose of adding the "ADT Pulse Gateway" accessory when it show that it's not supported by the Home App.

[mrjackyliang]

Quick question, what is the purpose of adding the "ADT Pulse Gateway" accessory when it show that it's not supported by the Home App.

@Danimal4326 It is a design decision I made when building the plugin. The Home app does not support it, but from the HAP protocol point-of-view, it is a valid accessory and you can see more information using third-party apps.

As for the accessory that says not supported, you can hide it away from the Home view if you wish.

[Danimal4326]

Thanks for the info @mrjackyliang

[jastorino82]

I just got up and running on the new plugin, beta 11. Few things

• I get this in my log on startup. Not sure if it is just cosmetic: "The plugin "homebridge-adt-pulse" requires Node.js version of 18 which does not satisfy the current Node.js version of v20.9.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF"

• I used to run the plugin as a child bridge. When I set up the new plugin as a child bridge and scan the QR code to add the child bridge to homekit, it doesn't work. Is child bridge supported? Edit After rebooting iPhone and trying again, I was able to add the child bridge

• My Security Panel shows in HomeKit and is working for arm/disarm, but all my sensors are mostly showing "No Response". Some come and go, but I have yet to see a state where they are all normal. I'm running the plugin as a child bridge on HomeBridge running on a Raspberry Pi 2b hard wired into Ethernet. If it helps, my HomeKit setup is running on the new architecture, and my hub is an Apple TV 4k Gen3 hard wired.

• If I run a scene that arms the panel, but the panel is already armed, it disarms it and then arms it again.

[mrjackyliang]

I just got up and running on the new plugin, beta 11. Few things

• I get this in my log on startup. Not sure if it is just cosmetic: "The plugin "homebridge-adt-pulse" requires Node.js version of 18 which does not satisfy the current Node.js version of v20.9.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF"
• I used to run the plugin as a child bridge. When I set up the new plugin as a child bridge and scan the QR code to add the child bridge to homekit, it doesn't work. Is child bridge supported? Edit After rebooting iPhone and trying again, I was able to add the child bridge
• My Security Panel shows in HomeKit and is working for arm/disarm, but all my sensors are mostly showing "No Response". Some come and go, but I have yet to see a state where they are all normal. I'm running the plugin as a child bridge on HomeBridge running on a Raspberry Pi 2b hard wired into Ethernet. If it helps, my HomeKit setup is running on the new architecture, and my hub is an Apple TV 4k Gen3 hard wired.
• If I run a scene that arms the panel, but the panel is already armed, it disarms it and then arms it again.

@jastorino82 I haven't tested this on Node v20 yet, but I assume it works because the compiled version is based on NodeNext. The sensors are being slowly fixed one by one, so that's going to be there, I first need to get the Security System working with Siri, so it doesn't say this device is taking long to respond. And then I'll nail the sensors one by one.

For the arming part, that is normal, unless your panel is in the same state at the time, then that is a bug. ADT doesn't allow me to simply change the state from, for example, away mode to night mode. Unless maybe things have changed.

But for now, you can start to add them into automation if you'd like, and on upgrades, some will slowly work itself out.

[mrjackyliang]

Also, I noticed this. My first time seeing the panel status with a This may take several minutes. That's extremely weird, I wonder what makes this happen.

[jastorino82]

Thanks @mrjackyliang - For the scene, I think it might be a bug. Here are the details

I have a scene setup for when I go to bed. Part of the scene is to set the security panel to arm stay. If the panel is already in arm stay / home state before I run the scene, it shouldn’t do anything with the panel, but it does - It disarms the panel, then tries to arm it again. I had that scene for a long time on the older versions and that didn’t happen for sure, 100%.

I just tested twice more - First time I ran the scene when the panel was already armed, same thing, it disarmed, then armed although the scene “failed”. Second time it just disarmed and the scene failed, and when I ran the scene again, it armed.

Not sure why exactly, but like you say, if the panel is already in the state the scene needs to get it to before the scene runs, the panel shouldn’t change state from armed —> disarmed —> armed, it should just stay armed.

[mrjackyliang]

Thanks @mrjackyliang - For the scene, I think it might be a bug. Here are the details

I have a scene setup for when I go to bed. Part of the scene is to set the security panel to arm stay. If the panel is already in arm stay / home state before I run the scene, it shouldn’t do anything with the panel, but it does - It disarms the panel, then tries to arm it again. I had that scene for a long time on the older versions and that didn’t happen for sure, 100%.

I just tested twice more - First time I ran the scene when the panel was already armed, same thing, it disarmed, then armed although the scene “failed”. Second time it just disarmed and the scene failed, and when I ran the scene again, it armed.

Not sure why exactly, but like you say, if the panel is already in the state the scene needs to get it to before the scene runs, the panel shouldn’t change state from armed —> disarmed —> armed, it should just stay armed.

@jastorino82 Can you go on your portal and test the scene again? Check if the status says "This may take several minutes". If you see that, then that's probably where the bug came from.

[Danimal4326]

Thanks @mrjackyliang - For the scene, I think it might be a bug. Here are the details I have a scene setup for when I go to bed. Part of the scene is to set the security panel to arm stay. If the panel is already in arm stay / home state before I run the scene, it shouldn’t do anything with the panel, but it does - It disarms the panel, then tries to arm it again. I had that scene for a long time on the older versions and that didn’t happen for sure, 100%. I just tested twice more - First time I ran the scene when the panel was already armed, same thing, it disarmed, then armed although the scene “failed”. Second time it just disarmed and the scene failed, and when I ran the scene again, it armed. Not sure why exactly, but like you say, if the panel is already in the state the scene needs to get it to before the scene runs, the panel shouldn’t change state from armed —> disarmed —> armed, it should just stay armed.

@jastorino82 Can you go on your portal and test the scene again? Check if the status says "This may take several minutes". If you see that, then that's probably where the bug came from.

I seem to have a similar issue. This morning when I went to run my "Good Morning" scene, which includes 2 things, Disarm the panel, and turn on my coffee maker. The coffee maker turned on. Home app showed the panel as disarmed, but it was still armed.

I disarmed via the Pulse app, then tried to manually disarm via the Homekit panel accessory. I heard the system disarm, then immediately re-arm.

P.S. Is there a way to turn on more verbose logging w/o making all of homebridge go into debug mode?

[mrjackyliang]

Thanks @mrjackyliang - For the scene, I think it might be a bug. Here are the details

I have a scene setup for when I go to bed. Part of the scene is to set the security panel to arm stay. If the panel is already in arm stay / home state before I run the scene, it shouldn’t do anything with the panel, but it does - It disarms the panel, then tries to arm it again. I had that scene for a long time on the older versions and that didn’t happen for sure, 100%.

I just tested twice more - First time I ran the scene when the panel was already armed, same thing, it disarmed, then armed although the scene “failed”. Second time it just disarmed and the scene failed, and when I ran the scene again, it armed.

Not sure why exactly, but like you say, if the panel is already in the state the scene needs to get it to before the scene runs, the panel shouldn’t change state from armed —> disarmed —> armed, it should just stay armed.

@jastorino82 Can you go on your portal and test the scene again? Check if the status says "This may take several minutes". If you see that, then that's probably where the bug came from.

I seem to have a similar issue. This morning when I went to run my "Good Morning" scene, which includes 2 things, Disarm the panel, and turn on my coffee maker. The coffee maker turned on. Home app showed the panel as disarmed, but it was still armed.

I disarmed via the Pulse app, then tried to manually disarm via the Homekit panel accessory. I heard the system disarm, then immediately re-arm.

P.S. Is there a way to turn on more verbose logging w/o making all of homebridge go into debug mode?

@Danimal4326 I took the option off because the older plugin debug options were pretty complex. Maybe I can add something simpler back.

[Danimal4326]

Looks like the panel state is not being reflected correctly in the Home app. If I arm on the physical panel, the app still shows off.. I haven't had chance to test all combinations, but something is not updating correctly.

[Danimal4326]

Ok did some quick testing. From a disarmed state, I armed stay in the home app. The panel went to armed, then disarmed, then armed again..

Also, looks like my sensors are not updating their state in the home app

[mrjackyliang]

I just checked my Pulse app, and yes it is happening to me too. So odd.

[bvelazquez1]

This plugin used to work for me a while ago but now it doesn't work. It hasn't been working for months but I figured I'd just ignore it until an update was available. Now that I've updated, it still doesn't work. If I log in to my ADT portal, I can change the status of my alarm, but i've lost the ability to control my alarm panel from the HomeKit app. I've tried updating the fingerprint and still I am unable to modify the status of my alarm. Should I just delete the plugin and reinstall it?

[sptv1]

In a very odd way, the current V2.2.0 app is actually working BETTER for me now without all the sensors. As long as it continues to allow me to arm/disarm the security panel and read its current status, that's all I really need exposed to HomeKit. I have this functionality built into multiple automations and it's critical!! If there's ever an alarm triggered, I get that notification on my devices via the ADT Pulse App. Having it in HomeKit is duplicative. At one point I had tried using the ADT sensors to trigger automations, but found them to be unreliable, so am now using Aqara sensors which work very well and are native to HomeKit.

[mrjackyliang]

This plugin used to work for me a while ago but now it doesn't work. It hasn't been working for months but I figured I'd just ignore it until an update was available. Now that I've updated, it still doesn't work. If I log in to my ADT portal, I can change the status of my alarm, but i've lost the ability to control my alarm panel from the HomeKit app. I've tried updating the fingerprint and still I am unable to modify the status of my alarm. Should I just delete the plugin and reinstall it?

@bvelazquez1 I'm still working on the new version, took a break for a few days cause I was burned out. But either, I'll continue working on it tonight or tomorrow.

[mrjackyliang]

In a very odd way, the current V2.2.0 app is actually working BETTER for me now without all the sensors. As long as it continues to allow me to arm/disarm the security panel and read its current status, that's all I really need exposed to HomeKit. I have this functionality built into multiple automations and it's critical!! If there's ever an alarm triggered, I get that notification on my devices via the ADT Pulse App. Having it in HomeKit is duplicative. At one point I had tried using the ADT sensors to trigger automations, but found them to be unreliable, so am now using Aqara sensors which work very well and are native to HomeKit.

@sptv1 The new version is supposed to improve the way how the plugin used to work because most users have issues with their automation resetting, including me. There was a setting that prevented it, but it was more of a workaround than a solution.

The new version allows the user to have more control in that particular manner, just so if it does reset (that the user accidentally reset it), at least you won't be wondering what Living Room Window 55 was.

For the security panel, that will be the next thing I'll fix on my list, and also I have detected a lot of different statuses that I never detected before in the older versions. So bear with me on this, thanks.