bwitting / homebridge-ttlock

Homebridge plugin for the TTLock Platform
Apache License 2.0
13 stars 5 forks source link

Anyone having issues using the created user in the TTLock mobile app? #9

Open fmp777 opened 1 year ago

fmp777 commented 1 year ago
  1. Created dev account
  2. Created user account using API
  3. Got resulting username
  4. Load up TTLock app on IOS
  5. put in the username from step 3
  6. put in password as provided via md5 in step 2
  7. app complains invalid user/pass

troubleshooting...

  1. but everything works in homekit
  2. Toying with the TTLock API directly, can pull lock list, gateway list, all good
  3. Used API to reset the password to something smaller/simpler thinking maybe the app had issues with length or some characters, but no go
  4. tried to use the md5 pass for just as a sanity check, no go
  5. tried the original username before the API prepended it with some characters, but no go

SIDE NOTE I would suggest better instructions for when a person has already setup an account with their locks. There's a Transfer option in the app allowing you to send your locks/gateways to the new account username. Worked for me. API Docs: https://euopen.ttlock.com/doc/api/v3/lock/transfer

bwitting commented 1 year ago

Thanks @fmp777 - didn't realize there was a way to transfer a user. Want to help write the documentation that?

brandifarmer commented 11 months ago

I am having a similar issue when creating a new user. Can someone help? This was my first error message curl: (3) bad range in URL position 53: So I added -g and now I am getting this: {"errcode":10001,"errmsg":"invalid client","description":"无效的client,client_id或client_secret错误"} I'm so lost

fmp777 commented 11 months ago

@bwitting Sorry didn't notice your request until now, and have already gotten rid of all TTLOCK devices, more trouble than they were worth. TUYA seems to be a bit more together, but its a challenge because of the general poor quality of all the devices.

@brandifarmer That error says your user is invalid, same issue I ran into. Maybe try reading the docs link I provided above to see if you are facing same issue of locks being in one username while your api setup using a different. You may need to tarnsfer like I did... which did end up "working" for me, but this package had issues causing homebridge to hang so was generally unreliable anyway. I ended up replacing locks with Homekit compatible TUYA bridge & locks, skipping the homebridge effort altogether.