Ideas & Suggestions

[rednblkx]

You can share your ideas and suggestions here for the project here.

[jk2g]

Bom primeiramente parabens pelo projeto!!!
gostaria que se possivel add possibilidade de adicionar um sensor para status de aberto e fechado . um sensor magnetico add a uma gpio.obrigado desde ja .

[jk2g]

digo sobre o sensor pois para o fechamento automatico somente criando automaçôes .com a possibilidade de adicionar um sensor o status mudaria automatico quando sensor ABERTO/FECHADO.sem uso de automaçâo.

[rhamblen]

OK so I've got it all working.
Im using not red to unlock the door. I was using a web ui for the lock but it was slow, so I've switched to MQTT commands and it is much quick, ie instantaneous!

Suggestion...
in the interface we can already send MQTT commands, but could we also set a custom topic and payload which is sent in addition. Something which is sent when the door unlock is issued.
This would be awesome as we then dont need a MIM line nodered to unlock the door.

[rednblkx]

There already is MQTT Custom States
They are tied to the internal lock states and only limited to numbers so it’s not complete custom payloads.
It was originally implemented in order to publish data directly to a Lock that has an MQTT API like Nuki’s.
The wiki needs a little work, let me know if you have any questions.

[konradhuebner]

@rednblkx there is another really nice project: https://github.com/esprfid/esp-rfid and I was wondering if a best-of-both would make sense:

• add user management for standard RFID to this project so that not only HomeKey works, but also the cheap tags. My kids don't have iPhones yet ;)
• maybe make use of some of their web-ui and infrastructure for this
• fully emulate a lock, and not only the reading. I want to integrate this into my garage door, and just need a 1s activation of the relais, and then I would be good again.

Ultimately, one could even add a fingerprint reader, for that there is also a project: https://github.com/frickelzeugs/FingerprintDoorbell

Would be happy to hear your thoughts :)

[electric-m]

I appreciate all of you ideas, but that seems like a huge change to the general project.

I do User management and the opening closing of the lock in nodered.

That way, so have Homekeys, Traditional Tags via NodeRED, and the correct animation and status of the locks also via NodeRED.

ScreenRecording_09-21-2024.09-55-52_1.mp4

[rednblkx]

Hi @konradhuebner
Appreciate your suggestions but I have to say that some of them go beyond the scope of this project unfortunately.
The main focus for this project is and will be homekey, the basic scanning of tags was included because it felt silly not to, since it was already halfway there. Also, the addition of all this extra rfid features would make the firmware size go overboard and would prompt people to search for a board with 8MB or even 16MB. I realise i should’ve been more clear in the description that the purpose of this project is to provide homekey functionality, anything extra are only QoL additions.

However, not all hope is lost, i actually developed a HomeKit component for ESPHome and a HomeKey integration for it that can be found here, so people can have this choice of customisation and expansion.

Additionally, I am actually planning on adding some simple uid tag whitelisting so you don’t have to rely on external validation.
Regarding your relay suggestion, you can use the success event, timeout can’t be changed as there is a bug but the default is 1s, however this won’t sync with the state in HomeKit for that I added GPIO actions but misses momentary state which will be added in the next version(present right now in the dev branch).

Again, thank you for the suggestions, let me know if you have any questions and you can also join the discord server for a chat if you want.