Kuba Szczodrzyński
Kuba Szczodrzyński
> Just glancing at your changes, seems like the only chip that is supported by this right now is the wr3? @rickyelopez No; all the chips (formally called "boards") from...
Hi, how exactly are you uploading the firmware? It may be tricky at first, so make sure you follow the guides in the docs. It's best to use ltchiptool or...
Hi @jesserockz What does this PR need so that we can make it merge-able? It's not feature-complete, many components will not work yet, but I think that's the case with...
You can use values like RX2 and TX2 to make sure you don't get these mixed up. Otherwise, it'll detect a non-hardware UART and try to use software serial.
Soft serial works on Realtek, but it's TX-only. I'm not sure what happens when you try to activate SS on hardware UART pins, that's probably why it failed. Also, I'm...
LibreTuya itself has pretty much nothing to do with Cloudcutter. In fact, the vulnerability has been patched for nearly a year now. Same thing applies for ESP chips. We've had...
Hi, I think these changes might actually be unnecessary for the LibreTiny platform - it doesn't use the `build.mcu` field for compilation. The compilation process only depends on the `board`...
> And currently that (the PIO board file) is where PIO gets the mcu type from since ESPHome doesn't pass on the variant selection. Unfortunately, that's not the case in...
> I think this is probably the best idea right now. And it should be disallowed if the `board:` setting _is_ known to ESPHome. Probably not even necessary to rename...
#146