Accessories not populating with "TypeError: Cannot read properties of undefined (reading 'getCharacteristic')" #119
Comments
|
I'm working on a new version of the plugin, 60% complete. Follow issue #98. |
|
Wait. This is so weird. Why are all the sensors set to zone 0. My thought: Probably because the current version is using the orb file to detect sensors and the markup changed🤔 But keeping closed for now since I don't use the |
|
Yes! Weird that was one of my questions. They used to be assigned a number based on zone. As for the water sensor, I used to override it and the heat detector- MattOn Dec 9, 2023, at 11:33 AM, Jacky Liang ***@***.***> wrote:
Wait. This is so weird. Why are all the sensors set to zone 0
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Maybe it's defaulting to 0 because it couldn't detect the zone. My guess is that it was lodash defaulting to it heh. |
|
https://portal.adtpulse.com/myhome/27.0.0-140/ajax/orb.jsp does list the Zones. I’m not sure if that is where you pick them up from.
From: Jacky Liang ***@***.***>
Sent: Saturday, December 9, 2023 3:18 PM
To: mrjackyliang/homebridge-adt-pulse ***@***.***>
Cc: hapinstance ***@***.***>; Author ***@***.***>
Subject: Re: [mrjackyliang/homebridge-adt-pulse] Accessories not populating with "TypeError: Cannot read properties of undefined (reading 'getCharacteristic')" (Issue #119)
Maybe it's defaulting to 0 because it couldn't detect the zone. My guess is that it was lodash defaulting to it heh.
—
Reply to this email directly, view it on GitHub <#119 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWODTQLA3YO6TJ6IRPQEOVLYITBOBAVCNFSM6AAAAABAL2O6EOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBYGY3DSOJSGU> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AWODTQKZDOB3BGOH6V2HD33YITBOBA5CNFSM6AAAAABAL2O6EOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTOGB3OK.gif> Message ID: ***@***.*** ***@***.***> >
|
|
They do list the zones, it's when it doesn't. I noticed it when I was re-building the plugin, that they sometimes use a different markup path and causes the detection to go from all your sensors to none. |
|
And one of the reasons why the new version will no longer detect new sensors or remove them. It will base it all on your config, and then match them so when ADT decides to play tricks on us again, at least we don't have to go and wonder what the heck was "Basement Window (548)" 🤣 |
|
This may be a shift in the industry away from open API’s. I also used the MyQ plugin, but the vendor started blocking access to it about 5 weeks ago. If that is the case it would be a shame. Anyway, let me know if I can help with any testing.On Dec 9, 2023, at 8:46 PM, Jacky Liang ***@***.***> wrote:
And one of the reasons why the new version will no longer detect new sensors or remove them. It will base it all on your config, and then match them so when ADT decides to play tricks on us again, at least we don't have to go and wonder what the heck was "Basement Window (548)" 🤣
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I hinted on that when I started building the new plugin. I copied the headers down completely from Chrome 119, and plan to update those as fast as Chrome becomes updated. If things become worse, I can always sniff the packets from the ADT Pulse app. |
|
This issue is now locked and considered resolved due to inactivity. |
Describe the bug:
I had to replace a sensor in my system. Once I replaced the sensor I checked the "Reset Plugin" option in the plugin, saved (restarted) waited a while, and then unchecked the "Reset Plugin" option, saved (restarted) the plugin again. The plugin reports every second or so [ ERROR ] An unknown error occurred. In the DEBUG log, it reports TypeError: Cannot read properties of undefined (reading 'getCharacteristic').
The system is logging onto the pulse portal and reading the sensors and reporting their changes in status. However, when it tries to list all of the sensors and add them, they are all listed as (sensor-0); this was not the case before as the plugin used the system ID as the sensor number.
Steps to reproduce the bug:
Expected behavior:
So far I have reinstalled the plugin, and created a new user in the pulse system. I have also uninstalled the bridge and created a new one. The new device has the same name and system ID as it did before however it's "Reporting type" might be different within pulse (I don't know what that is).
The Apple device you are using:
Homebridge information:
Logs related to this bug:
The text was updated successfully, but these errors were encountered: