Margriko / Paradox-ESPHome

Import states to Home Assistant from Paradox alarm system by connecting esp8266 to keypad green-yellow (COMBUS) interface.
21 stars 6 forks source link

NodeMCU blinks fast when CLK pin is connected. #3

Open lpperras opened 1 year ago

lpperras commented 1 year ago

Hi there, I am trying to connect a NodeMCU running the code on my Paradox alarm system. I followed the diagram (As far as I know) and as soon as I connect the CLK (Yellow wire) to the pin, the blue light starts flashing quickly and then it disconnect. It won't event connect is restarted with the pin connected, but if I start it without connecting the pin just to test, I see it, but then as soon as the pin gets connected it crashes.

I am not that familiar with that type of development so I might be missing something stupid as to how I should troubleshoot this. When looking at references you used for your development, I saw that they were using 33k ohm resistor instead of 15k. I tried and has the same problem. How could I troubleshoot the startup of the NodeMCU?

Is this a behavior you have seen while developing on your side? I tried changing pin and had the same problem with D1, D2 and D8. If I don't call 'attachInterrupt' on the pin it doesn't fail, but as long as I change the code to point to that pin, and connect the CLK it fails.

Thanks for any support you can provide!

n3on4s commented 1 year ago

Have you managet to resolve it @lpperras ? I have the same problem now.

lpperras commented 1 year ago

The problem seems to be when decoding what was read from the pins. If you comment out the decode part, it no longer crashes. I debugged briefly and saw that the binary that was returned is not complete very often. The code is made to have to read in chunk of 8 bits, and sometimes my alarm system would return '00000' for example. It might be that the 40ms delay isn't proper for my alarm system, I'll need to do more testing. Let me know if this is useful and if you have a similar issue.

n3on4s commented 1 year ago

hmm i will try to do same today. If decodes fails atleast it should be possilbe to handle this error and/or adjust system accordingly.

eqasxar commented 4 months ago

has anyone had any luck scanning it?