Can't get available token for this device #219
Comments
|
你的debug log，刚好把你所有设备的具体型号信息都给删除了.....可以把自己的账号信息处理一下即可(下一个版本会自动强行处理)，所以这样就有点失去了debug log的意义，后面都是报错的信息了 所以具体是美的哪个系列的空调？具体型号等信息呢？是近期新买的？之前也从未成功添加过？ |
Your debug log has just deleted the specific model information of all your devices... The meaning of the debug log has been lost, and all the subsequent information is error messages. So which series of Midea air conditioners is it specifically? What about the specific model and other information? Bought new recently? Never added successfully before? |
|
Had same issue today, managed to solve it by turning off the AC through the nethome plus app after which it got past that point, kept getting some errors in the next steps, but got through all of them by just retrying the steps. |
抱歉 美的省电星系列，去年购买 型号：KFR-35G/BDN8Y-DH400(3)A 、KFR-26G/BDN8Y-DH400(3)A、KFR-26G/BDN8Y-DH400(3)A，之前从未在在这个插件添加过，在smart_ac那个添加上一个，其他两个不行 具体log如下： |
thanks, but report with not pass and without debug log is no a useful info for both us and you.... and we should disable you add it with error config and a not working device, if you are using an error config and setting, force add it pass, then report any error bug , it should not a normal case. |
|
@mengxiang2020aa 多谢，从你补充的这部分debug log来看，你的三款AC设备，其中二款的model为22012617，一款为22012615，具体哪个成功，哪个失败，以及设备的其他具体信息，实际上还有更详细的信息，都在 debug log里面，从美居登录以后获取更多来辅助添加设备，以及失败以后的其他尝试，都在 debug log中体现。 当然，有一小部分使用中的错误，可能其中一小段关键错误log就足以解决问题，但是目前添加失败大概率是不行.... |
@mengxiang2020aa Thank you. Judging from the debug log you added, of your three AC devices, two of them have models 22012617 and one is 22012615. Which one succeeds and which one fails, as well as other specific information about the device, are actually There is also more detailed information, all in the debug log. After logging in from Mercure, you can get more information to assist in adding devices, as well as other attempts after failure, all of which are reflected in the debug log. Of course, there are a small number of errors in use, and a small section of the key error log may be enough to solve the problem, but adding a high probability of failure is currently not possible.... |
|
感谢你的帮助 22012615可以添加，但是不能使用。显示不可用，一个设备和一个实体，查看log应该是貌似是使用V2协议
22012617是无法添加 |
Thank you for your help 22012615 can be added, but cannot be used. It shows that it is unavailable, one device and one entity. Looking at the log, it seems that the V2 protocol is used.
22012617 cannot be added |
|
刚刚再次尝试发现一个的新的错误 |
|
@mengxiang2020aa 这压根不是一个错误，这是对所有配置强行做了二次检测，以前的版本压根不检查，所有人都在设备添加不成功时，使劲改各种参数，改完添加成功，感觉自己能用了，各种报bug，实际都是使用的是一个错误的配置，基于错误的配置报bug，如何解？ 所以新版已经禁止使用此类骚操作，必须保证所有设备信息都是符合实际设备的真实准确的配置，保证添加进去的配置都是准确的 |
@mengxiang2020aa This is not a mistake at all. This is a forced secondary check of all configurations. The previous version did not check at all. When the device was unsuccessfully added, everyone tried hard to change various parameters. After the changes were completed, the addition was successful and I felt like I It works, but the various bug reports are actually using an incorrect configuration. How to solve the bug report based on the wrong configuration? Therefore, the new version has banned the use of such frivolous operations. You must ensure that all device information is in line with the true and accurate configuration of the actual device, and ensure that the added configurations are accurate. |
So what should I do? 0 reset once? |
|
你好，删除之后重新添加之后，依然加不上，完整日志见附件 |
Hello, after deleting and re-adding, it still cannot be added. Please see the attachment for the complete log. |
|
Link is broken |
|
Thanks for letting me know，the link has been put back up |
Something not supported in your log. Which ap are you using ? |
|
@chemelli74 this is meiju cloud from user input, get_device_info should ok but get_key not available for meiju cloud as no route(no get token api). some device still can use phase 2 to got a passed token and works well, but some device can't use msmart to got a passed token now. |
|
How do I retrieve keys from Meijucloud? Another API version was released? Can you @wuwentao sniff the protocol? |
|
0.5.4 should fix your issue. |
HA版本
2024.7.1
集成版本
2024.06.2
设备类型及型号
Air Conditioner 22012615 (0)
使用的App
美的美居
问题详细描述
使用0.5.0版本，无法添加美的空调设备，提示“Can't get available token for this device”，日志有显示获取到token，手动配置依然不行，日志如下：
2024-07-09 22:40:55.316 DEBUG (MainThread) [midealocal.cloud] Midea cloud API url: https://mp-prod.smartmidea.net/mas/v5/app/proxy?alias=/v1/iot/secure/getToken, data: {'udpid': '4a18a602ae874fd7fc7e7df9febbd8d2', 'reqId': '7b95d8bd94a9459934ff2fec151fe456', 'stamp': '20240709144055'}, response: b'{"msg":"\xe8\xb0\x83\xe7\x94\xa8\xe4\xb8\x9a\xe5\x8a\xa1\xe7\xb3\xbb\xe7\xbb\x9f\xe5\xbc\x82\xe5\xb8\xb8(\xe8\xae\xbf\xe9\x97\xae\xe5\x9c\xb0\xe5\x9d\x80\xe4\xb8\x8d\xe5\xad\x98\xe5\x9c\xa8) [no Route matched with those values]","code":40404}'
2024-07-09 22:40:55.316 DEBUG (MainThread) [midealocal.cloud] Response from get_keys() for appliance_id 210006728402011 with method 1: None
2024-07-09 22:40:55.353 DEBUG (MainThread) [midealocal.cloud] Midea cloud API url: https://mp-prod.smartmidea.net/mas/v5/app/proxy?alias=/v1/iot/secure/getToken, data: {'udpid': 'dc2fdf5ddb6dba82169610d941acdfb0', 'reqId': '5471fcf700918369fb745985df04f0fa', 'stamp': '20240709144055'}, response: b'{"msg":"\xe8\xb0\x83\xe7\x94\xa8\xe4\xb8\x9a\xe5\x8a\xa1\xe7\xb3\xbb\xe7\xbb\x9f\xe5\xbc\x82\xe5\xb8\xb8(\xe8\xae\xbf\xe9\x97\xae\xe5\x9c\xb0\xe5\x9d\x80\xe4\xb8\x8d\xe5\xad\x98\xe5\x9c\xa8) [no Route matched with those values]","code":40404}'
2024-07-09 22:40:55.354 DEBUG (MainThread) [midealocal.cloud] Response from get_keys() for appliance_id 210006728402011 with method 2: None
2024-07-09 22:40:55.354 DEBUG (MainThread) [midealocal.device] [210006728402011] Connecting to 192.168.50.57:6444
2024-07-09 22:40:55.483 DEBUG (MainThread) [midealocal.device] [210006728402011] Connected
2024-07-09 22:40:55.484 DEBUG (MainThread) [midealocal.device] [210006728402011] Handshaking
2024-07-09 22:40:55.543 DEBUG (MainThread) [midealocal.device] [210006728402011] Authentication failed
2024-07-09 22:40:55.543 DEBUG (MainThread) [midealocal.device] [210006728402011] Status update: {'available': False}
2024-07-09 22:40:55.543 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] connect device using method 99 token/key failed
2024-07-09 22:40:55.543 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] Unable to connect device with all the token/key
2024-07-09 22:40:55.544 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] Can't get valid token with input account in 美的美居 server
2024-07-09 22:40:58.301 DEBUG (MainThread) [midealocal.cloud] Midea cloud API url: https://mp-prod.appsmb.com/mas/v5/app/proxy?alias=/v1/multicloud/platform/user/route, data: {'src': '1010', 'format': '2', 'stamp': '20240709144055', 'platformId': '1', 'deviceId': '2625df98eed17b6f', 'reqId': '97190a00b14e042f0b042156788c9db7', 'uid': None, 'clientType': '1', 'appId': '1010', 'userType': '0', 'userName': 'c414e631394b8639@outlook.com'}, response: b'{"msg":"ok","code":0,"data":{"masUrl":"https://mp-prod.appsmb.com/mas/v5/app/proxy?alias=","sseUrl":"https://sse.msmartlife.net","idAdapt":"131329","countryCode":"HK","emsIdAdapt":"132097"}}'
The logs
homeassistant_logs-debug-0709.txt
The text was updated successfully, but these errors were encountered: