Closed Fergie2020 closed 5 months ago
The configuration has been upgraded to accommodate some users having issues. Simply add "options": [],
below the "speed": 1,
line, and you should be all set.
Got it!!!
Thank you so much!
On Jan 27, 2024, at 5:12 PM, Jacky Liang @.***> wrote:
Closed #132 https://github.com/mrjackyliang/homebridge-adt-pulse/issues/132 as completed.
— Reply to this email directly, view it on GitHub https://github.com/mrjackyliang/homebridge-adt-pulse/issues/132#event-11618172285, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVH3TJ7YKUNBEHEUTYEB4LTYQV3T7AVCNFSM6AAAAABCNU2BU2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGYYTQMJXGIZDQNI. You are receiving this because you authored the thread.
No problem!
And make sure that you at least have a "sensors": []
attribute?
And make sure that you at least have a
"sensors": []
attribute?
Yes. If you don't want sensors, you have to set it to an empty array.
Grateful for such timely responses!
Now I'm seeing:
[ADT Pulse] Login attempt has failed. Trying 1 more time ...
{
action: 'LOGIN',
success: false,
info: {
message: '"/myhome/27.0.0-140/access/signin.jsp?e=ns&partner=adt" is not the summary page'
}
}
I know that I have the correct credentials.
Oh perhaps my fingerprint is wrong?
Oh perhaps my fingerprint is wrong?
Most likely the fingerprint became outdated or per @rlippmann's discovery, you cannot have multiple logins of the same fingerprints. If login fails 3 times in a row, the plugin will just stop for 30 minutes to prevent ADT from blocking your IP due to many attempts.
I'm getting "fingerprint too_big
". :confused:
I'm getting "fingerprint
too_big
". 😕
Mmm. this sounds like a bug. Please create a bug report, thanks!
Just an FYI.....I woke up this morning and the plugin wouldn't work again. Checked logs and my json file changed. The "platform": ...... line (second from top) was gone. Had to re-enter the the line and save/restart homebridge to get it back up and running.
Just an FYI.....I woke up this morning and the plugin wouldn't work again. Checked logs and my json file changed. The "platform": ...... line (second from top) was gone. Had to re-enter the the line and save/restart homebridge to get it back up and running.
The plugin doesn't touch the platform key in the config. That's all Homebridge. If it's missing, something wanky going on with the install.
Thanks for the update. Not sure what happened through the night but will keep you posted if anything changes. On Feb 2, 2024, at 3:36 PM, Jacky Liang @.***> wrote:
Just an FYI.....I woke up this morning and the plugin wouldn't work again. Checked logs and my json file changed. The "platform": ...... line (second from top) was gone. Had to re-enter the the line and save/restart homebridge to get it back up and running.
The plugin doesn't touch the platform key in the config. That's all Homebridge. If it's missing, something wanky going on with the install.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Thanks for the update. Not sure what happened through the night but will keep you posted if anything changes. On Feb 2, 2024, at 3:36 PM, Jacky Liang @.***> wrote:
Just an FYI.....I woke up this morning and the plugin wouldn't work again. Checked logs and my json file changed. The "platform": ...... line (second from top) was gone. Had to re-enter the the line and save/restart homebridge to get it back up and running.
The plugin doesn't touch the platform key in the config. That's all Homebridge. If it's missing, something wanky going on with the install.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
If you do suspect something, please file a new bug report, thanks!
Pre-check confirmation
Your email address
ferguson.brian@mac.com
Tell us exactly what happened
I thought I had my plugin all set but I am getting the same message
Plugin version
3.1.0
Homebridge version
1.7.0
Node.js® version
18.19.0
Log output of the "test-api" command
More logs relevant to this bug
Legal Agreements