Replies: 2 comments 2 replies
-
|
It sounds to me like you have a wiring issue. The circuit design and firmware are fine. Also make sure that the panel ground is connected to the ESP ground as well as that could cause issues if missing. Otherwise recheck your wiring. Make sure you are connected to the right pins, etc. Not much i can offer. As to your question reqarding sending when no keys are sent, yes it does send an "*" once when it sees the "press * " message so that it can get zone data. That would not cause the issues you have. It does not send continuously. |
Beta Was this translation helpful? Give feedback.
-
|
Wiring is all good. What I did notice is that I did not disable the expanderaddr1. It was still "07" from the base yaml file I got from github. If that is the case, and I have a real expansion module at the same address, would it make sense that both my board and the real expansion board are being polled and the replies are stepping on each other? (I broke something in my yaml file so I can't try that right now.) I really appreciate the quick response and am finding that this project is a lot of fun. As a retired EE, I haven't had cause to prototype anything in quite a while. |
Beta Was this translation helpful? Give feedback.
-
|
Well, I got my yaml syntax errors fixed. WIth expanderaddr1 set to "0", it works perfectly. There were definitely messages from the real expander board and the ecphome-vistaalarm board stomping on each other. Guess I didn't pay enough attention to the difference between "emulate" and "monitor" in your sample yaml comments. Thanks for this great project. |
Beta Was this translation helpful? Give feedback.
-
|
Yes they would conflict. Set the expanders to 0. I didnt notice the expander line in your yaml otherwise I might have mentioned it. Glad you got it sorted!
…On Wed, Feb 21, 2024, 2:22 PM czsmith ***@***.***> wrote:
Wiring is all good.
What I did notice is that I did not disable the expanderaddr1. It was
still "07" from the base yaml file I got from github.
If that is the case, and I have a real expansion module at the same
address, would it make sense that both my board and the real expansion
board are being polled and the replies are stepping on each other?
(I broke something in my yaml file so I can't try that right now.)
I really appreciate the quick response and am finding that this project is
a lot of fun. As a retired EE, I haven't had cause to prototype anything in
quite a while.
—
Reply to this email directly, view it on GitHub
<#124 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABW4E7N5GJTKY4WKLSNR3ULYUZCQ7AVCNFSM6AAAAABDTPZGCOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DKNBXHA4DM>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
I built the ESP8266 version using the single opto exactly as shown in the first diagram. (Well, maybe I used a 34K resistor instead of a 33K, but that's about it.)
I am have been getting "Check 107" errors and errors about zones on my expansion card with the device.
What is particularly interesting is that if I do not connect U2/pin 5 (collector) to the red signal, I have absolutely no problem and it runs for days. If I do connect it, I get the errors within minutes.
So I put a scope on the U2 input (pin 1) with the yellow probe and the output (pin 5) with the blue. Something is amiss about the signal... the output rises before the driving input. And the output can remain high while the driving signal is low.
This looks very much like there is a collision. I suspect:
I am not doing anything on the HA alarm panel to trigger a transmission (e.g. no keypresses) I suspect that there is polling or checking going to that causes the 8266 to start transmitting almost immediately after there's activity on the green line. Or just very frequent coincidences.
To check this out a bit more, I added a 4.7K resister between the red input that's the pull-up on the opto (U2/pin 5). The pattern looks much clearer then.
The intermediate voltage shows the 8266 is attempting to pull the green signal high but someone else is driving it low.
I have set my device address to 17 and the only devices on the bus are:
Is this board communicating even when not pressing buttons or activating the alarm?
Any idea what's going on or areas that I should be checking next?
I tried to add the VistaAlarm yaml file, but it cannot be attached and if quoted is a display mess. You can find it here on Google Drive: https://drive.google.com/file/d/10dy3p6kAemYUvefYIl2dgYlmd-v3dxOi/view?usp=sharing
Beta Was this translation helpful? Give feedback.
All reactions