Support for WG / MS

[uknn88]

Hello,

I was wondering when smart locks would be supported? Would love these to be in HomeKit and working, I've tried everything with no luck at the moment.

Thanks

[0x5e]

Ok I will add to the todo list

[0x5e]

Hello, thanks for the response, I appreciate it hugely.

So I can assist, please let me know where I can get the debug logs?

Readme is updated, please see Troubleshooting section.
You can do some operations with physal lock, open/close the door, or do some operations in tuya app, and tell me your operation with time, and upload the homebridge log during these operations.

I will try with virtual lock next days, no need to buy me, thanks :)

[uknn88]

Hello, thanks for the reply.

In terms of the debug log on homebridge, I enabled it and don't see any updates where i'm operating the lock manually. I'm currently looking at the Tuya debug log as well however that doesn't give much information unfortunately. Please can you explain where the readme file is on homebridge? I can then find it for you.

In terms of product category, Tuya states that it is 'ms'

The lock is a bluetooth lock which is connected to the mini ble gateway with product code 'wg2' which makes it wifi as such.

[0x5e]

Homebridge: https://github.com/homebridge/homebridge
Please upload the log like this: #14

As it's a bluetooth lock, can it be controlled by tuya app, with ble and wifi both off (only celluar data opened)?

[uknn88]

Thank you for example file, this is simply the normal debug logs on homebridge. However, when I play with the locks (unsupported), nothing shows up in the logs. The only thing it shows regarding the locks is that it recognises it but is unsupported. Any action from physical or app related doesn't show anything.

Yes it can be controlled by Tuya app with bluetooth and wifi off on phone.

This is because Tuya platform is linked with the wifi gateway which is then linked to locks via bluetooth.

[0x5e]

I need normal debug logs too. I'm not sure if you correctly opened the debug mode.
Normal debug log contains your device infomation including functions and status.

[uknn88]

Anywhere that details how to do this?ThanksSent from my iPhoneOn 26 Oct 2022, at 14:49, gaosen ***@***.***> wrote: I need normal debug logs too. I'm not sure if you correctly opened the debug mode. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[0x5e]

Before use, please uninstall homebridge-tuya-platform first. They can't run together. (But the config is compatible, no need to delete.)

For Homebridge Web UI Users

Go to plugin page, search @0x5e/homebridge-tuya-platform and install.

For Homebridge Command Line Users

npm install @0x5e/homebridge-tuya-platform

[uknn88]

I have the correct plugin installed, so where do I find the debug log?ThanksSent from my iPhoneOn 26 Oct 2022, at 18:35, gaosen ***@***.***> wrote: Before use, please uninstall homebridge-tuya-platform first. They can't run together. (But the config is compatible, no need to delete.) For Homebridge Web UI Users Go to plugin page, search @0x5e/homebridge-tuya-platform and install. For Homebridge Command Line Users npm install @0x5e/homebridge-tuya-platform —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[uknn88]

[uknn88]

log.txt

This is what shows on start up. Any action afterwards does not show anything in debug log.

[0x5e]

Any logs before this? During the launch, did the plugin success log your tuya account and start the mqtt connection? there should be more logs before this.
Before uploading the log, please remove the sensitive data such as username password.

[uknn88]

homebridge.log (1).txt

Hi, please see attached.

[0x5e]

Thanks for providing the log. I will try it next week.

The following is your lock device's status and function, I have read the tuya docs but something still not very clearly about the meaning of unlock_xxx's value. In docs it has range from 0~999. If you have any idea about it, please tell me.
And bluetooth_unlock's value is base64 encoded, don't know what's the meaning too...

By the way, when you lock/unlock/open/close the door physically, can you see any changes notifications on Tuya App's device control page of this lock?

status:

[{
	"code": "bluetooth_unlock",
	"value": "AQE="
}, {
	"code": "residual_electricity",
	"value": 89
}, {
	"code": "unlock_fingerprint",
	"value": 0
}, {
	"code": "unlock_password",
	"value": 0
}, {
	"code": "unlock_dynamic",
	"value": 0
}, {
	"code": "unlock_ble",
	"value": 1
}, {
	"code": "alarm_lock",
	"value": "wrong_password"
}, {
	"code": "hijack",
	"value": false
}, {
	"code": "beep_volume",
	"value": "mute"
}, {
	"code": "lock_motor_state",
	"value": false
}, {
	"code": "unlock_temporary",
	"value": 0
}]

