-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mqtt issue or code? #23
Comments
Possible that your esp8266 device is dropping off the wifi network? |
Mine does the opposite of this (if open, it alternates between open and close every minute or so). This is because I didn't install a pull-down resistor, so when the door is open, the pin is left floating. Depending on your circuit, you may have left out a pull-up or a pull-down resistor. |
When I test the first time with version 1 don't have issue only see that
after upload the vldev version.
But in none of the cases I use a pull up resistor :/
…On Mon, Sep 3, 2018, 06:01 sam-wright ***@***.***> wrote:
Mine does the opposite of this (if open, it alternates between open and
close every minute or so). This is because I didn't install a pull-down
resistor, so then the door is open, that pin is left floating. Depending on
your circuit, you may have left out a pull-up or a pull-down resistor.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#23 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACxnX7Zsc_ubTYWrLstgO9eG78R3e8NAks5uXLeUgaJpZM4WWTZa>
.
|
@sam-wright The pin shouldn’t be floating as I’m enabling the INPUT_PULLUP mode for the door status input pins. So when the door is closed, the pin is pulled low, but when open, the internal pull-up resistor should be pulling it high. Possible though that the resistor is too weak depending on your own environment. @codedmind you can try using a pull-up resistor and see if it solves your problem. |
Any sechematics to use the pull-up?
Thanks
…On Tue, Sep 4, 2018, 00:35 Mark Coombes ***@***.***> wrote:
@sam-wright <https://github.com/sam-wright> The pin shouldn’t be floating
as I’m enabling the INPUT_PULLUP mode for the door status input pins. So
when the door is closed, the pin is pulled low, but when open, the internal
pull-up resistor should be pulling it high. Possible though that the
resistor is too weak depending on your own environment. @codedmind
<https://github.com/codedmind> you can try using a pull-up resistor and
see if it solves your problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACxnX1KdbPEyY3uwxo7m-TDkwgdDsORuks5uXbzSgaJpZM4WWTZa>
.
|
Ok @marthoc i made the connections (no resistor) an try the both versions (master and dev) in the master the serial connections show normal output, change status and keep, but the dev is always connection and publish to mqtt don't now why... same connections , same hardware . WiFi connected - IP address: 192.168.1.80 |
After some days working well now i'm getting issues when the garage doors is closed the homeassistant is getting wrong status inside a minute it open and close again, the garage door is always close...
If open everything is ok.
Any suggestion for debug?
The text was updated successfully, but these errors were encountered: