Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
- [ ] Set `weblog` to 4 and then, when you experience your issue, provide the output of the Console log:
```lua
Console output here:
TO REPRODUCE
Steps to reproduce the behavior:
block external internet access.
setup venetian blinds according to manual.
ShutterTiltConfig1"0 0 90 17 0 90
play with the shutter, move it up and down. At some point you will notice a lag. It will move with a delay. Apparently that's when a time server sync is pending - and failing.
move blind to close.
move it up.
while it moves up, change tilt. That should crash it.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
either stop and set tilt or complete movement and ignore tilt.
if the issue is related to a reboot, moving the shutter all the way up or down for the configured amount of time should fix this.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
I use a FritzBox, that does also provide the time. Setting NTP1 to 192.168.1.1 apparently fixes the issue.
(Please, remember to close the issue when the problem has been addressed)
PROBLEM DESCRIPTION
A clear and concise description of what the problem is. Blind position jumps to zero when a tilt command is issued while the blind is moving.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Status 0
:TO REPRODUCE
Steps to reproduce the behavior:
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here. I use a FritzBox, that does also provide the time. Setting NTP1 to 192.168.1.1 apparently fixes the issue.
(Please, remember to close the issue when the problem has been addressed)