functions:

[{
	"code": "beep_volume",
	"desc": "beep volume",
	"name": "beep volume",
	"type": "Enum",
	"values": "{\"range\":[\"mute\",\"normal\"]}"
}]

[0x5e]

@uknn88 hello, are you still there? If you can record the mqtt message when unlock, lock, open the door, close for examples, I can submit a beta version and you can have a try.

[paesvitor]

AFAIK these values are the id's from the users registered on the smart locker. If you are user with ID 101 and unlocks the door using fingerprint unlock_fingerprint value will be 101 same as the user ID. And this value will remain indeterminately until someone else unlocks, and this value will be overwritten. I tried to clear these values using some API calls but with no success. The thing is, if we want to have the information on homekit wheater the door has unlocked or not, we have to be able to set the unlock values to zero again, so we know the current state, some of these lockers do not have lock_motor_state info, but i still didn't figured out a solution for this yet.

[0x5e]

AFAIK these values are the id's from the users registered on the smart locker. If you are user with ID 101 and unlocks the door using fingerprint unlock_fingerprint value will be 101 same as the user ID. And this value will remain indeterminately until someone else unlocks, and this value will be overwritten. I tried to clear these values using some API calls but with no success. The thing is, if we want to have the information on homekit wheater the door has unlocked or not, we have to be able to set the unlock values to zero again, so we know the current state, some of these lockers do not have lock_motor_state info, but i still didn't figured out a solution for this yet.

@pfgimutao have the lock support, using lock api, please have a test after I submit a version:
#120

[uknn88]

Hey bro, I’ve tried but it doesn’t record any mqtt message when I do those operations?ThanksSent from my iPhoneOn 5 Nov 2022, at 11:50, gaosen ***@***.***> wrote: @uknn88 hello, are you still there? If you can record the mqtt message when unlock, lock, open the door, close for examples, I can submit a beta version and you can have a try. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[0x5e]

Have you tried web debugging on tuya platform? Can it controls your lock?

[uknn88]

I’ve checked and it don’t seem to be able to. Only though Tuya smart life app.ThanksSent from my iPhoneOn 5 Nov 2022, at 14:07, gaosen ***@***.***> wrote: Have you tried web debugging on tuya platform? Can it controls your lock? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[0x5e]

I think your device may have non-standard instrument set so are not able to supported.
#44 (comment)

[uknn88]

Oh that’s a shame ☹️ how come it works on app and not web?Sent from my iPhoneOn 7 Nov 2022, at 12:33, gaosen ***@***.***> wrote: I think your device may have non-standard instrument set so are not able to supported. #44 (comment) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[0x5e]

I don't like this decision either. The API just hide them, didn't consider how to support old non-standard devices.

[uknn88]

Any way of getting this raised with Tuya? Sent from my iPhoneOn 7 Nov 2022, at 13:53, gaosen ***@***.***> wrote: I don't like this decision either. The API just hide them, didn't consider how to support old non-standard devices. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[0x5e]

Yes I've wrote in the #44 (comment)
there's one way but not too much hope, need to contact device's manufactor, let manufactor submit the request to tuya, to expose the non-standard instruction set

[uknn88]

Thank you for raising it 😊 Sent from my iPhoneOn 7 Nov 2022, at 15:17, gaosen ***@***.***> wrote: Yes I've wrote in the #44 (comment) there's one way but not too much hope, need to contact device's manufactor, let manufactor submit the request to tuya, to expose the non-standard instruction set —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[0x5e]

Update: now tuya platform support switching control mode, so support your device maybe possible again. Please see #111.

[uknn88]

Will test once it’s released 😊 thanks buddySent from my iPhoneOn 24 Feb 2023, at 06:16, gaosen ***@***.***> wrote: AFAIK these values are the id's from the users registered on the smart locker. If you are user with ID 101 and unlocks the door using fingerprint unlock_fingerprint value will be 101 same as the user ID. And this value will remain indeterminately until someone else unlocks, and this value will be overwritten. I tried to clear these values using some API calls but with no success. The thing is, if we want to have the information on homekit wheater the door has unlocked or not, we have to be able to set the unlock values to zero again, so we know the current state, some of these lockers do not have lock_motor_state info, but i still didn't figured out a solution for this yet. @pfgimutao have the lock support, using lock api, please have a test after I submit a version: #120 —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>