A HUB component was introduced. This HUB component has all the knowledge
about the Yeelight Bedside Lamp 2 hardware. It known what pins are used,
that PWM frequencies to use, what pins to switch in binary mode, etc. etc.
No configuration is required for this HUB component. It's automatically
loaded when the light component is loaded. The light component will use the
HUB component to access the pins that are required for driving the LED
circuitry.
Note that this simplifies the configuration by A LOT. There's no need
anymore to configure the pinouts in the YAML file. This is a logical route
to take, since we're talking about a factory-produced PCB with a soldered on
ESP32 chip, which uses the same GPIO's and settings on all produced devices
(I presume). It would be quite redundant to force every user into
configuring these pinouts themselves.
** Beware to update your device yaml configuration **
There are a few pinouts left to move into the HUB. I will do that in the
next commit. Your device yaml configuration can be simplified along with
these changes. Some of the keys in the existing light configuration block
will no longer work and will have to be removed (red, green, blue, white).
** Further development **
The HUB will be extended make it the central component that also handles
the I2C communication. This way, there is a central place to regulate the
traffic to and from the front panel. We will be able to build upon this
by implementing extra, fully separated components that handle for example
the front panel light level, the power button, the color button and
the slider.
** Interrupt handler for the I2C IRQ trigger pin **
One requirement for the I2C communication has already been implemented: an
interrupt handler for the GPIO that is used by the front panel to signal the
ESP that a new touch or release event is avilable to be read.
It doens't do anything functionally right now, but if you watch the log
file, you will see that touch events are detected and that they trigger some
log messages.
The work-around has been implemented in a forward-compatible manner,
so the light transition when turning off the light should still
work once the upstream code gets fixed.
* When turning off the light at a low brightness setting,
the LEDs were seen flashing brightly for a short time.
* Transitioning did not work when turning of the light. The light would be
kept at normal brightness during the transition and then it turned of
at once. This looks like an issue in the ESPHome transitioning code,
because that is the code that is responsible for the transitioning.
When turning on the light, it works correctly. I see both the state
and the brightness go up. But when turning off the light, I see that
the state decreases gradually to zero, but the brightness is kept
as-is. I wrote a fix for this behavior in my code and will investigate
if the ESPHome code can be fixed for this.
Maurice Makaay
mmakaay
Maurice Makaay