-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
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
Problem with user names containing spaces in Synology DSM #87457
Comments
Hey there @hacf-fr, @Quentame, @mib1185, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) synology_dsm documentation |
Additional information: I have 2 LAN ports of my Synology NAS in use, but they are bonded to the same IP address. |
@XalaTheShepard: I think you made a type 2022.2 should be 2023.2. For me this issue also started after upgrading from 2023.1.7 -> 2023.2. After boot the integration synology_dsm was logout. If I try to login again it failed with the same error you have 'Invalid credentials'. I din't change anything on my Synology, only upgrade docker Home Assistant to 2023.2. Also running the latest version of DSM 6.2 with 2FA and the user is admin. |
please update to 2023.2.2 and test again |
I did this 1 hour ago, same result... |
ok, than please enable debug logging, restart HA and provide the home-assistant.log logger:
default: info
logs:
homeassistant.components.synology_dsm: debug
synology_dsm: debug Further if possible please download and provide the diagnostics data for this integration. Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub. |
Here you are: |
@XalaTheShepard does your username really contains spaces "Home Assistant VM" ? |
FYI: My username also have spaces |
is it possible to downgrade HA to 2023.1.7 and provide the logs again? Would need them to compare the differences in API calls |
Dear mib1185, I confirm my username has spaces. This was no issue in previous HA Core versions. |
Here you are: The log starts when I add the integration and login. After login I type the 2FA code and everything works fine. |
I have the same issue with the latest version of Home Assistant. Workaround: I create a new admin account just for home assistant with 2FA enabled, without spaces in username. It is working with 2023.2.2 |
I can confirm, its a user name spaces issue. Change the user name without spaces and it works! |
|
Thank you mib1185 for the quick response and solution on your Sunday off. Really appreciated. |
The problem
After upgrading from HA Core 2023.1.7 to 2022.2.0 or above I get the following error message for my Synology DSM integration:
{'api': 'SYNO.API.Auth', 'code': 400, 'reason': 'Invalid credentials', 'details': 'Invalid password or not admin account: Home Assistant VM'}
12:42:08 PM – (ERROR) Synology DSM
Reauthenticating the integration is impossible.
When deleting the integration, I am unable to add it again.
However, downgrading again to HA Core 2023.1.7 solves the issue.
Please note that the credentials are correct and that Home Assistant VM is an admin account.
This account has never caused issues before.
Could you please inform me if I am doing something wrong or how I can solve the issue?
I am running the latest version of DSM 6.2 with 2FA.
Thanks in advance.
Kind regards,
Robin
What version of Home Assistant Core has the issue?
2023.2.0 and above
What was the last working version of Home Assistant Core?
2023.1.7
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Synology DSM
Link to integration documentation on our website
https://www.home-assistant.io/integrations/synology_dsm/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: