Andreas Roedl

The driver worked very well a month ago. When I came back from vacation I wanted to switch from the PR driver channel to main (or beta). See my comment(s)...

I'll try again tomorrow. Device firmware: 1.2.7_0011.0080 Hub firmware: 000.053.00019 ST app (Android): 1.8.18.21

Got a full log now. The interesting part: ``` 2024-09-27T22:47:45.440063966Z ERROR Aqara Presence Sensor get_credential : ip = 192.168.1.121, failed to get token, error = wantread 2024-09-27T22:47:45.445295882Z WARN Aqara Presence...

I'm pretty sure now that the very last commit (the whole lunchbox updated to the latest version and more), right before the PR was merged into main broke the driver....

**Thanks, ChatGPT!** The "wantread" error in luasec (a Lua library for SSL/TLS support) typically indicates that a non-blocking operation is expected to read more data from the network (e.g., receiving...

@seojune79 Is there a reason why the FP2 can't be added anymore? Maybe a hidden expiration date for /authcode or the whole REST in firmware version 1.2.7_0011.0080?

Thanks, @seojune79

Not fixed. Another user has the same issue. Read the comments here (conversation between Andreas_Roedl and ewimer2): https://community.smartthings.com/t/aqara-fp2-tested-with-smartthings/270688/136 User has hub firmware 54.x, FP2 firmware 1.2.8x. Keep in mind that...

@seojune79 >If something goes wrong while removing FP2 from the ST app, the device won't be onboarded. >If this happens, removing and onboarding the FP2 in the Aqara home app...

This is from the logcat of the user: ``` 2024-10-16T00:28:57.487769932Z INFO Aqara Presence Sensor 54:EF:44:5B:E4:1F Successfully created TCP connection 2024-10-16T00:29:58.667069064Z ERROR Aqara Presence Sensor get_credential : ip = 192.168.86.52, failed...