Currently some links in the documentation seem to be broken. They need to be fixed.

• find broken links
• fix them

As a user I do want to access the WebUI directly with the Tesla Browser.

In #36 we want to introduce a new hardware version. Since the board dimensions changed, a new case should be designed to properly fit it.

• Once the boards are there, design a new case
• Make sure it can easily be 3D printed
• Provide it as stl file(s)

Shhhhhh🤫...

Based on a few experiments I think we can switch to a json based API.

• Implement json based API
• OpenAPI document
• Swagger
• Test if it works
• Test if memory is a issue

As a developer, the pushed code shut be linted automatically.

The UI should support a dark theme and multiple languages #71 #70. For that we need a way to save these settings. I would propose to add a settings endpoint to the mcu to store these.

• Add UI Settings endpoint
• Value for fw version
• Value for theme
• Value for language
• Value for expert mode
• Add to OpenApi document and swagger

@danielbayerlein any more values I should add for the future? Anything you need for the UI?

Currently there is no way to save more than one configuration. Since it can be quite annoying to reconfigure all settings, it would be nice to store all settings in profiles so that they can be switched easily.

• Implement profiles on MCU side
• Implement profiles on UI side

The web-app was renamed to ui, this needs to be reflected in the build guide as well

The current frontend is not really suitable for all use cases anymore. Also it's not nice looking. I want to come up with a new frontend together with BlackBeaver.eu.

• Create a new frontend design
• Setup a project with ReactJS
• Port the design to the ReactJS project
• Implement the frontend logic and provide all features we had before
• Add a mockserver for easier development
• Add an option to access the log via the Ui
• Update documentation

The controller is creating a WiFi hotspot when it is started. This connection should be used to transfer a new firmware to the controller. Since there also is a frontend, this firmware should be a package containing the executable code and the frontend.

• Come up with a suitable package format, no compression
• Create a tool to build these packages
• Implement endpoint to upload the package to the controller
• Implement a class to install the update
• Remove the WiFi client functionality since no longer needed
• Add frontend option to upload TUP files
• Export new Postman collection under documentation

Installation guide for Tesla Model 3 and Model Y should be added to the documentation.

• Remove the panels from the car
• How to get power from the CAN connector in the center console
• Install the TesLight controller in the center console
• Install the fibre cable around the center console
• Install the LED strip under the dash board
• Install the LEDs in the front doors
• Install the LEDs in the rear doors
• Connect the TesLight controller to the oem ambient light
• Close everything up and test it

In the main loop there is bug in the timer related to the light sensor. There millis() instead of micros() is used. This isn't breaking anything but should be fixed.

After the planning (#2) and parts (#3) were documented, it's time to write the build guide.

• How to order the PCB and printed parts
• Build the TesLight controller
• Build the LED injectors
• Upload the software
• Prepare the SD card
• Test run
• Link it to the readme

In the TesLight_Case and TesLight_Fan_Adapter there are 0.8mm wall thickness detected by jlcpcb.

A simple button for switching the fan on (full power or adjustable) regardless of the temperature

Calibrating the motion sensor at each start of the controller is not the best solution. When the car is not parked on an even ground, this can lead to miscalibration. To solve this issue, the calibration should be saved to the configuration and a recalibration via the UI should be possible.

• Save the calibration data to the configuration
• Only calibrate the sensor when no calibration data exists or the user is triggering the calibration via the UI

The cable length for dashboard and front doors should be 50cm shorter for the Model 3. This makes the cable management easier.

• Adjust the cable length in the documentation

Nothing here, it's still a secret 😉 ...

Before building the TesLight project some consideration and planning is required. These should be documented to support users to get started with the build.

• Document knowledge that is required before the build
• Document required planning before starting the project
• Link it to the readme

After updating to the latest core, the performance of reading single pixels from the fseq file dropped significantly. This is dues to optimizations inside the SD lib. It's now always reading a number of bytes for better performance when reading more than one byte.

• Adjust FseqLoader and FseqAnimator to read all pixels at once into the pixel buffer

Currently the rainbow animators use an approximate cosine wave with a 120° shift to achieve the RGB effect. Due to the rounded wave form this causes unwanted and unpleasant looking side effects on low brightness settings. The solution should be to use a trapezoidal wave form.

• try this solution and see if it works better

In #36 we want to introduce a new hardware version. Due to this, adjustments to the documentation are necessary.

• Go through the documentation and fix outdated parts

It would be best if the antenna of the ESP32 points to the front and the USB port to the back of the vehicle. This way we ensure consistent acceleration directions from the sensor for all users.

To Reproduce
Steps to reproduce the behavior:

1. Go to Settings
2. Adjust Fan Start Temp to less than 45 °C
3. Apply Settings
4. See error

Screenshots

Information:

• Device: iPad Mini 5
• Browser Safari

Recently a new hardware prototype was designed. It should solve flickering issues with some types of LEDs due to a too low signal voltage. Also it now gives the option to use a second voltage regulator and so split the load. Allowing for a total power output of around 30W. As a request from the community, two more output channels were added. A 4 pin connector, exposing an I2C BUS is now available as well. It might be used for hardware extensions.

• Test the new boards once they arrive
• Analyze the level-shifted data signal
• Test the I2C BUS
• Test the dual regulator setup
• Adjust the software to support two more channels
• Close #37 before closing this issue
• Close #38 before closing this issue

Looking at it today I had some doubts the controller fits in the current case with the onboard voltage regulator.

• Check if it fits
• Fix it otherwise

Like discussed earlier it would be interesting to have an endpoint that is exposing some system information. Also with the new audio analyzer we are bringing more optinal hardware into the project. With this, some features might not be available for everyone. Having a list of available hardware, the UI can hide unavailable settings and options.

• Collect system and hardware information inside a SystemInformation class
• Include: RPS, FPS, power consumption, temps, fan, memory usage
• Collect information about available hardware: Audio analyzer, BH1750, MPU6050 (yes we can make it optional with that step), installed regulators

I recently experienced different, randomly appearing crashes like:

Guru Meditation Error: Core  1 panic'ed (Cache disabled but cached memory region accessed). 

Core  1 register dump:
PC      : 0x4011b968  PS      : 0x00060035  A0      : 0x800814ae  A1      : 0x3ffbf1fc
A2      : 0x00000002  A3      : 0x00000001  A4      : 0xbad00bad  A5      : 0x00000000  
A6      : 0x00000006  A7      : 0x00000000  A8      : 0x8011b963  A9      : 0x3ffbf1dc  
A10     : 0x00000001  A11     : 0xffffffff  A12     : 0x000f8023  A13     : 0x00000006  
A14     : 0x007bf2a8  A15     : 0x00000000  SAR     : 0x0000000f  EXCCAUSE: 0x00000007
EXCVADDR: 0x00000000  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000  


Backtrace:0x4011b965:0x3ffbf1fc |<-CORRUPTED

  #0  0x4011b965:0x3ffbf1fc in xPortEnterCriticalTimeoutSafe at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/freertos/port/xtensa/include/freertos/portmacro.h:590
      (inlined by) vPortEnterCriticalSafe at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/freertos/port/xtensa/include/freertos/portmacro.h:599
      (inlined by) rmt_set_tx_intr_en at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/driver/rmt.c:497

Guru Meditation Error: Core  1 panic'ed (Cache disabled but cached memory region accessed). 

Core  1 register dump:
PC      : 0x4011bae0  PS      : 0x00060035  A0      : 0x800817f2  A1      : 0x3ffbf22c  
A2      : 0x3ffc3220  A3      : 0x00000002  A4      : 0x0ffd114c  A5      : 0xfffffffe  
A6      : 0x0000001a  A7      : 0x00000008  A8      : 0x800813d5  A9      : 0x00000008  
A10     : 0x00000002  A11     : 0x00000000  A12     : 0x00000010  A13     : 0x00000000  
A14     : 0x00000003  A15     : 0x00060323  SAR     : 0x00000012  EXCCAUSE: 0x00000007  
EXCVADDR: 0x00000000  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000  


Backtrace:0x4011badd:0x3ffbf22c |<-CORRUPTED

  #0  0x4011badd:0x3ffbf22c in rmt_set_tx_thr_intr_en at ??:?

Guru Meditation Error: Core  1 panic'ed (Cache disabled but cached memory region accessed). 

Core  1 register dump:
PC      : 0x4011b92c  PS      : 0x00060035  A0      : 0x800817f2  A1      : 0x3ffbf22c
A2      : 0x3ffc3080  A3      : 0x0028800a  A4      : 0x0ffd114c  A5      : 0xfffffffe  
A6      : 0x0000001a  A7      : 0x00000008  A8      : 0x800814ae  A9      : 0x3ffbf20c  
A10     : 0x00000002  A11     : 0x00000001  A12     : 0x3ff56ac8  A13     : 0x00000000  
A14     : 0x00000006  A15     : 0x00000000  SAR     : 0x00000007  EXCCAUSE: 0x00000007  
EXCVADDR: 0x00000000  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000  


Backtrace:0x4011b929:0x3ffbf22c |<-CORRUPTED

  #0  0x4011b929:0x3ffbf22c in rmt_module_enable at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/driver/rmt.c:130

I have no clue at the moment, why this is happening, what exactly is causing it and how to fix it. But we need to do something about this otherwise I see the project at risk. Unfortunately, I can't provide any code that is constantly reproducing it. click. Using WiFi in STA mode seems to trigger it more frequently. Same for using the Os optimization flag. Also, it seems to be related to the rmt driver. At least it can be found in almost every stack trace.

Maybe related, but should be fixed in the meantime: espressif/esp-idf#9487

When updating to the new UI the option to change the number of LED per channel went missing.

• Bring the option back

Currently at the top of most files there is a comment with the file version and last changed data. These should be removed since it's to much effort to keep it up to date.

Since zones can use different LEDs, the current consumption should be configurable per zone.

• current consumption is individualizable per zone

Currently there are two ways to turn on/off the LEDs with TesLight. This is by measuring the voltage of the footwell lights or by using a BH1750 light sensor which can be plugged into the I2C connector. Since some Teslas don't have the footwell lighting, it would be good to have alternatives.

• Try if the motion sensor can be used
• Try if Bluetooth could be an option (for example detecting the phone)

With the hardware update 2.1 the following features should be introduced.

• Upgraded board design
• Fan control
• Temperature sensors
• Temperature check of regulators
• Reduce brightness when reacahing a high temperature
• Values configurable in the UI
• Implementation of the BH1750 light sensor

• Implement fan controller
• Implement temperature sensor
• Implement overheat protection
• Make it configurable via the UI
• Update documentation
• More hardware abstraction
• Implementation of the BH1750 light sensor
• Test the chaos you created...

It would be good if there is an option to configure a power limit for the LEDs to protect the voltage regulator.

• Implement power limiting feature for the controller
• Make it configurable via the settings
• Expose settings to the Ui

For Tesla Model 3:

It was mentioned that there is no documentation for the capacitors C2 and C3 which is correct.

• Add documentation and build steps for these two components

The log file created by the controller should accessible via the rest API and UI. This should allow to access it easily without removing the MicroSD card. Also, it makes it easier to report and trace bugs.

• Get the log via rest API
• Clear the log via rest API
• Make it accessible via the UI

Building the TesLight project requires different hardware parts. The PCBs and 3D prints may be ordered online. There should be a part list in the documentation and the ordering process should be described.

• Part list (split in required and optional)
• Describe how to order PCBs and 3D prints
• Link it to the readme

Install temperature sensors:

    I know I wrote this myself. Not looking at it again I feel like 5m is a lot. Wonder why I wrote it back then. Probably because of the lengths that are available on Amazon. Maybe we should check again if we can get away with less waste.

Originally posted by @TheRealKasumi in #52 (comment)

It should be possible to set the theme of the app in the settings.

In the Tesla there already is an existing ambient light in the foot area. TesLight is connected to this to capture the signal.

• Use the signal to turn on/off TesLight
• Fade control, no rapid on/off
• Automatically adjust the brightness based on the signal
• Add configuration options to TesLight and expose them via api
• clean main.cpp
• Adjust the UI

When a custom animation is played, the brightness settings for the zones can't be accessed. This issue is only related to the UI and has nothing to do with the mcu. This should be fixed until 24.12 because then custom animations will be available to everyone.

• Add a option to the UI to adjust brightness while playing a custom animation.

This needs to be fixed because it's dumb.

In part list, we can add this 3 wire cable as an example for the connection wires.

As a developer, the build of the update package should be triggered automatically for every commit. Docu fixes should be excluded.

• build the TesLight Update Packaging Tool in workflow
• build the packagws with the tool

Use an "electricity thief" to get the signal of the factory build Footlights. You can even use this T-connector.

It could look like this if you add the correct plugs.

It should be possible to set the language of the app in the settings.