You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, although Espurna is born on the wave of ESP switches, IMO it differs radically from other frameworks as it can be also a good generic ESP firmware that can be adapted to lots of solutions very different from wifi switches.
With this goal in mind, I'm trying Espurna on bare bone ESP-12F and Wemos D1 mini without a relay and without a predefined LED behaviour, but as of 1.12.4a by defining ESPURNA_CORE the switch#0 is included in the UI and the LED doesn't have an "unhandled" option, therefore occupying two precious GPIO.
As a generic firmware, ESPURNA_CORE should not include switch#0 and the LED should have a "Custom" choice in the drop-down. This should be limited to ESPURNA_CORE without any impact the currently supported switches.
Piero
The text was updated successfully, but these errors were encountered:
Hi, although Espurna is born on the wave of ESP switches, IMO it differs radically from other frameworks as it can be also a good generic ESP firmware that can be adapted to lots of solutions very different from wifi switches.
With this goal in mind, I'm trying Espurna on bare bone ESP-12F and Wemos D1 mini without a relay and without a predefined LED behaviour, but as of 1.12.4a by defining ESPURNA_CORE the switch#0 is included in the UI and the LED doesn't have an "unhandled" option, therefore occupying two precious GPIO.
As a generic firmware, ESPURNA_CORE should not include switch#0 and the LED should have a "Custom" choice in the drop-down. This should be limited to ESPURNA_CORE without any impact the currently supported switches.
Piero
The text was updated successfully, but these errors were encountered: