v3 Development - Calling All TypeScript Developers #98

mrjackyliang · 2023-04-02T17:33:26Z

I'm looking to re-build the entire plugin base using TypeScript due to the massive amounts of support for this plugin. Because of the defunct platform that ADT currently has no plans improving, I'm not sure if the switch to it would be worth the investment.

If you think this plugin can be further improved, please let me know, and I'll see if I can make this crucial plugin work out.

mrjackyliang · 2023-04-02T17:33:57Z

Tagging @Danimal4326 in for a discussion, see if you're interested.

mrjackyliang · 2023-04-02T17:49:54Z

The re-write versions will be in this branch and merged when everything is tested, documented, and stable.

Danimal4326 · 2023-04-02T17:50:31Z

I talked to ADT regarding upgrading my system to their newer platform (based on Alarm.com I believe) After discussing costs and benefits, I’ll be sticking with Pulse. They’ve upgraded my backed call box to LTE too so I don’t think Pulse is going anywhere, as they have a large installed base.

With that said, I’d love to see continued support for the plug-in as well as improvements

Danimal4326 · 2023-04-02T17:52:46Z

My ts skills are basic at best, as my day job is firmware development in C/C++ with Python for testing/support. But I’d love to help out in any way I can

mrjackyliang · 2023-04-02T18:02:06Z

My ts skills are basic at best, as my day job is firmware development in C/C++ with Python for testing/support. But I’d love to help out in any way I can

Yeah, I just had feelings that one day ADT might want to pull the plug, but it has been years and I'm sure I seem to like the way how everything works.

On the contrary, TypeScript is just JS with types haha, really nothing crazy about it. Plus, I'd convert this to ESM along the way.

mrjackyliang · 2023-07-31T15:19:22Z

Decided to put a pause on this for now. Will re-open when I decide it is worth doing.

mrjackyliang · 2023-11-21T05:05:22Z

Began re-writing the API today.

Future versions will no longer auto-detect accessories due to the fragility of users losing data often when ADT makes a unsuspecting change. Before updating, please make a detailed note of all your sensors info.

Name (the name you put in HomeKit, optional)
- Normally I'd put in the Room and then the sensor this is. For example, if this was a kitchen sink right side window, I'd name it something like "Kitchen Counter Window".
The EXACT name assigned for your ADT sensor
Note the type of the sensor. Homebridge now separates doors and window sensors (so please take note of that)
The zone number.

However, I may create a script for you to easily generate part of that configuration where you'd just need to focus on what to name your devices.

mrjackyliang · 2023-11-24T16:07:43Z

I've noticed something odd with the newer portal versions, and that is the orb.jsp file never loads during the summary page load. I do see that there is a updateContent() function on the summary page.

That is not called (because orb.jsp doesn't show in the networks tab), and I have a feeling that they may remove those pages or make it inaccessible in the future.

If that happens, the only way we can get status is through the summary page or the system page (which is fine). Marking this here to document there may be breaking changes.

UPDATE: My findings were incorrect. The function is being used, but not during initial page load. Only when something updates live while you are on the page.

mrjackyliang · 2023-11-26T02:34:34Z

I made some progress today and worked on reverse engineering the setArmState function and how it works.

Also, I forgot that I finally figured out why sometimes the sensors are blank and accidentally trigger the accessories reset. Nonetheless, having a manually configured sensors list is actually still the best just to protect ourselves from unwanted changes.

sapireli · 2023-11-26T02:54:13Z

is there any way to quickly export this?

Began re-writing the API today.

Future versions will no longer auto-detect accessories due to the fragility of users losing data often when ADT makes a unsuspecting change. Before updating, please make a detailed note of all your sensors info.

Name (the name you put in HomeKit, optional)

Normally I'd put in the Room and then the sensor this is. For example, if this was a kitchen sink right side window, I'd name it something like "Kitchen Counter Window".

The EXACT name assigned for your ADT sensor

Note the type of the sensor. Homebridge now separates doors and window sensors (so please take note of that)

The zone number.

However, I may create a script for you to easily generate part of that configuration where you'd just need to focus on what to name your devices.

mrjackyliang · 2023-11-26T03:00:06Z

is there any way to quickly export this?

Began re-writing the API today.

Future versions will no longer auto-detect accessories due to the fragility of users losing data often when ADT makes a unsuspecting change. Before updating, please make a detailed note of all your sensors info.

Name (the name you put in HomeKit, optional)

Normally I'd put in the Room and then the sensor this is. For example, if this was a kitchen sink right side window, I'd name it something like "Kitchen Counter Window".

The EXACT name assigned for your ADT sensor

Note the type of the sensor. Homebridge now separates doors and window sensors (so please take note of that)

The zone number.

However, I may create a script for you to easily generate part of that configuration where you'd just need to focus on what to name your devices.

Yes, I will include a script and instructions on how to easily export this. Might also add some recommendations on how to name the devices in case there is a need to reset the plugin (remembering which zone is which is a pain)

mrjackyliang · 2023-11-27T17:59:27Z

At the moment, working on the arm/disarm handlers. I found a few interesting arm states that are in the new version but never seen before in the older versions.

tr1um9h · 2023-11-27T18:10:04Z

Thanks for this! Any ETA on possible release?

mrjackyliang · 2023-11-27T18:16:16Z

Thanks for this! Any ETA on possible release?

I'm hoping in the next week or two. The plugin has to be completely rewritten.

mrjackyliang · 2023-11-28T17:40:11Z

Today, I finished the API portion of the plugin, and successfully completed testing. Going to make some optimizations before proceeding to the Homebridge plugin part.

Danimal4326 · 2023-11-28T17:42:00Z

Awesome!!! can't wait.

mrjackyliang · 2023-11-30T03:19:09Z

Today I spent some time refactoring the newly written API, and added some detection utilities to help with unexpected changes.

mrjackyliang · 2023-12-02T21:12:49Z

I've pushed the finished API along with the test files to the ts-rewrite branch.

sapireli · 2023-12-03T00:20:40Z

Jacky Liang coming in hot!

hapinstance · 2023-12-08T01:49:37Z

Wow! What an effort. Let me know if you need any help. I have some coding experience, and can assist in testing early versions if you like.

mrjackyliang · 2023-12-08T05:08:06Z

Wow! What an effort. Let me know if you need any help. I have some coding experience, and can assist in testing early versions if you like.

Will let you know, thank you!!

mrjackyliang · 2023-12-08T13:38:47Z

The fun part has come 👯

chabapj · 2023-12-16T21:55:40Z

It is working now - but it is a bit slow. The motion sensor takes 20-30 seconds to show motion, and then several minutes to reset itself to "no motion"?

The same for the door sensors. API polling interval?

mrjackyliang · 2023-12-16T22:35:03Z

It is working now - but it is a bit slow. The motion sensor takes 20-30 seconds to show motion, and then several minutes to reset itself to "no motion"?

The same for the door sensors. API polling interval?

I think I forgot to put in the force update after polling that's why it's taking forever.

sapireli · 2023-12-17T00:51:13Z

Ok was able to install, it’s working!! some issues:

High cpu usage - this plugin gets my cpu usage up to 100% every few seconds running on a raspberry pi, prior version had negligible effect on cpu.
As already reported updating sensors and security panel state takes forever.

Thank you for all the hard work @mrjackyliang

mrjackyliang · 2023-12-17T02:17:25Z

Ok was able to install, it’s working!! some issues:

High cpu usage - this plugin gets my cpu usage up to 100% every few seconds running on a raspberry pi, prior version had negligible effect on cpu.

As already reported updating sensors and security panel state takes forever.

Thank you for all the hard work @mrjackyliang

Oh high CPU? That's a first. I ran it on my system and it's working fine.

chabapj · 2023-12-17T02:26:01Z

I do not see any high CPU usage. I am running it on an 8-core beast, there is no difference between the plugin enabled or disabled.

mrjackyliang · 2023-12-17T02:26:13Z

@sapireli What are the specs to your Raspberry Pi? My CPU is running at the typical 2% right now. It's an i7

sapireli · 2023-12-17T02:37:34Z

@sapireli What are the specs to your Raspberry Pi? My CPU is running at the typical 2% right now. It's an i7

i'm using a trusty old raspi 1b, on the old plugin cpu usage would minimally increase 5-7% now its hitting 100%. i disabled it for now and its back down to 11%

sapireli · 2023-12-17T02:38:59Z

also why are you all using an i7 for homebridge? waste of $$ on electricity

mrjackyliang · 2023-12-17T02:41:54Z

also why are you all using an i7 for homebridge? waste of $$ on electricity

@sapireli I don't just use it for Homebridge. Would definitely be a waste if it really was for just that.

mrjackyliang · 2023-12-17T02:42:51Z

@sapireli What are the specs to your Raspberry Pi? My CPU is running at the typical 2% right now. It's an i7

i'm using a trusty old raspi 1b, on the old plugin cpu usage would minimally increase 5-7% now its hitting 100%. i disabled it for now and its back down to 11%

@sapireli That's odd, because the way how I coded the old plugin uses the same syncing methodology

mrjackyliang · 2023-12-17T04:23:41Z

I have a feeling it's because of OpenSSL and their EOL upgrade from 1.1.1 to 3.0.

I looked up Axios 100% high CPU just as a hunch and I'm thinking it's because of that. The old version used older ciphers and the depreciated request package, because some older Raspberry Pi's couldn't use the plugin, but Axios, unfortunately doesn't offer custom ciphers.

mrjackyliang · 2023-12-17T22:06:41Z

@sapireli Updated to v3.0.0-beta.6, you can now choose between 4 operational modes for your Raspberry Pi.

sapireli · 2023-12-18T04:29:00Z

last night i went down the rabbit hole of trying to upgrade the openssl library to 3.2, ended up destroying dietpi beyond recovery, and then spent way too many hours rebuilding / recreating automations. The homebridge backups weren't usable either. FML.

In any event, i ended up installing a bullseye version of dietpi instead of bookworm that has openssl 1.1.1. It does seem to be a lot faster now FYI.

sapireli · 2023-12-18T04:29:23Z

Ps. @mrjackyliang Thank you will try it tonight. You're the man.

mrjackyliang · 2023-12-18T05:21:12Z

last night i went down the rabbit hole of trying to upgrade the openssl library to 3.2, ended up destroying dietpi beyond recovery, and then spent way too many hours rebuilding / recreating automations. The homebridge backups weren't usable either. FML.

In any event, i ended up installing a bullseye version of dietpi instead of bookworm that has openssl 1.1.1. It does seem to be a lot faster now FYI.

Try to see if the 100% CPU comes back up even under a normal operational speed setting. I'm pretty sure it has to do with OpenSSL. That also was one of the knockers when the plugin was first released as well.

I do hope Axios can take care of it automatically because with request, I had to specify specific ciphers.

sapireli · 2023-12-18T16:07:17Z

New beta working well. After the downgrade to 'debian bullseye' i.e. Openssl 1.1.1, the CPU usage is back to normal. You were absolutely right.

The only two things are:

Now I'm seeing this error in the logs:
[12/18/2023, 10:59:32 AM] [ADT Pulse] Plugin is unable to initialize due to an invalid platform configuration. [ { "code": "invalid_union", "unionErrors": [ { "issues": [ { "code": "invalid_literal", "expected": "normal", "path": [ "mode" ], "message": "Invalid literal value, expected 'normal'" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": "paused", "path": [ "mode" ], "message": "Invalid literal value, expected 'paused'" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": "reset", "path": [ "mode" ], "message": "Invalid literal value, expected 'reset'" } ], "name": "ZodError" } ], "path": [ "mode" ], "message": "Invalid input" }, { "code": "invalid_union", "unionErrors": [ { "issues": [ { "code": "invalid_literal", "expected": 1, "path": [ "speed" ], "message": "Invalid literal value, expected 1" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": 0.75, "path": [ "speed" ], "message": "Invalid literal value, expected 0.75" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": 0.5, "path": [ "speed" ], "message": "Invalid literal value, expected 0.5" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": 0.25, "path": [ "speed" ], "message": "Invalid literal value, expected 0.25" } ], "name": "ZodError" } ], "path": [ "speed" ], "message": "Invalid input" } ]
and perhaps bump to the node version so this message doesnt show> 'The plugin "homebridge-adt-pulse" requires Node.js version of 18 which does not satisfy the current Node.js version of v20.10.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF'

Many thanks @mrjackyliang would love to buy you a drink i'm in NYC too.

mrjackyliang · 2023-12-18T16:11:56Z

New beta working well. After the downgrade to 'debian bullseye' i.e. Openssl 1.1.1, the CPU usage is back to normal. You were absolutely right.

The only two things are:

Now I'm seeing this error in the logs:

`[12/18/2023, 10:59:32 AM] [ADT Pulse] Plugin is unable to initialize due to an invalid platform configuration.

[

{

"code": "invalid_union",

"unionErrors": [

  {

    "issues": [

      {

        "code": "invalid_literal",

        "expected": "normal",

        "path": [

          "mode"

        ],

        "message": "Invalid literal value, expected 'normal'"

      }

    ],

    "name": "ZodError"

  },

  {

    "issues": [

      {

        "code": "invalid_literal",

        "expected": "paused",

        "path": [

          "mode"

        ],

        "message": "Invalid literal value, expected 'paused'"

      }

    ],

    "name": "ZodError"

  },

  {

    "issues": [

      {

        "code": "invalid_literal",

        "expected": "reset",

        "path": [

          "mode"

        ],

        "message": "Invalid literal value, expected 'reset'"

      }

    ],

    "name": "ZodError"

  }

],

"path": [

  "mode"

],

"message": "Invalid input"

},

{

"code": "invalid_union",

"unionErrors": [

  {

    "issues": [

      {

        "code": "invalid_literal",

        "expected": 1,

        "path": [

          "speed"

        ],

        "message": "Invalid literal value, expected 1"

      }

    ],

    "name": "ZodError"

  },

  {

    "issues": [

      {

        "code": "invalid_literal",

        "expected": 0.75,

        "path": [

          "speed"

        ],

        "message": "Invalid literal value, expected 0.75"

      }

    ],

    "name": "ZodError"

  },

  {

    "issues": [

      {

        "code": "invalid_literal",

        "expected": 0.5,

        "path": [

          "speed"

        ],

        "message": "Invalid literal value, expected 0.5"

      }

    ],

    "name": "ZodError"

  },

  {

    "issues": [

      {

        "code": "invalid_literal",

        "expected": 0.25,

        "path": [

          "speed"

        ],

        "message": "Invalid literal value, expected 0.25"

      }

    ],

    "name": "ZodError"

  }

],

"path": [

  "speed"

],

"message": "Invalid input"

}

]`

and perhaps bump to the node version so this message doesnt show> 'The plugin "homebridge-adt-pulse" requires Node.js version of 18 which does not satisfy the current Node.js version of v20.10.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF'

Many thanks @mrjackyliang would love to buy you a drink i'm in NYC too.

@sapireli Ah yes, the configuration changed a bit. I consolidated the Pause and Reset modes and added a Speed setting. The new config shape should be in the readme!

For the Homebridge version part, I have only tested it on Node.js 18. I know it is the last supported version, but from my experience, the last supported versions are actually the ones that are most stable overall. v20 is optimal, should work, v21 a bit too new and possibly plagued with unknown bugs.

Awesomeness!! Would love to meet whenever we get the chance to😁

knedd · 2023-12-18T16:25:13Z

I had those initial errors when I upgraded from beta 5 to beta 6. Upgrading my configuration file with the new additional attributes fixed it for meKevinSent via iPhoneOn Dec 18, 2023, at 5:12 PM, Jacky Liang ***@***.***> wrote: New beta working well. After the downgrade to 'debian bullseye' i.e. Openssl 1.1.1, the CPU usage is back to normal. You were absolutely right. The only two things are: Now I'm seeing this error in the logs: `[12/18/2023, 10:59:32 AM] [ADT Pulse] Plugin is unable to initialize due to an invalid platform configuration. [ { "code": "invalid_union", "unionErrors": [ { "issues": [ { "code": "invalid_literal", "expected": "normal", "path": [ "mode" ], "message": "Invalid literal value, expected 'normal'" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": "paused", "path": [ "mode" ], "message": "Invalid literal value, expected 'paused'" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": "reset", "path": [ "mode" ], "message": "Invalid literal value, expected 'reset'" } ], "name": "ZodError" } ], "path": [ "mode" ], "message": "Invalid input" }, { "code": "invalid_union", "unionErrors": [ { "issues": [ { "code": "invalid_literal", "expected": 1, "path": [ "speed" ], "message": "Invalid literal value, expected 1" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": 0.75, "path": [ "speed" ], "message": "Invalid literal value, expected 0.75" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": 0.5, "path": [ "speed" ], "message": "Invalid literal value, expected 0.5" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": 0.25, "path": [ "speed" ], "message": "Invalid literal value, expected 0.25" } ], "name": "ZodError" } ], "path": [ "speed" ], "message": "Invalid input" } ]` and perhaps bump to the node version so this message doesnt show> 'The plugin "homebridge-adt-pulse" requires Node.js version of 18 which does not satisfy the current Node.js version of v20.10.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF' Many thanks @mrjackyliang would love to buy you a drink i'm in NYC too. @sapireli Ah yes, the configuration changed a bit. I consolidated the Pause and Reset modes and added a Speed setting. The new config shape should be in the readme! Awesomeness!! Would love to meet whenever we get the chance to😁 —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

mrjackyliang · 2023-12-18T16:41:42Z

I had those initial errors when I upgraded from beta 5 to beta 6. Upgrading my configuration file with the new additional attributes fixed it for meKevinSent via iPhoneOn Dec 18, 2023, at 5:12 PM, Jacky Liang @.> wrote: New beta working well. After the downgrade to 'debian bullseye' i.e. Openssl 1.1.1, the CPU usage is back to normal. You were absolutely right. The only two things are: Now I'm seeing this error in the logs: [12/18/2023, 10:59:32 AM] [ADT Pulse] Plugin is unable to initialize due to an invalid platform configuration. [ { "code": "invalid_union", "unionErrors": [ { "issues": [ { "code": "invalid_literal", "expected": "normal", "path": [ "mode" ], "message": "Invalid literal value, expected 'normal'" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": "paused", "path": [ "mode" ], "message": "Invalid literal value, expected 'paused'" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": "reset", "path": [ "mode" ], "message": "Invalid literal value, expected 'reset'" } ], "name": "ZodError" } ], "path": [ "mode" ], "message": "Invalid input" }, { "code": "invalid_union", "unionErrors": [ { "issues": [ { "code": "invalid_literal", "expected": 1, "path": [ "speed" ], "message": "Invalid literal value, expected 1" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": 0.75, "path": [ "speed" ], "message": "Invalid literal value, expected 0.75" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": 0.5, "path": [ "speed" ], "message": "Invalid literal value, expected 0.5" } ], "name": "ZodError" }, { "issues": [ { "code": "invalid_literal", "expected": 0.25, "path": [ "speed" ], "message": "Invalid literal value, expected 0.25" } ], "name": "ZodError" } ], "path": [ "speed" ], "message": "Invalid input" } ] and perhaps bump to the node version so this message doesnt show> 'The plugin "homebridge-adt-pulse" requires Node.js version of 18 which does not satisfy the current Node.js version of v20.10.0. You may need to upgrade your installation of Node.js - see https://homebridge.io/w/JTKEF' Many thanks @mrjackyliang would love to buy you a drink i'm in NYC too. @sapireli Ah yes, the configuration changed a bit. I consolidated the Pause and Reset modes and added a Speed setting. The new config shape should be in the readme! Awesomeness!! Would love to meet whenever we get the chance to😁 —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.>

@knedd I attest to the huge blocks of error messages for the invalid configuration somewhat hard to read. I did spend some time trying to add custom messages to the schema validator, but the messages were wayyy too dynamic.

I'm pretty sure I had to account for more than 40 different error messages just in that config. Not sure if I really want to put the effort in that. In the future if I were to update the config to add supported sensors or even another setting, that's like another 6 error messages I need to add.

Danimal4326 · 2023-12-18T19:34:11Z

I just upgraded to the beta.

Not sure if this was mentioned, but if "name" does not match "adtName" in the plugin config, the sensor shows as unavailable.

mrjackyliang · 2023-12-18T22:22:21Z

I just upgraded to the beta.

Not sure if this was mentioned, but if "name" does not match "adtName" in the plugin config, the sensor shows as unavailable.

@Danimal4326 Mmm, they don't have to match each other. I think the sensor shows as unavailable because of the slow updating.

Danimal4326 · 2023-12-18T22:23:57Z

Hmm I changed the name to match, and they immediately showed as available..

let me test again.

mrjackyliang · 2023-12-18T22:25:11Z

Hmm I changed the name to match, and they immediately showed as available..

let me test again.

@Danimal4326 Yeah the sensor's updating is slow, haven't worked on it yet. Yesterday I re-built the config UI, and that took an entire day

sapireli · 2023-12-18T23:54:26Z

tty sure I had to account for more than 40 different error messages just in that config. Not sure if I really want to put the effort in that. In the future if I were to update the config to add supported sensors or even another setting, that's like another 6 error messages I need to add.

That fixed it. i could have sworn i updated the config i guess i didn't save or something. Many thanks!

sapireli · 2023-12-19T07:16:08Z

beta 6 still going strong only recurring issue is some sensors aren't being matched although less with every restart.

take for example:

12/19/2023, 2:09:45 AM] [ADT Pulse] Attempted to add or update Window 1 Glass (zone: 25) accessory that does not exist on the portal.
[12/19/2023, 2:09:45 AM] [ADT Pulse] Attempted to add or update Window 2 Glass (zone: 27) accessory that does not exist on the portal.
[12/19/2023, 2:10:22 AM] [ADT Pulse] Attempted to add or update Window 1 Glass (zone: 25) accessory that does not exist on the portal.
[12/19/2023, 2:10:22 AM] [ADT Pulse] Attempted to add or update Window 2 Glass (zone: 27) accessory that does not exist on the portal.

all these zones are correct, and the spelling is exact.

mrjackyliang · 2023-12-19T13:22:25Z

beta 6 still going strong only recurring issue is some sensors aren't being matched although less with every restart.

take for example:

12/19/2023, 2:09:45 AM] [ADT Pulse] Attempted to add or update Window 1 Glass (zone: 25) accessory that does not exist on the portal.
[12/19/2023, 2:09:45 AM] [ADT Pulse] Attempted to add or update Window 2 Glass (zone: 27) accessory that does not exist on the portal.
[12/19/2023, 2:10:22 AM] [ADT Pulse] Attempted to add or update Window 1 Glass (zone: 25) accessory that does not exist on the portal.
[12/19/2023, 2:10:22 AM] [ADT Pulse] Attempted to add or update Window 2 Glass (zone: 27) accessory that does not exist on the portal.

all these zones are correct, and the spelling is exact.

@sapireli Does this happen all the time, or from time to time? If it is from time to time, then it is probably ADT wanting to act up again. Definitely need to figure out how to better support these errors.

mrjackyliang · 2023-12-19T15:19:07Z

Let's continue this conversation in #124, thanks! This thread is too long to scroll down to🥲

mrjackyliang · 2023-12-19T15:19:56Z

Also plugin has been updated to v3.0.0-beta.7

mrjackyliang added the enhancement New feature or request label Apr 2, 2023

mrjackyliang closed this as completed Jul 31, 2023

mrjackyliang reopened this Nov 21, 2023

This was referenced Nov 21, 2023

Door sensor is reported OPEN in Homebridge but CLOSED in ADT Pulse App. The door is CLOSED. #116

Closed

pyadtpulse has a simple page for grabbing the browser fingerprint #111

Closed

mrjackyliang mentioned this issue Nov 27, 2023

Sensors not appearing #117

Closed

mrjackyliang mentioned this issue Nov 30, 2023

"Exclude" Option to hide/disable sensors #118

Closed

mrjackyliang mentioned this issue Dec 8, 2023

Accessories not populating with "TypeError: Cannot read properties of undefined (reading 'getCharacteristic')" #119

Closed

Repository owner locked and limited conversation to collaborators Dec 19, 2023

mrjackyliang unpinned this issue Jan 27, 2024

v3 Development - Calling All TypeScript Developers #98

v3 Development - Calling All TypeScript Developers #98

Comments

mrjackyliang commented Apr 2, 2023

mrjackyliang commented Apr 2, 2023

mrjackyliang commented Apr 2, 2023

Danimal4326 commented Apr 2, 2023

Danimal4326 commented Apr 2, 2023

mrjackyliang commented Apr 2, 2023

mrjackyliang commented Jul 31, 2023

mrjackyliang commented Nov 21, 2023 • edited Loading

mrjackyliang commented Nov 24, 2023 • edited Loading

mrjackyliang commented Nov 26, 2023 • edited Loading

sapireli commented Nov 26, 2023

mrjackyliang commented Nov 26, 2023

mrjackyliang commented Nov 27, 2023

tr1um9h commented Nov 27, 2023

mrjackyliang commented Nov 27, 2023

mrjackyliang commented Nov 28, 2023

Danimal4326 commented Nov 28, 2023

mrjackyliang commented Nov 30, 2023

mrjackyliang commented Dec 2, 2023

sapireli commented Dec 3, 2023

hapinstance commented Dec 8, 2023

mrjackyliang commented Dec 8, 2023

mrjackyliang commented Dec 8, 2023

chabapj commented Dec 16, 2023 • edited Loading

mrjackyliang commented Dec 16, 2023

sapireli commented Dec 17, 2023

mrjackyliang commented Dec 17, 2023

chabapj commented Dec 17, 2023

mrjackyliang commented Dec 17, 2023

sapireli commented Dec 17, 2023

sapireli commented Dec 17, 2023

mrjackyliang commented Dec 17, 2023

mrjackyliang commented Dec 17, 2023

mrjackyliang commented Dec 17, 2023

mrjackyliang commented Dec 17, 2023

sapireli commented Dec 18, 2023 • edited Loading

sapireli commented Dec 18, 2023

mrjackyliang commented Dec 18, 2023

sapireli commented Dec 18, 2023

mrjackyliang commented Dec 18, 2023 • edited Loading

knedd commented Dec 18, 2023 via email

mrjackyliang commented Dec 18, 2023

Danimal4326 commented Dec 18, 2023

mrjackyliang commented Dec 18, 2023

Danimal4326 commented Dec 18, 2023

mrjackyliang commented Dec 18, 2023

sapireli commented Dec 18, 2023

sapireli commented Dec 19, 2023

mrjackyliang commented Dec 19, 2023

mrjackyliang commented Dec 19, 2023

mrjackyliang commented Dec 19, 2023

mrjackyliang commented Nov 21, 2023 •

edited

Loading

mrjackyliang commented Nov 24, 2023 •

edited

Loading

mrjackyliang commented Nov 26, 2023 •

edited

Loading

chabapj commented Dec 16, 2023 •

edited

Loading

sapireli commented Dec 18, 2023 •

edited

Loading

mrjackyliang commented Dec 18, 2023 •

edited

Loading