cyrille-g / master-dimmer Goto Github PK

2.0 1.0 0.0 62 KB

esp8266 based board controlling white led strips with MQTT commands sent by custom sonoff touch. See readme for details

C 14.64% C++ 85.36%

master-dimmer's Introduction

master-dimmer

The ESP8266 sends PWMs to control led strips, either using wifi or serial commands.

The code works (although no wifi, but i might have fried that because it should).

It currently only controls one led strip on the D7 pin, and applies the state, brightness, and transition time parameters specified in JSON format.

Make sure to change the default values in settings.h .

Json examples:

{ "state": "ON" }

{ "state": "ON" , "brightness": 600}

{ "state": "ON" "brightness": 600, "transition" : { "preset": "AUTO" }}

{ "state": "ON" "transition" : { "preset": "CLOCK", "TimeMs": 2000 }}

{ "state": "ON" "brightness": 600, "transition" : { "preset": "CLOCK", "TimeMs": 2000 }}

This is my first github project and more an experiment than something else, so please be patient and show forgiveness :)

The code was first based on @corbanmailloux work (https://github.com/corbanmailloux/esp-mqtt-rgb-led), but i only kept the wifi part in the end.

TODO:

Apply coding rules
Add light sensor code (sensor connected on the analog input)
Add ntp clock usage
Add pattern code
update JSON commands for other lamps

Warning

Do NOT try to connect your led strip on D7, you need a mosfet that can work with 3.3V level, or any kind of mosfet driver that will take that voltage level.

I will publish the schematics when i have tested it enough. For now it seems to work pretty well and does not heat, but be extra careful when assembling and trying it; remember this circuit can command tens of amps, which can easily start a fire. If your AC/DC converter is badly wired, it could also kill you, so if you do not know for sure what you are doing, please ask someone who does to do the assembling and testing for you.

Your mileage may vary, i will not take any responsibility if you end up frying something.

master-dimmer's People

Contributors

Stargazers

Watchers

master-dimmer's Issues

sending the "OFF" command twice in a row crashes and reboot the esp

probably a division by 0 somewhere as "OFF" is meant as "zero brightness". Setting it twice in a row means a transition going from 0 to 0 which is meant to break things if not caught

manual control of a led strip from the serial interface

requires working lestrip controler hardware and software, and defined JSON format

setting pwm value with the debug webserver causes some memory corruption

The data returned by the webserver is totally wrong. The function is currently commented.

Add dimming vs time system

time is provided by NTP, now we need to generate scenarii based on time when a command is issued.

use these settings vars.
gConfAutoDimStartHour // "time to start dimming" hour. Dimming will start from now.
gConfHourOfInflexion // "pitch blackest time of your night" hour. The closer to this hour, the dimmer the light.
gConfAutoDimStopHour // "time to stop dimming" hour. Dimming will be back to normal at that time.
gConfMaxDimmedBrightness // this brightness is achieved at gConfHourOfInflexion
gConfMaxDimmedTransitionTime // this time will be used at gConfHourOfInflexion

Step 1: linear interpolation
Step 2: cosinus interpolation

Configure and save parameters using webserver

the goal is to set the data currently in the settings.h file by using the webserver. It needs to be saved in the eeprom.

Implement OTA updates

Now that the system is up and running, getting the chip out to flash it is a problem.

computing scenario while one is executing gives bad result

scenario generation is based on the current brightness and computes a target brightness. This causes a problem when a scenario is already executing:

either the executing scenario and everything in the scenario queue has to be trashed, and we can use current brightness,
or we need to use the last queued (or the executing scenario if there are none) target brightness as a starting point.

Use power on demand and TC4489 "B" pin

set power on demand ON if at least 1 led strip is ON.
set TCC4489 "B" pin the same way.

Wifi does not connect on startup

This may be a local router issue or a fried board as the code seems to be quite standard on that.

My wifi router gives the ESP an IP address and can ping it when the ESP starts, yet the ESP is stuck in the setup / setup_wifi() call, with wifi.status() always reporting WL_DISCONNECTED.

Webbased logging system needed

Since the esp is now away from the computer, looking at what it is currently doing or what it was doing is hard.

Add a log message queue and send it on demand on the webserver.

Add a webserver subsystem

Add unit testing framework

The software is currently not unit tested. It will use mmurdock system, as soon as it works with esp8266

wrong json parsing on the transition item

root[transition] is supposed to return something not null when the item has subitems. It currently returns null. It could be a bug from the parser or a wrong usage, either way do not test for root[transition]

Code is hard to read. Separate in more files

As the title says.

Add a "JSON command queue" to implement complex scenarii dimming

The current system works by trying to reach the target brightness in a given transition time using linear interpolation. When a JSON command is received, waiting and brightness steps for the whole process are computed.

add a command queue so locally generated commands gets pushed in and executed. This will allow complex scenarii by interpolating short linear sequences.

Serial and wifi MQTT commands should clear the queue once they have been processed, before the result of their processing is pushed in the queue.

add 3 queues
update available topics from "light/topic/state" to:
light/corridor/
light/toilet/
light/bedroom/
light/diningroom/

Problems on tokenizing

when parsing the topic, strtok destroys the topic. Make a backup before parsing.
when parsing a topic, the system will never find the room in the list.