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
Motionblinds AccessToken error with HA core 2024.4.4 integration: motion_blinds #116367
Comments
Hey there @starkillerOG, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) motion_blinds documentation |
You can try power cycling the bridge. Please note that “-” characters need to be included in the key when providing it to Home Assistant. The key needs to be similar to Please check again from the app if you copied the key correctly, maybe a mistake like I (i) vs l (L). |
Hi Starkiller,
Thanks for the quick answer.
I have tried to restart my bridge several times, but the key I
received from the app never worked:
[image: image.png]
[image: image.png]
I have even tried to make another MotionBlinds registration but that API
either didn't work.
If I understand correctly, the MotionBlinds app only needs a registration,
I don't need to connect to my Smart Bridge, just need to go Settings/About
MMotion, click the text 5x times and then use the generated API key in HA
Motionblinds integration. It is 100% sure that something is wrong with the
API key, since if I just enter random characters, I have the same
AccessToken error, but the status of the shutters are working perfectly.
Maybe I'm using an incorrect version of MotionBlinds (1.1.8) ?
…On Mon, Apr 29, 2024 at 3:04 PM starkillerOG ***@***.***> wrote:
You can try power cycling the bridge.
But since it has never worked for you, it is more likely that the key you
put in is wrong.
Please note that “-” characters need to be included in the key when
providing it to Home Assistant. The key needs to be similar to
12ab345c-d67e-8f
Please check again from the app if you copied the key correctly, maybe a
mistake like I (i) vs l (L).
—
Reply to this email directly, view it on GitHub
<#116367 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AW536EYQBDOYNCOVK6QR64DY7ZAO3AVCNFSM6AAAAABG5ZFAVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBSGY3TMNBXGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Üdvözlettel:
Polgár András
|
Is there another way to extract my Motionblinds integration AccessToken? |
The problem
Hello,
In mot able to control my shutters in the HA Motionblinds integration, however I can see the status and the state of the shutters perfectly, like I only have read access to the system in Home Assistant. I can control the shutters from Google Home and from the "officical" SmartHome Bridge Connector application (FW A1.0.9_B0.2.0 FW).
It was never working.
I tried to readd the device to the Wifi, and to the Motionblinds integration with the TokenCode from MotionBlinds app, but still not able to control from HA, I keep seeing the following:
Logger: motionblinds.motion_blinds
Source: components/motion_blinds/coordinator.py:67
First occurred: 9:26:46 AM (10 occurrences)
Last logged: 9:27:00 AM
Received actionResult: 'AccessToken error', when sending message: '{'msgType': 'WriteDevice', 'mac': 'b0b21c7655280006', 'deviceType': '10000000', 'AccessToken': 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'msgID': '20240429072654057', 'data': {'operation': 5}}', got response: '{'msgType': 'WriteDeviceAck', 'mac': 'b0b21c7655280006', 'deviceType': '10000000', 'msgID': '20240429092653675', 'token': 'xxxxxxxxxxxxxxxx', 'actionResult': 'AccessToken error'}'
Received actionResult: 'AccessToken error', when sending message: '{'msgType': 'WriteDevice', 'mac': 'b0b21c7655280007', 'deviceType': '10000000', 'AccessToken': 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'msgID': '20240429072655681', 'data': {'operation': 5}}', got response: '{'msgType': 'WriteDeviceAck', 'mac': 'b0b21c7655280007', 'deviceType': '10000000', 'msgID': '20240429092655211', 'token': 'xxxxxxxxxxxxxxxx', 'actionResult': 'AccessToken error'}'
Received actionResult: 'AccessToken error', when sending message: '{'msgType': 'WriteDevice', 'mac': 'b0b21c7655280008', 'deviceType': '10000000', 'AccessToken': 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'msgID': '20240429072657215', 'data': {'operation': 5}}', got response: '{'msgType': 'WriteDeviceAck', 'mac': 'b0b21c7655280008', 'deviceType': '10000000', 'msgID': '20240429092656748', 'token': 'xxxxxxxxxxxxxxxx', 'actionResult': 'AccessToken error'}'
Received actionResult: 'AccessToken error', when sending message: '{'msgType': 'WriteDevice', 'mac': 'b0b21c7655280009', 'deviceType': '10000000', 'AccessToken': 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'msgID': '20240429072658772', 'data': {'operation': 5}}', got response: '{'msgType': 'WriteDeviceAck', 'mac': 'b0b21c7655280009', 'deviceType': '10000000', 'msgID': '20240429092658386', 'token': 'xxxxxxxxxxxxxxxx', 'actionResult': 'AccessToken error'}'
Received actionResult: 'AccessToken error', when sending message: '{'msgType': 'WriteDevice', 'mac': 'b0b21c765528000a', 'deviceType': '10000000', 'AccessToken': 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'msgID': '20240429072700391', 'data': {'operation': 5}}', got response: '{'msgType': 'WriteDeviceAck', 'mac': 'b0b21c765528000a', 'deviceType': '10000000', 'msgID': '20240429092659924', 'token': 'xxxxxxxxxxxxxxxx', 'actionResult': 'AccessToken error'}'
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
What version of Home Assistant Core has the issue?
core-2024.4.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Motionblinds
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: