search

datjan / HomeSpanUI

Webinterface for HomeKit devices running on the Arduino-ESP32
https://www.homekitblogger.de
MIT License
15 stars 0 forks source link

GPIO output gpio_num error #2

Open YouCanNotBeSerious opened 9 months ago

YouCanNotBeSerious commented 9 months ago

Can you help with what this means exactly?

When trying to use GPIO 34 or 35 .... other pins work fine. 

19:57:38.109 -> 35 (outlet) -> switch: off
19:57:39.099 -> E (76189) gpio: gpio_set_level(227): GPIO output gpio_num error

For 35 per the schematic below it is. tied midway on the battery rail so I can see why not to use it but how does the error get generated just because the pin is already biased with resistors?

For 34 I can't see any reason not to use that pin, it's not used for anything else on the D32 board that I can see....and not used for SPI or AP mode buttons in the setup.

https://www.wemos.cc/en/latest/_static/files/sch_d32_v1.0.0.pdf

YouCanNotBeSerious commented 9 months ago

FYI what I did to solve my problem on this is simply tested by creating LED accessories and mapped out the pins that work and noted them down. I guess it is not HomeSpanUI's fault if some pins are not available on the real hardware even if logically available, AND the debug serial is warning you of the issue, so this is not really a bug/issue and can be closed IMHO.