mitchjs

there is no rolling codes what so ever in V1 wire connections, the protocol is single byte send / rx i guess they felt no need to secure a wire......

hopefully the code work i did for the homekit sec+1.0 doesnt have this problem i have a wallplate, and funny enough had a power outage this morning, and when it...

but oh yes... we could certainly make it an option, how it works, the code listens for traffic (polling or bootup of the wall panel) and that's how it knows...

@emlynmac you are using ESPHOME version, no? i can share with you the firmware.bin (or you can prob get the pending PR) and build and try my version of sec+1.0...

i left it unpowered for 1hr+ and plugged it all back in, and it just works no issues with my 889LM when powering up i wanted to capture logs, but...

i have to collect the from boot to fail.. (but keep in mind, it connects perfectly everytime to my iphone ios13) its just this older BLE 4.0 device the log...

its like the android doesnt respond to the request, and nimble doesnt time out and move on using this demo: https://github.com/espressif/esp-idf/tree/master/examples/bluetooth/nimble/bleprph when DEBUG LOG level is on... it works MOST...

Yes hang is it sits there long time... then it does the disconnect

no go... i hacked that change in... in nimble 1.3 the did a lot of nice refactoring... hopefully ESP-IDF version gets updated

well keep in mind it works sometimes... its for sure an issue with android 5 i just purchased an samsung tab A 8 (2019 model) it runs android 9 BLE5.0...