Crow Runner Alarm interface using an esp8266 and Home Assistant

Can you post a picture with the alarm panel and this in the same picture with the wiring?

1 Like


Thanks for the help.
This is of course, a temp wiring u til I get it working. Then Will solder all wires neatly.

you should be using D6 for clock and D7 for data (There was a typo in the readme). Currently you are using D5 for clock and D6 for data - your labelling seems wrong.

1 Like

Ha! Amazing! Thank you. It now works! Really appreciate your work on this code as well as the extra help!

I’m glad it works! Enjoy… :wink:

1 Like

Hello all,

I uploaded the code on esp
Added mqtt from hacs and copied the example yaml files under config folder.

When I try to include this yaml files I had an error as platform required , but as I see the platform parameter already in alarm yaml files

I tried to add alarm panel on dashboard and it found the alarm entity while adding the panel but it seems unavailable (esp not connected to crow yet .awaiting for shifters)

I guess second part is about not connecting it yet… but can somebody help me on including the alarm yaml files shared in GitHub…

And is there any screenshots you can share with the panel while running this integration

I am thrilled for having succeeded in doing this project, even if I am not an engineer. Just enthusiasm and determination.

The information shared here and in the github would be sufficient for those familiar with the topic, but to me, it required good doses of googling as I was unfamiliar with several terms.

A big thank you to MadDoctor, (ou doctor maluco) :slight_smile: for having shared his work and for being so supportive to the people here.

If anyone less techy attempts to do it, here is a short guide from the eyes of a non-engineer:

i) buy: 1 Wemos mini D1 (microcontroller with Wifi integrated), a Step dow (device that will allow you to source 12V from Crow board and then reduce it to 5V), bidirectional Logic Level Converter (to allow to run 3.3V and 5V in parallel)

ii) to program the Wemos mini D1 (flash), user Visual Studio Code with PlatformIO extention. Download the zip file of MadDoc from his GitHub and add it to the patformIO. Fix a little glitch (add .toString() - see issue " compile error with arduinoIDE" in the github) and compile. In platformio.ini add your board and COM. in main.cpp, add your wifi/password and mqtt server/password and upload.

iii) for soldering, well… you need to know the basics. I share my diagram here (hand written, sorry).

iv) connection to Crow board: follow the diagram. Ensure you have tunned the step down to output 5V else, things will fry.

1 Like

Just a little correction - the ground of the esp (wemos) should be connected to the groung of the rest of the system.

(and as a side note, I couldn’t be further from being an engineer, workwise! :wink: )

Good catch maddoctor; I had uploaded a preliminary picture of the diagram by mistake. I have now replaced it by the correct one.

And… if you are not an engineer (at least by training), then it is absolutely impressive what you can do.

Thanks to you, I can now control my Crow which I was on the verge of ditching since it was totally analogic to my standards and with this project, suddenly, it became smart too.

Hello Everyone,

I try to deploy this but i think this is no longer supported from HA.
I have some errors on HA config file
property supported feature is not allowed

anyone can help with this ?

I´m currently installing this system, as there was some changes in the HA I put everything on the configuration.yaml (with help from deepseek).
I´m still not there and ì need help, after installing everything I have a problem, the keyboard is messaging “falha com” and MQTT is like this:

Alarm/status Alarme Despoletado                                                 
Alarm/tele {"Uptime":"0D 02:49:42","IP":"192.168.1.275","RSSI":-53}             
Alarm/status Alarme Despoletado                                                 
Alarm/tele {"Uptime":"0D 02:49:52","IP":"192.168.1.275","RSSI":-53}             
Alarm/status Alarme Despoletado                                                 
Alarm/active_zones 1 activo                                                     
Alarm/active_zones 2 activo                                                     
Alarm/active_zones 4 activo                                                     
Alarm/active_zones 5 activo                                                     
Alarm/active_zones 6 activo                                                     
Alarm/active_zones 7 activo                                                     
Alarm/active_zones 1 triggered                                                  
Alarm/active_zones 2 triggered                                                  
Alarm/active_zones 6 triggered                                                  
Alarm/active_zones 7 triggered                                                  
Alarm/active_zones 8 triggered                                                  
Alarm/tele {"Uptime":"0D 02:50:02","IP":"192.168.1.275","RSSI":-54}             
Alarm/status Alarme Despoletado                                                 
Alarm/tele {"Uptime":"0D 02:50:12","IP":"192.168.1.275","RSSI":-52}             
Alarm/status Alarme Despoletado                                                 
Alarm/tele {"Uptime":"0D 02:50:22","IP":"192.168.1.275","RSSI":-52}             
Alarm/status Alarme Despoletado                                                 
Alarm/tele {"Uptime":"0D 02:50:32","IP":"192.168.1.275","RSSI":-53}             
Alarm/status Alarme Despoletado                                                 
Alarm/active_zones 9 activo

on and on and on

Did you disconnected the old keyboard ?
Any idea why this is happening ?

You don’t need or should disconnect the keyboard. Seems like the keyboard isn’t connected, given the message that it displays… Maybe that’s the problem.

Hello Maddoctor

Thank you for the response , I have 2 keypads both with LCD display (one big and the other small) . Deeps seek warned me that I should give the ESP an keypad ID. I bought a TXB0104 for the bi directional level converter (by mistake) do you think that this might be causing this “Alarme desplotado”.
Do you have any info about the length of the hex decimal bit of the messages ? Are they 72 bit ?

Thank you

There are several different lengths.
You don’t use a different ID because the esp is “impersonating” one of the keypads…
Does the keyboard show the same error without the esp?

The com fail actually disappeared when I reopened the alarm panel and screw better screws . But the messages are not correct , see the zones triggered at the same time, maybe it was the other keypads messing around. I read the keypads installation pdf and they have an identifying number , I really don´t want to disconnect the keypads , I’m going to try and add an id for the esp and see what happens.


This is mine

Vs 908.2 , 211.1

Can any you guys please confirm if your runner is 4/8 or 8/16 ? Thank you

Hello , it was the bidirectional level shifter , now i have a BOB-12009 and it is working many thanks Madoc. i dont understand coding but deepseek told me to reformulate the code and not to use Deque , I told him to go away , I´m not going to mess if it´s working.

I’m glad it is working now.

The usage of deque is due to memory constraints of the esp…

Ok I think i understood why it is not possible to check the rf sensors , because ther is no comunication to the keyboard from the bus like the Pir ones. So I thought why not pass another cable to the FW2-RCV-8F and try catch the pulses from th rf sensors. I Really don’t know much about codding and eletronics and even with the help of Chatgpt or deepseek I’m not confortable on doing this alone so is anybody willing to try and help with this ?

My is working but sometimes I realize that the alarm aumomatically shifts to arm…
… any ideas?