jpraus / floower Goto Github PK

When Bluetooth support is enabled, it will start in pairing mode whenever the Floower is turned on, the Floower will keep blinking blue until an app is connected. This makes it really difficult to manually control the app when Bluetooth is enabled. For example, when you manually change the color by touching the leaf it will return to blinking blue after a few seconds.

I think once the user has touched the leaf after Bluetooth mode is enabled, it should stop blinking blue and allow full manual control.

When setting the touch sensitivity to high, the Floower will think that you are holding the leaf continuously. Perhaps 'high' (value of 55) is too high.

The result is that the Floower will constantly enable Bluetooth pairing mode and the Floower will start blinking blue and stop responding to normal touches.

Hello!

Just upgraded my Floower. Thank you again for this huge upgrade! I can't wait to play with WiFi :) but ... There seems to be an issue (or something I didn't understood well).

• I am using an "old" (few years) 12W mac charger with my floower.
• BT connection works fine and I can see the "battery charging notification" on my iPhone Floower app homepage.
• My issue is that settings page complains "Please charge your floower to enable wifi"
  • as long as a red warning logo just next to the above mentionned charging animation).
• On the floower itself, i cannot see no red led shining.

best regards :)

NB: My floower is 24/24 connected to power, used (very) approx. 6 hours a week and and is a rev6.

Following instructions on this page (https://github.com/jpraus/floower#connecting-flower-to-the-computer) leads to the flower slamming closed upon sketch upload compile completion then I get this message:

Sketch uses 1004283 bytes (76%) of program storage space. Maximum is 1310720 bytes.
Global variables use 36744 bytes (11%) of dynamic memory, leaving 290936 bytes for local variables. Maximum is 327680 bytes.
esptool.py v2.6
Serial port COM3
Connecting......................................____An error occurred while uploading the sketch
_

A fatal error occurred: Failed to connect to ESP32: Timed out waiting for packet header

Running a windows 10 latest PC with newest drivers based on recommended versions and verified USB-C data cable on port COM3.

I wanted to download the updater to update my Floower.
On opening, it remains black:

MacBook Pro M1 Pro 2021 with latest macOS Monterey (12.0.1).

Hi!

Just received and unboxed my Floower. Great work with the packaging 👏 !! (though it could have been a little bit more ecofriendly :-))
Can't wait to put my hand "in" it (in the code, at least).

Unfortunately it came flashed with the 4.0 FW and I want to upgrade it, but the flasher crash on my macbook.

I can give you the full report if needed.
Have a nice day.
Here is a chunk :

Process:               Floower Flasher [12556]
Path:                  /private/var/folders/*/Floower Flasher.app/Contents/MacOS/Floower Flasher
Identifier:            io.floower.flasher
Version:               0.0.0 (???)
Code Type:             X86-64 (Native)
Parent Process:        Floower Flasher [12547]
Responsible:           Floower Flasher [12547]
User ID:               501

Date/Time:             2021-02-01 11:56:40.785 +0100
OS Version:            macOS 11.1 (20C69)
Report Version:        12
Bridge OS Version:     5.1 (18P3030)
Time Awake Since Boot: 420000 seconds (OMG 🙄 )
Time Since Wake:       2300 seconds

System Integrity Protection: disabled

Notes:                 Translocated Process

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

Hi,

First, I really like the Floower 😊. It's a great addition to the living room.

I was trying to compile the source code, but I'm running into some issues.
Floorer.h has a reference to AccelStepper.h but that file seems to be missing in the repo.

Am I missing something or did you forget it to push it to the repo?