oyooyo / keyble-mqtt Goto Github PK

Hello,

Thank you for this nice piece of code.
Could you please give one example, how a command should be published?
That would be helpful.
Thanks.
Dieter

As suggested by @mccoy88f, the documentation should contain a section that explains how to automatically start keyble-mqtt on boot.

Hey oyooyo,
I was already using your previous implementation on a raspberry pi and now switched to the mqtt implementation.
Great job - really like it and it's one of the most useful things in my smarthome.

Unfortunately, sometimes the issued command gets send out to the broker but the lock doesn’t move. There seems to be no error handling feedback back to the broker or am I missing something? Would be quite useful so we could implement a retry mechanism.
Maybe even some kind of configuration within the keyble-mqtt client allowing to set the number of retries if the issued command times out or issues an error? Would be very handy!

Thanks a lot for restarting the development and implementing new features.

Using mqtt is possible to integrate in Home Assistant.
As i read on your page (keyble, keyble-mqtt, and keyble-nodered) you think to create add-on or something else to integrate in home assistant?
Also il will be possible to use RPi4 bluetooth or i esphome and a project for using esp32 bluetooth?
Thanks a lot execelent work
Antonello (from Italy)

Issue: The current implementation of keyble-mqtt does not support the -adt 0 option available in keyble-sendcommand. This option allows for a persistent connection to the smart lock, reducing the command execution delay from 5-10 seconds to approximately 1-1.5 seconds.

Steps to Reproduce:

1. Install keyble and keyble-mqtt using the standard installation process.
2. Send a command to the smart lock via keyble-sendcommand --command open.
3. Observe the delay before the smart lock executes the command.

Expected Result: The command is executed with minimal delay.

Actual Result: There is a delay of 5-10 seconds before the command is executed.

Proposed Solution: Implement the -adt 0 option in keyble-mqtt to allow for a persistent connection to the smart lock. This would reduce the command execution delay, improving user experience.

Potential Implications: A persistent connection may prevent other devices from connecting to the smart lock and could potentially increase battery usage. However, the benefits of reduced delay may outweigh these potential downsides for many users.

Request: Please consider adding support for the -adt 0 option in keyble-mqtt.

I would be happy to assist with the implementation if provided with the right approach.