mwood77/winderoo

Winderoo - Supercharge your Open Source Watch Winder (OSWW) build!

winderoo's Issues

Fix FE dependabot issues

https://github.com/mwood77/winderoo/security/dependabot

mDNS stops working after ~2 minutes

I'm basically seeing this issue - any idea if there's an easy fix?

espressif/arduino-esp32#4406

Add support for multiple powered winders on one network

There's a possibility more than one powered unit will be on the network. Therefore, each winder should search the network to discover if there are other active winders already on the network & available at http://winderoo.local.

If there are, it should try to find an 'available 'domain' on the network.

The code could be something like:

 // pseudo code..
 int domainNumber;     

 // winder exists
 if (PING winderoo.local (status code) == 200) {
    // find incremented mDNS address to use

    for (int i = 0; i < 10; i++) {
        if (PING winderoo[i].local (status code) != 200) {
             domainNumber = i;
             break;
        }
    }
    MDNS.begin("winderoo"+domainNumber);
 }

Improve documentation

Introducer linter for c++ code

It's a mess - make it a bit nicer.

https://docs.platformio.org/en/latest/advanced/static-code-analysis/tools/clang-tidy.html

Add support for physical interrupt button.

There are a large number of requests for a physical button to change on/off state. This would stop all activity when pressed.

A couple nice features could come out of this:

1. We would now have a physical 'sleep/wake' button. When the button is pressed, it should toggle winderEnabled either true or false.
2. If the device is in the 'OFF' state, the onboard LED should 'snooze.' This can be accomplished with PWM.

Time calculation is incorrect

220rpd = 58 minutes
240rpd = 2 hours 4 minutes

440rpd = 2 hours 57 minutes
440rpd = 4 hours 2 minutes

660rpd = 4 hours 56 minutes
6800rpd = 6 hours 1 minutes

ruh roh raggy....

Android mDNS resolution failure

What

Android cannot resolve .local mDNS domains. Browsers offload mDNS resolution to the OS, which cannot resolve the request due to "security concerns" (google).

See issues

• https://issuetracker.google.com/issues/140786115
• https://bugs.chromium.org/p/chromium/issues/detail?id=405925
• https://source.android.com/docs/core/ota/modular-system/dns-resolver#mdns-local-resolution

Work Around

Front end

• Automatic retrieval of domain from window url & pass through domain to service layer. This is a bandaid fix.
  • Android users will have to access it via ip for now.
  • possible to deploy a 'discovery website' to assist in resolution, but that's a serious PITA.

Android

• Disable 'Private DNS'

Resolution

• Unable to resolve this for devices that are not running on Android 12 (Pixel).
• Unsure when other device manufacturers will roll out a release containing fix Android 12 SQ1A220105.002

Investigate WiFi Manager callbacks for webserver / mDNS autostart after captive portal success

Winderoo must be physically reset after successfully connecting to a user's WiFi network; this is inconvenient.

Investigate whether a callback exists that can trigger the webserver & mDNS to start after successfully changing wifi networks.

Introduce Internationalization for GUI

i18n & localization should be supported by the GUI.

Reduce Power Consumption

• Under clock processor to 80 MHz
• Enable Light Sleep (double check applicable)

Issue with mDNS and Android

It seems that mDNS doesn't work properly on Android which causes the Winderoo web UI to not work anymore after #36. At least I couldn't get it to work... 😅

It turned out that I cannot resolve http://winderoo.local on any Android device (7, 12, 13, 14).
Before the change in #36, it was possible to access the web UI with the IP of the ESP32 on Android and the API call was then done towards the IP. With my change in #35, the API call would be done to any domain that was used for the UI (which is of course accessible, otherwise the UI would not load at all).

But now since #36, the API call is always done to http://winderoo.local, even if the IP is used to load the UI or if a custom non-.local-domain name is used (I can set this with AdGuard Home in my LAN).

I did some research and found some issues where this one seems to be quite similar to my problem:
espressif/arduino-esp32#9051

esphome/issues#3003

I can access the .local domain which is broadcasted from a Raspberry Pi with OpenHAB, but I cannot access the .local from the ESP32 on Android.
On Linux or iOS it works fine.

Long story short - @mwood77 do you observe the same with an Android device? Or does it work for you on Android? I'm currently not sure if it's an issue in my network or an issue in the combination Android + mDNS on ESP32.

To not be dependent on mDNS, perhaps the web UI could load the API from the IP of the ESP32 instead of the mDNS .local domain?

Bill of materials list links aren't working anymore

Hi, I tried to follow the link for the ESP32 board but it no longer exists. Unfortunately there's a ton of slightly different ESP32 boards at AliExpress and the more inexperienced of us (me on top of that list) are afraid to get a wrong one