-
Notifications
You must be signed in to change notification settings - Fork 34
VMB4000: Settings "base.mode" No Longer Seems to Work #185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I have removed and re-added all devices, including the base station. Pyaarlo still shows the base station as mode 'unknown' |
Did anything change on the Arlo account? Does it still have admin access? Did they move it to the new interface? Can you post the config you are passing to the |
The accounts have not changed. All have admin access. The accounts were all moved to the "new" interface. |
If you are on the new interface you have to use the locations interface.
Arlo had removed base station access
…On Sun, Apr 6, 2025, 15:05 Paul Curtis ***@***.***> wrote:
arlo = pyaarlo.PyArlo(
verbose_debug=True,
save_state=True,
save_session=True,
synchronous_mode=True,
save_media_to="/tmp",
storage_dir="/tmp/logs/",
user_agent="linux",
backend="sse",
refresh_devices_every=1,
username="bob",
password="carol",
tfa_source="imap",
tfa_type="email",
tfa_host="imap.gmail.com",
tfa_username="ted",
tfa_password="alice",
)
The accounts have not changed. All have admin access. The accounts were
all moved to the "new" interface.
Pyaarlo "pip" installed from git+https://github.com/twrecked/pyaarlo
—
Reply to this email directly, view it on GitHub
<#185 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALHJU6UTFRK5HTY5YY4B7Q32YF3F7AVCNFSM6AAAAAB2CSAMQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBRGU3TIMRXGM>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
[image: pfcurtis]*pfcurtis* left a comment (twrecked/pyaarlo#185)
<#185 (comment)>
arlo = pyaarlo.PyArlo(
verbose_debug=True,
save_state=True,
save_session=True,
synchronous_mode=True,
save_media_to="/tmp",
storage_dir="/tmp/logs/",
user_agent="linux",
backend="sse",
refresh_devices_every=1,
username="bob",
password="carol",
tfa_source="imap",
tfa_type="email",
tfa_host="imap.gmail.com",
tfa_username="ted",
tfa_password="alice",
)
The accounts have not changed. All have admin access. The accounts were
all moved to the "new" interface.
Pyaarlo "pip" installed from git+https://github.com/twrecked/pyaarlo
—
Reply to this email directly, view it on GitHub
<#185 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALHJU6UTFRK5HTY5YY4B7Q32YF3F7AVCNFSM6AAAAAB2CSAMQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBRGU3TIMRXGM>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
I will look at the new code today. Thank you for the update. (might be a good note for the README) |
Changed the logic code to use the "location" API instead of the older "basestation" API. Everything is again working as expected. |
pyaarlo 0.8.0.18
python 3.12.9
Very recently (< 1 week), the pyaarlo instance stopped receiving base station events. For example, when using the app, setting 'Arm Home' or 'Arm Away' does not get the equivalent events in the pyaarlo code. And the reverse it also true: executing
base.mode = 'armed'
does not change the status of the system or in the app.I am capturing all attribute changes in the code, any changes are logged. On startup, the pyaarlo library shows the existence of the base station, but its mode is "unknown". (
base: name=Base Station,device_id=4R057B7BAA708,mode=unknown
) The base station has been rebooted. All the devices connected to that base station work as expected.Other than the addition of the 'home' mode, I don't see any changes that would cause this to occur. I am using IMAP login (no problems ... the occasional "cloudflare" error). The problem initially showed before I upgraded the library from 0.8.0.12 to 0.8.0.18.
The text was updated successfully, but these errors were encountered: