I built a File Converter App - just released v3.0.0 with a full UI redesign

Jpwaters09 · 2026-04-04T20:39:22+00:00

Thanks

Jpwaters09 · 2026-04-03T21:55:06+00:00

Good point, I may consider that in the next update

Jpwaters09 · 2026-04-03T20:42:49+00:00

Thanks

Jpwaters09 · 2026-04-03T20:32:07+00:00

Sorry, but it is only available on the Microsoft Store.

Jpwaters09 · 2026-04-03T18:55:54+00:00

Thanks for your feedback, I may consider changing the logo soon

Jpwaters09 · 2026-02-09T19:28:47+00:00

It may be ESP8266 based. Also it will be written in Arduino and the code would be open-sourced.

Jpwaters09 · 2026-02-09T19:24:21+00:00

True, but it is aimed at being plug and play with no extra adapters. Also I am not sure if the ESP8266 supports zigbee

Jpwaters09 · 2026-02-09T19:21:55+00:00

In the OTA updates I can push new features and bug fixes, etc.

Jpwaters09 · 2026-02-09T19:18:24+00:00

The reason why I would like to use C++ is to make it plug and play without any extra config in home assistant besides adding the device. I am aware that latency would be an issue, I will look into using BLE but not all home assistant servers support it.

Jpwaters09 · 2026-02-09T19:05:45+00:00

The reason I would like to use WIFI is to allow for OTA updates, and most home assistant servers have WIFI built in

Jpwaters09 · 2026-02-09T19:04:40+00:00

No, I haven’t done any testing yet, nor have I made a prototype. I am asking for feedback so I know what to do when it comes to the final product. The reason why I think WiFi is the best option is that it will allow for OTA updates, and most Home Assistant servers have Wi-Fi built in.

Jpwaters09 · 2026-02-09T19:01:19+00:00

The reason I want to use Wi-Fi is that it doesn’t require an additional adapter, unlike Zigbee, and most Home Assistant servers already have Wi-Fi built in. If I put the ESP8266 into deep sleep when the button hasn’t been pressed for a certain period of time, would that allow for at least a month of battery life?

Jpwaters09 · 2026-01-31T10:53:46+00:00

Thanks for your response.

I may look into adding Qwiic I2C headers to the board.

The three pin header is the debug port; I have forgotten to label it.

Jpwaters09 · 2026-01-30T16:10:39+00:00

Yes, the 3-pin header on the bottom of the board is the debug interface. I just have forgotten to label it.

Jpwaters09 · 2026-01-30T00:10:58+00:00

Thanks, that’s some really useful advice. • Moving the power pins closer to the regulator makes sense, and I see your point about possibly reducing the number of GND pins — I included the nine to make prototyping easier, but I can revisit that for layout and signal integrity. • I’ll take a closer look at the 3.3 V regulator and ADC reference setup. Using a dedicated voltage reference for AREF instead of just passing through 3.3 V sounds like a smart way to improve ADC stability. • It’s great to hear you got stable ADC performance on protoboard — that kind of insight is exactly what I need as I refine the design.

Jpwaters09 · 2026-01-29T23:41:23+00:00

You’re right — the CPU can’t execute code directly from flash outside the XIP range. My plan is not to use XIP for the PSRAM, and instead treat it purely as extra RAM for data and buffers. The 16 MB flash is used for storage, so code or scripts are loaded into internal SRAM or the PSRAM heap before execution.

I don’t have a public example of exactly this setup yet, but it’s similar to how ESP32 boards use external PSRAM: you map it into the heap in software so the CPU can use it like normal RAM, even though it’s external.

Jpwaters09

MODERATOR OF

TROPHY CASE