v3.0.0 Beta Testers

[mrjackyliang]

Creating a thread here for all beta testing issues.

[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?

@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.

I have noticed that now in my homebridge it says "Plugin is unable to initialize due to an invalid platform configuration." Have you seen this issue?

[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.

I have noticed that now in my homebridge it says "Plugin is unable to initialize due to an invalid platform configuration." Have you seen this issue?

That is because the configuration has changed to a new one. The old config does not work anymore. You can read the readme to update them, or use the config UI (if you're not using HOOBS). HOOBS is not supported due to the product being stale.

[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?

@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.

I have noticed that now in my homebridge it says "Plugin is unable to initialize due to an invalid platform configuration." Have you seen this issue?

That is because the configuration has changed to a new one. The old config does not work anymore. You can read the readme to update them, or use the config UI (if you're not using HOOBS). HOOBS is not supported due to the product being stale.

Ok I understand. I added my keypad and it sort of works now. I can arm and disarm the panel from the Home app. However when I try and arm the panel, it arms and then quickly disarms the panel and then arms it again. Additionally, the homebridge logs say "Attempted to add or update Security Panel (zone: 1) accessory that does not exist on the portal." I logged into my ADTPortal to try and identify which zone my security panel is on, but it doesn't say a zone number.

[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.

I have noticed that now in my homebridge it says "Plugin is unable to initialize due to an invalid platform configuration." Have you seen this issue?

That is because the configuration has changed to a new one. The old config does not work anymore. You can read the readme to update them, or use the config UI (if you're not using HOOBS). HOOBS is not supported due to the product being stale.

Ok I understand. I added my keypad and it sort of works now. I can arm and disarm the panel from the Home app. However when I try and arm the panel, it arms and then quickly disarms the panel and then arms it again. Additionally, the homebridge logs say "Attempted to add or update Security Panel (zone: 1) accessory that does not exist on the portal." I logged into my ADTPortal to try and identify which zone my security panel is on, but it doesn't say a zone number.

@bvelazquez1 Yes I am aware of that issue. I checked my system yesterday and it's indeed doing that on mine as well. For the Security Panel accessory, are you able to run commands on your system? Specifically this:

cd homebridge-adt-pulse && npm run test-api

I need to know if the tests pass, or if something is up here.

[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?

@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.

I have noticed that now in my homebridge it says "Plugin is unable to initialize due to an invalid platform configuration." Have you seen this issue?

That is because the configuration has changed to a new one. The old config does not work anymore. You can read the readme to update them, or use the config UI (if you're not using HOOBS). HOOBS is not supported due to the product being stale.

Ok I understand. I added my keypad and it sort of works now. I can arm and disarm the panel from the Home app. However when I try and arm the panel, it arms and then quickly disarms the panel and then arms it again. Additionally, the homebridge logs say "Attempted to add or update Security Panel (zone: 1) accessory that does not exist on the portal." I logged into my ADTPortal to try and identify which zone my security panel is on, but it doesn't say a zone number.

@bvelazquez1 Yes I am aware of that issue. I checked my system yesterday and it's indeed doing that on mine as well. For the Security Panel accessory, are you able to run commands on your system? Specifically this:

cd homebridge-adt-pulse && npm run test-api

I need to know if the tests pass, or if something is up here.

I attempted to run that command but it said "No such file or directory"

[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.

I have noticed that now in my homebridge it says "Plugin is unable to initialize due to an invalid platform configuration." Have you seen this issue?

That is because the configuration has changed to a new one. The old config does not work anymore. You can read the readme to update them, or use the config UI (if you're not using HOOBS). HOOBS is not supported due to the product being stale.

Ok I understand. I added my keypad and it sort of works now. I can arm and disarm the panel from the Home app. However when I try and arm the panel, it arms and then quickly disarms the panel and then arms it again. Additionally, the homebridge logs say "Attempted to add or update Security Panel (zone: 1) accessory that does not exist on the portal." I logged into my ADTPortal to try and identify which zone my security panel is on, but it doesn't say a zone number.

@bvelazquez1 Yes I am aware of that issue. I checked my system yesterday and it's indeed doing that on mine as well. For the Security Panel accessory, are you able to run commands on your system? Specifically this:

cd homebridge-adt-pulse && npm run test-api

I need to know if the tests pass, or if something is up here.

I attempted to run that command but it said "No such file or directory"

First type pwd, also let me know what are you using (HOOBS, Homebridge, OS)

[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?

@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.

I have noticed that now in my homebridge it says "Plugin is unable to initialize due to an invalid platform configuration." Have you seen this issue?

That is because the configuration has changed to a new one. The old config does not work anymore. You can read the readme to update them, or use the config UI (if you're not using HOOBS). HOOBS is not supported due to the product being stale.

Ok I understand. I added my keypad and it sort of works now. I can arm and disarm the panel from the Home app. However when I try and arm the panel, it arms and then quickly disarms the panel and then arms it again. Additionally, the homebridge logs say "Attempted to add or update Security Panel (zone: 1) accessory that does not exist on the portal." I logged into my ADTPortal to try and identify which zone my security panel is on, but it doesn't say a zone number.

@bvelazquez1 Yes I am aware of that issue. I checked my system yesterday and it's indeed doing that on mine as well. For the Security Panel accessory, are you able to run commands on your system? Specifically this:

cd homebridge-adt-pulse && npm run test-api

I need to know if the tests pass, or if something is up here.

I attempted to run that command but it said "No such file or directory"

First type pwd, also let me know what are you using (HOOBS, Homebridge, OS)

tried it with pwd but now I just get the following error:

/var/lib/homebridge npm ERR! Missing script: "test-api" npm ERR! npm ERR! To see a list of scripts, run: npm ERR! npm run

npm ERR! A complete log of this run can be found in: /home/homebridge/.npm/_logs/2023-12-27T03_41_45_174Z-debug-0.log

I am running Homebridge on a raspberry pi with Debian GNU/Linux Bookworm (12) as my OS

[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.

I have noticed that now in my homebridge it says "Plugin is unable to initialize due to an invalid platform configuration." Have you seen this issue?

That is because the configuration has changed to a new one. The old config does not work anymore. You can read the readme to update them, or use the config UI (if you're not using HOOBS). HOOBS is not supported due to the product being stale.

Ok I understand. I added my keypad and it sort of works now. I can arm and disarm the panel from the Home app. However when I try and arm the panel, it arms and then quickly disarms the panel and then arms it again. Additionally, the homebridge logs say "Attempted to add or update Security Panel (zone: 1) accessory that does not exist on the portal." I logged into my ADTPortal to try and identify which zone my security panel is on, but it doesn't say a zone number.

@bvelazquez1 Yes I am aware of that issue. I checked my system yesterday and it's indeed doing that on mine as well. For the Security Panel accessory, are you able to run commands on your system? Specifically this:

cd homebridge-adt-pulse && npm run test-api

I need to know if the tests pass, or if something is up here.

I attempted to run that command but it said "No such file or directory"

First type pwd, also let me know what are you using (HOOBS, Homebridge, OS)

tried it with pwd but now I just get the following error:

/var/lib/homebridge

npm ERR! Missing script: "test-api"

npm ERR!

npm ERR! To see a list of scripts, run:

npm ERR! npm run

npm ERR! A complete log of this run can be found in: /home/homebridge/.npm/_logs/2023-12-27T03_41_45_174Z-debug-0.log

I am running Homebridge on a raspberry pi with Debian GNU/Linux Bookworm (12) as my OS

@bvelazquez1 Yes, it wasn't supposed to work. pwd is a command to let me know which directory you are in. You can try this:

cd /var/lib/homebridge/node_modules/homebridge-adt-pulse && npm run test-api

[mrjackyliang]

Released v3.0.0-beta.12. Added some new detected sensors and sensor statuses. Please update if you can. Will need to continue getting more information about the recent statuses I've been seeing.

[jastorino82]

I installed beta 12. I still am seeing the same issues as beta 11. Specifically:

• If I arm in the home app, the panel arms, disarms, and then arms again

• All my sensors except one show “No response.” The vast majority are door/window contact sensors, but also 1 smoke and 3 motions. 1 window sensor status shows correctly for some reason.

[mrjackyliang]

I installed beta 12. I still am seeing the same issues as beta 11. Specifically:

• If I arm in the home app, the panel arms, disarms, and then arms again

• All my sensors except one show “No response.” The vast majority are door/window contact sensors, but also 1 smoke and 3 motions. 1 window sensor status shows correctly for some reason.

@jastorino82 Yes, the updates did not fix anything. They are supposed to assist me with today's development in fixing them.

[mrjackyliang]

Currently working on re-building the panel status detector. These are the statuses I've seen from the detector in the plugin.

const regex = /^([A-Za-z0-9 ]+)\. ?([A-Za-z0-9 ]*)\.?$/;
//const text = 'Armed Away. Sensor Bypassed.';
//const text = 'Armed Stay. All Quiet. This may take several minutes.';
//const text = 'All Quiet.';
const text = 'Armed Stay, No Entry Delay. All Quiet.';

const sections = text.split(/\.\s*/).filter(Boolean);

for (let i = 0; i < sections.length; i += 1) {
  sections[i] = sections[i].split(', ')
}

console.log(sections);

> Array [Array ["Armed Stay", "No Entry Delay"], Array ["All Quiet"]]

[knedd]

Thanks for the update. KevinSent via iPhoneOn Dec 29, 2023, at 10:16 AM, Jacky Liang @.**> wrote: Currently working on re-building the panel status detector. These are the statuses I've seen from the detector in the plugin. const regex = /^([A-Za-z0-9 ]+). ?([A-Za-z0-9 ]).?$/; //const text = 'Armed Away. Sensor Bypassed.'; //const text = 'Armed Stay. All Quiet. This may take several minutes.'; //const text = 'All Quiet.'; const text = 'Armed Stay, No Entry Delay. All Quiet.';

const sections = text.split(/.\s*/).filter(Boolean);

for (let i = 0; i < sections.length; i += 1) { sections[i] = sections[i].split(', ') }

console.log(sections);

Array [Array ["Armed Stay", "No Entry Delay"], Array ["All Quiet"]]

—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]

Thanks for the update. KevinSent via iPhoneOn Dec 29, 2023, at 10:16 AM, Jacky Liang @.**> wrote: Currently working on re-building the panel status detector. These are the statuses I've seen from the detector in the plugin. const regex = /^([A-Za-z0-9 ]+). ?([A-Za-z0-9 ]).?$/; //const text = 'Armed Away. Sensor Bypassed.'; //const text = 'Armed Stay. All Quiet. This may take several minutes.'; //const text = 'All Quiet.'; const text = 'Armed Stay, No Entry Delay. All Quiet.';

const sections = text.split(/.\s*/).filter(Boolean);

for (let i = 0; i < sections.length; i += 1) { sections[i] = sections[i].split(', ') }

console.log(sections);

Array [Array ["Armed Stay", "No Entry Delay"], Array ["All Quiet"]]

—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]

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 just started to think about this, and I realized that if I allow users to manually set debug mode, that would mean that Homebridge may or may not be in debug mode, and that will cause some messages to go missing, especially for logs that are sent only via Homebridge and not the API.

[mrjackyliang]

v3.0.0-beta.13 should be up soon. Seeing if this fixes that issue. You may get more errors because, I have added a lot more of those to see what causes the sensors to not work.

[jastorino82]

v3.0.0-beta.13 should be up soon. Seeing if this fixes that issue. You may get more errors because, I have added a lot more of those to see what causes the sensors to not work.

Thanks Jacky, I installed beta 13. I see this in my logs now for all my window/door contact sensors

[30/12/2023, 19:47:48] [ADT Pulse] Attempted to get sensor status on Basement Office Window (id: adt-device-7, uuid: ) accessory but sensor is not found or sensor type is not supported.

Then this for motion detectors

[30/12/2023, 19:49:27] [ADT Pulse] Attempted to get sensor status on Living Room Motion Detector (id: adt-device-19, uuid: ) accessory but actions have not been implemented yet.

I assume these new logs are all part of the troubleshooting / upgrade effort, but just wanted to pass on what I see in case it is of any help. Thanks!

[mrjackyliang]

v3.0.0-beta.14 is up, sorry peeps. The last version sent me device contexts that had nothing to do with understanding the panel/sensor statuses.

Kek. What I get for coding while having a cold...

[mrjackyliang]

v3.0.0-beta.13 should be up soon. Seeing if this fixes that issue. You may get more errors because, I have added a lot more of those to see what causes the sensors to not work.

Thanks Jacky, I installed beta 13. I see this in my logs now for all my window/door contact sensors

[30/12/2023, 19:47:48] [ADT Pulse] Attempted to get sensor status on Basement Office Window (id: adt-device-7, uuid: ) accessory but sensor is not found or sensor type is not supported.

Then this for motion detectors

[30/12/2023, 19:49:27] [ADT Pulse] Attempted to get sensor status on Living Room Motion Detector (id: adt-device-19, uuid: ) accessory but actions have not been implemented yet.

I assume these new logs are all part of the troubleshooting / upgrade effort, but just wanted to pass on what I see in case it is of any help. Thanks!

@jastorino82 If the first error message only comes up once, you can ignore it. If it comes up more than once, it is a problem. The second error message is valid. I should be getting the statuses and then figuring out what to do with them.

[jastorino82]

v3.0.0-beta.13 should be up soon. Seeing if this fixes that issue. You may get more errors because, I have added a lot more of those to see what causes the sensors to not work.

Thanks Jacky, I installed beta 13. I see this in my logs now for all my window/door contact sensors [30/12/2023, 19:47:48] [ADT Pulse] Attempted to get sensor status on Basement Office Window (id: adt-device-7, uuid: ) accessory but sensor is not found or sensor type is not supported. Then this for motion detectors [30/12/2023, 19:49:27] [ADT Pulse] Attempted to get sensor status on Living Room Motion Detector (id: adt-device-19, uuid: ) accessory but actions have not been implemented yet. I assume these new logs are all part of the troubleshooting / upgrade effort, but just wanted to pass on what I see in case it is of any help. Thanks!

@jastorino82 If the first error message only comes up once, you can ignore it. If it comes up more than once, it is a problem. The second error message is valid. I should be getting the statuses and then figuring out what to do with them.

Yeah, so I get the first message constantly over and over for all door/window and smoke sensors, and the second message constantly for motions

[knedd]

I am getting the …Attempted to get sensor status…error for my gas, smoke, and heat detectors. KevinSent via iPhoneOn Dec 30, 2023, at 8:32 PM, Jacky Liang @.***> wrote: v3.0.0-beta.14 is up, sorry peeps. The last version sent me device contexts that had nothing to do with understanding the panel/sensor statuses. Kek. What I get for coding while having a cold...

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

[jastorino82]

Just making a note, same issue as I just posted is observed on beta 14. Same logs every few seconds

[30/12/2023, 19:47:48] [ADT Pulse] Attempted to get sensor status on Basement Office Window (id: adt-device-7, uuid: ) accessory but sensor is not found or sensor type is not supported.

Then this for motion detectors [30/12/2023, 19:49:27] [ADT Pulse] Attempted to get sensor status on Living Room Motion Detector (id: adt-device-19, uuid: ) accessory but actions have not been implemented yet.

[mrjackyliang]

v3.0.0-beta.13 should be up soon. Seeing if this fixes that issue. You may get more errors because, I have added a lot more of those to see what causes the sensors to not work.

Thanks Jacky, I installed beta 13. I see this in my logs now for all my window/door contact sensors [30/12/2023, 19:47:48] [ADT Pulse] Attempted to get sensor status on Basement Office Window (id: adt-device-7, uuid: ) accessory but sensor is not found or sensor type is not supported. Then this for motion detectors [30/12/2023, 19:49:27] [ADT Pulse] Attempted to get sensor status on Living Room Motion Detector (id: adt-device-19, uuid: ) accessory but actions have not been implemented yet. I assume these new logs are all part of the troubleshooting / upgrade effort, but just wanted to pass on what I see in case it is of any help. Thanks!

@jastorino82 If the first error message only comes up once, you can ignore it. If it comes up more than once, it is a problem. The second error message is valid. I should be getting the statuses and then figuring out what to do with them.

Yeah, so I get the first message constantly over and over for all door/window and smoke sensors, and the second message constantly for motions

@jastorino82 Yes, those are correct. I will be making more adjustments soon.

[mrjackyliang]

I am getting the …Attempted to get sensor status…error for my gas, smoke, and heat detectors. KevinSent via iPhoneOn Dec 30, 2023, at 8:32 PM, Jacky Liang @.> wrote: v3.0.0-beta.14 is up, sorry peeps. The last version sent me device contexts that had nothing to do with understanding the panel/sensor statuses. Kek. What I get for coding while having a cold... —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.>

@knedd Yes, these few versions will have a lot of errors popping up. They're just were never shown before. As long as I keep getting the status updates, I'll make more updates.

[mrjackyliang]

v3.0.0-beta.15 another fix again. Okay this is probably my last one for today.

[mrjackyliang]

Also forgot to mention beta 13+ should fix the repetitive arming/disarming issue. I checked this morning, everything works as expected.

Plus the plugin no longer logs in and out every 5 mins due to the keep alive checks it does

[mrjackyliang]

@Danimal4326 I remember somewhere you mentioned that the status didn't update because the display name and ADT sensor name weren't the same. You are right. The checks were too strict apparently.

[knedd]

@ Jacky

Do you know why I am now getting the following messages for these sensors along with them now not responding in HomeKit?

[12/31/2023, 9:49:06 AM] [ADT Pulse] Attempted to get sensor status on 2nd Floor Smoke (id: adt-device-16, uuid: f598ec0c-4e65-4137-bae1-b065cd06c0f6) accessory but actions have not been implemented yet. [12/31/2023, 9:49:06 AM] [ADT Pulse] Attempted to get sensor status on Kitchen Heat Detector (id: adt-device-15, uuid: 3d1bd248-358c-4ef9-8ae8-f3564643fab0) accessory but actions have not been implemented yet. [12/31/2023, 9:49:06 AM] [ADT Pulse] Attempted to get sensor status on Basement Gas Detector (id: adt-device-68, uuid: 81dcb64d-9991-446b-98be-7264d4c798a9) accessory but actions have not been implemented yet.

Thanks,

Kevin

[mrjackyliang]

@ Jacky Do you know why I am now getting the following messages for these sensors along with them now not responding in HomeKit? [12/31/2023, 9:49:06 AM] [ADT Pulse] Attempted to get sensor status on 2nd Floor Smoke (id: adt-device-16, uuid: f598ec0c-4e65-4137-bae1-b065cd06c0f6) accessory but actions have not been implemented yet. [12/31/2023, 9:49:06 AM] [ADT Pulse] Attempted to get sensor status on Kitchen Heat Detector (id: adt-device-15, uuid: 3d1bd248-358c-4ef9-8ae8-f3564643fab0) accessory but actions have not been implemented yet. [12/31/2023, 9:49:06 AM] [ADT Pulse] Attempted to get sensor status on Basement Gas Detector (id: adt-device-68, uuid: 81dcb64d-9991-446b-98be-7264d4c798a9) accessory but actions have not been implemented yet. Thanks, Kevin

@knedd Yes, I have located the issue and have fixed it. I'm now implementing the other enhancements before pushing the next version.

[mrjackyliang]

v3.0.0-beta.16 is up. Fixes the sensor not being displayed! And now every sensor includes optional information, such as low battery, or if the sensor went offline as well. We're getting closer and closer to stable :)

[mrjackyliang]

Made some minor changes to the plugin, updated to v3.0.0-beta.17

[jastorino82]

It’s working!!!

[mrjackyliang]

It’s working!!!

@jastorino82 Thanks for your patience! There will be some sensors that don't properly work, but with time, they will be resolved!

[sapireli]

Question for @mrjackyliang

Is it possible to split up the sensors and panel management such that if i have zero sensors added, i can still control the panel but the updates are super fast without the cpu overhead of the sensors? Right now when i run it without all the sensors, CPU utilization is still quiet high. I guess what i'm asking is would it be hard to have aggressive synchronization for panel status and slow or now sync at all for sensors?

[sapireli]

Also Happy new year @mrjackyliang and thank you for all the hard work you've put into this!

[mrjackyliang]

Question for @mrjackyliang

Is it possible to split up the sensors and panel management such that if i have zero sensors added, i can still control the panel but the updates are super fast without the cpu overhead of the sensors? Right now when i run it without all the sensors, CPU utilization is still quiet high. I guess what i'm asking is would it be hard to have aggressive synchronization for panel status and slow or now sync at all for sensors?

@sapireli I believe it has to do with the portal syncing issue. Did you happen to try to set the operating speed to 0.25x?

Splitting them unfortunately won't work because that's what keeps the plugin working, and the core design mimics how the portal works (every 3 seconds or so doing a sync, and every 8.9 mins running a keep alive check).

There is one last thing to check, the OpenSSL version. The latest upgrade to v3 really killed a lot of older devices, as v1.1.1 was way faster.

You can attempt to downgrade, but there is a security risk since it is depreciated.

[sapireli]

Yep i set the speed to .25x and it didnt really make much of a difference as it still roughly hovers around 30% utilization and spikes up to 100% now and then. I have it running on a child bridge and its by far the highest cpu consumer for some reason. I guess the only option is to wait for the trixie upgrade which comes with openssl 3.1 that should speed things up from what i read

[sapireli]

one follow up question: should removing sensors from homebridge theoretically reduce load or it doesn't matter?

[mrjackyliang]

one follow up question: should removing sensors from homebridge theoretically reduce load or it doesn't matter?

@sapireli It doesn't matter. The same process flow goes through regardless if you have sensors or not. Mainly because it's the sync code that's causing the huge load. And unfortunately that is one single endpoint for all devices

[mrjackyliang]

I also want to note some odd things with the update. If anyone here has glass break detectors, please remove them from the config, and then re-add them again.

I think that's because the service was changed from Motion Detector to Occupancy Detector.

I might be able to remove them later on, but I prefer the user themselves take control of this situation.

[sapireli]

i see a lot of these FWIW:

[1/1/2024, 12:58:15 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:15 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:15 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:15 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:15 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:21 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:21 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:21 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:21 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:21 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:25 AM] [ADT Pulse] Attempted to set panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:25 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:31 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:31 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:31 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:31 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:31 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:32 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:32 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:32 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:32 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:32 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:41 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:41 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:42 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:42 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:45 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:45 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:45 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet. [1/1/2024, 12:58:45 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[mrjackyliang]

i see a lot of these FWIW:

[1/1/2024, 12:58:15 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:15 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:15 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:15 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:15 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:21 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:21 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:21 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:21 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:21 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:25 AM] [ADT Pulse] Attempted to set panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:25 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:31 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:31 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:31 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:31 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:31 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:32 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:32 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:32 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:32 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:32 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:41 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:41 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:42 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:42 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:45 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:45 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:45 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

[1/1/2024, 12:58:45 AM] [ADT Pulse] Attempted to get panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but panel status has not been retrieved yet.

@sapireli Can you login to your portal and tell me what you see below the circle button?

[sapireli]

@mrjackyliang you mean the arm/disarm button? Under it I see "Disarmed. All Quiet." My Web Portal version: 27.0.0-140

[mrjackyliang]

@mrjackyliang you mean the arm/disarm button? Under it I see "Disarmed. All Quiet." My Web Portal version: 27.0.0-140

@sapireli Yes, it the error still happening now? Seems like it only appears when you initialize the plugin.

[sapireli]

I think you're right as i just tested and seemed ok but there is also something else that is weird in homebrdige accessories tab i see the new panel status shortly after it is armed etc, but in the home app it shows "no response" for some time after that.

[sapireli]

Nope i take that back @mrjackyliang tested again same error comes up: [1/1/2024, 1:24:07 AM] [ADT Pulse] Attempted to set panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but request was not successful.

[mrjackyliang]

I think you're right as i just tested and seemed ok but there is also something else that is weird in homebrdige accessories tab i see the new panel status shortly after it is armed etc, but in the home app it shows "no response" for some time after that.

@sapireli Yeah that happens with me as well. Trying to figure out why. As for the errors you're getting, I'll just set those logs to display in debug mode instead so they don't fill up your log file unnecessarily. I also noticed earlier, the panel was armed stay, but Home app showed Off...

I gave it a shake and it fixed it self. So odd.

[mrjackyliang]

Nope i take that back @mrjackyliang tested again same error comes up:

[1/1/2024, 1:24:07 AM] [ADT Pulse] Attempted to set panel status on Security Panel (id: adt-device-1, uuid: af79de8a-2216-49c1-aafa-606251d39c3e) accessory but request was not successful.

@sapireli Oh that error is different from before. I'm going to guess that the system is already armed.

[sapireli]

yep :) it is

[mrjackyliang]

yep :) it is

@sapireli Ah, okay. Looks like I shall make some optimizations.