S505d invalid authentication #888
Comments
|
This error is usually because the credentials you supplied are invalid. Have you provisioned this device? |
|
I am getting this same error when trying to setup a new device, I think this might have to do with having 2fa enabled on my Tapo Account? Does this integration support having 2FA on the account you login with? |
|
if you supply creds you can get a bit further: |
|
@steveredden, this might be a separate issue, but
tells us that the device was provisioned using matter, which could be the culprit for the error. If you add Also, can you control the device using the mobile app? @Maeur1 is the error the same as in the original issue description? @sykhew do you have more information / did you get it working? If yes, please consider contributing a fixture file like described here: https://python-kasa.readthedocs.io/en/latest/contribute.html#contributing-fixture-files |
|
yes, this dimmer switch was configured via matter first (home assistant as the controller). It is also controllable via the app - I may have had to enable additional pairing to do so (but i don't remember). it can fixture S505D(US)_1.0_1.1.0.json |
|
Looks like it's (almost) working, thanks for the fixture file! So the culprit is this (ping @sdb9696):
Looks like there are a couple of cases with error You could try to let the device to connect to the NTP server for synchronization (port 123/udp), or set the time manually using something like |
Merged
rytilahti
added a commit
that referenced
this issue
Jun 3, 2024
By courtesy of @steveredden: #888 (comment)
So the fixture file https://github.com/python-kasa/python-kasa/pull/947/files appears have the preset rules. @rytilahti do you know why the error was being raised? Was it fixed by the time sync? |
|
Hmm, maybe the dump_devinfo performs a different query, as those in the attached logs are erroring out with params error, and after seeing the time error I made an assumption that it could be the root cause. |
|
I was able to get diff --git a/kasa/smart/modules/lightpreset.py b/kasa/smart/modules/lightpreset.py
index 8e5cae2..898c3f3 100644
--- a/kasa/smart/modules/lightpreset.py
+++ b/kasa/smart/modules/lightpreset.py
@@ -140,7 +140,7 @@ class LightPreset(SmartModule, LightPresetInterface):
"""Query to execute during the update cycle."""
if self._state_in_sysinfo: # Child lights can have states in the child info
return {}
- return {self.QUERY_GETTER_NAME: None}
+ return {self.QUERY_GETTER_NAME: {}}
async def _check_supported(self):
"""Additional check to see if the module is supported by the device.
diff --git a/kasa/smart/modules/lighttransition.py b/kasa/smart/modules/lighttransition.py
index 29a4bb0..ca0eca8 100644
--- a/kasa/smart/modules/lighttransition.py
+++ b/kasa/smart/modules/lighttransition.py
@@ -230,7 +230,7 @@ class LightTransition(SmartModule):
if self._state_in_sysinfo:
return {}
else:
- return {self.QUERY_GETTER_NAME: None}
+ return {self.QUERY_GETTER_NAME: {}}
async def _check_supported(self):
"""Additional check to see if the module is supported by the device.""" |
|
@pierlon would you mind creating a PR? Changing this does not seem to affect my devices. |
|
Hi, could you test your devices with this PR #1036 and see if it fixes the issue? |
|
This is now fixed in master and released in 0.7.0.3 (release) Thanks @pierlon for the tip about the |
|
Thanks for fixing this @sdb9696! Tested and it works perfectly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hardware version 1.0 firmware 1.1.0 build 231024
Authenticating device results in following error
Invalid authentication: Unable to complete handshake: 192.168.x.x: TRANSPORT_UNKNOWN_CREDENTIALS_ERROR(1003)
The text was updated successfully, but these errors were encountered: