Feedback cover gets inconsistent state after transient spike on a sensor · Issue #6660 · esphome/issues · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using a feedback cover for my parking gate, which has 4 "state" sensors: 2 limit switches (open/closed) and 2 motor sensors (opening/closing).
The cover works perfectly 99.9% of the time but, sometimes, an ingress spike is created by the motor current on the opposite sensor (e.g. at the end of the closing phase, the "opening" sensor registers a transient on/off).
In that case, the issue is that the feedback cover is left in an inconsistent state:
although the gate is really closed, and the position of the cover is "100% closed", and the "open" action is enabled, and the "close" action is disabled,
the state of the cover is "Open" instead of "Closed"...
That can be seen in the following captures taken 2 hours after the gate was closed (info highlighted in green is consistent, red is not):
Here is the history log in text and graphical form:
The transient spike on the "is_gate_opening" sensor can be seen at 07:29:04 and is immediately followed by a "Was Opened" state (although only the "is_gate_closed" sensor is On). The state of the gate is thus left "Open".
Which version of ESPHome has the issue?
2024-12-2
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2025.1.1
What platform are you using?
ESP8266
Board
D1 mini
Component causing the issue
Feedback cover
YAML Config
esphome:
name: "esp-parking"friendly_name: ESP Parkingesp8266:
board: d1_mini# Enable logginglogger:
# Enable Home Assistant APIapi:
encryption:
key: "************"ota:
password: "************"wifi:
ssid: !secret wifi_ssidpassword: !secret wifi_password# Enable fallback hotspot (captive portal) in case wifi connection failsap:
ssid: "Esp-Parking Fallback Hotspot"password: "************"manual_ip:
static_ip: ************gateway: ************subnet: ************captive_portal:
output:
- platform: gpiopin: D7id: gate_control_close
- platform: gpiopin: D8id: gate_control_open
- platform: gpiopin: D4id: gate_control_stopinverted: truebinary_sensor:
- platform: gpioid: is_gate_openingname: is_gate_openingpin:
number: D1mode:
input: truepullup: trueinverted: true
- platform: gpioid: is_gate_closingname: is_gate_closingpin:
number: D2mode:
input: truepullup: trueinverted: true
- platform: gpioname: "Gate obstacle detected"pin:
number: D3mode:
input: truepullup: trueinverted: true
- platform: gpioid: is_gate_openname: is_gate_openpin:
number: D5mode:
input: truepullup: trueinverted: true
- platform: gpioid: is_gate_closedname: is_gate_closedpin:
number: D6mode:
input: truepullup: trueinverted: truecover:
- platform: feedbackdevice_class: gatename: "ParkingGate"id: parking_gatehas_built_in_endstop: Trueopen_action:
- output.turn_on: gate_control_open
- delay: 300ms
- output.turn_off: gate_control_openopen_duration: 20sopen_endstop: is_gate_openopen_sensor: is_gate_openingclose_action:
- output.turn_on: gate_control_close
- delay: 300ms
- output.turn_off: gate_control_closeclose_duration: 20sclose_endstop: is_gate_closedclose_sensor: is_gate_closingstop_action:
- output.turn_on: gate_control_stop
- delay: 300ms
- output.turn_off: gate_control_stopscript:
- id: postman_accessthen:
- cover.control:
id: parking_gateposition: 25%
- delay: 65s# must be = opening time + duration of the "open" phase
- cover.close: parking_gate
- delay: 8s# must be = closing time + a few secs (motor slows down when nearing full close)
- switch.turn_off: postmanswitch:
- platform: templatename: "Postman"id: postmanoptimistic: True #otherwise it turns off automatically after a delay as it has no confirmation of a stateturn_on_action:
- script.execute: postman_access turn_off_action:
- script.stop: postman_access
- cover.stop: parking_gatebutton:
- platform: restart # reboot buttonname: "Gate module reboot"
- platform: outputname: "Gate control open"output: gate_control_openduration: 300ms
- platform: outputname: "Gate control close"output: gate_control_closeduration: 300ms
- platform: outputname: "Gate control stop"output: gate_control_stopduration: 300ms sensor:
# wifi signal level in dBm
- platform: wifi_signalname: "Gate WiFi signal"update_interval: 60s# ESP uptime (to track reboots, if any)
- platform: uptimename: Uptime Sensor
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The problem
I am using a feedback cover for my parking gate, which has 4 "state" sensors: 2 limit switches (open/closed) and 2 motor sensors (opening/closing).
The cover works perfectly 99.9% of the time but, sometimes, an ingress spike is created by the motor current on the opposite sensor (e.g. at the end of the closing phase, the "opening" sensor registers a transient on/off).
In that case, the issue is that the feedback cover is left in an inconsistent state:
although the gate is really closed, and the position of the cover is "100% closed", and the "open" action is enabled, and the "close" action is disabled,
the state of the cover is "Open" instead of "Closed"...
That can be seen in the following captures taken 2 hours after the gate was closed (info highlighted in green is consistent, red is not):
Here is the history log in text and graphical form:
The transient spike on the "is_gate_opening" sensor can be seen at 07:29:04 and is immediately followed by a "Was Opened" state (although only the "is_gate_closed" sensor is On). The state of the gate is thus left "Open".
Which version of ESPHome has the issue?
2024-12-2
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2025.1.1
What platform are you using?
ESP8266
Board
D1 mini
Component causing the issue
Feedback cover
YAML Config
Anything in the logs that might be useful for us?
No response
Additional information
Details on the build, with pictures, schematics and a video demo (of the 99.9% case when it works ;-)) can be found in my blog post at http://blog.deconinck.info/post/2024/01/20/Came-Home-Assistant-Interface
The text was updated successfully, but these errors were encountered: