Search results

I've never seen anything like that before. It seems like something in the Arduino build process isn't working right. I only have 1.8.12 though so I'll try it with 1.8.13 tonight. From your log it looks like there's more options in the Arduino app that I don't have. Weirdly, when I compile, I...

haha yeah, that's what I started by google image searching to see what design aesthetic I could steal. It is really does look amazing, the display is really really good (apart from some flicker when updating). If it was like 2.4" it might actually be usable, but every 2.4" TFT I've bought for...

I'm not sure how easy it would be to get working on that, since the client library relies on AsyncTCP and the espressif HTTP client and WiFi libraries. It would work with a WT32-SC01 probably, but building stuff with parts on hand is always more fun (although it can take a lot longer). Heck even...

SMUSHI is another demo of the HeaterMeter client library, now with ESP32 support. I needed to make sure the client library worked on ESP32 and all the test devices I have are already doing something so I bought one of these LILYGO(R) TTGO T-Display ESP32 mouthfuls with 1.18" IPS TFT display...

Yeah I haven't tried printing the lid at all, which is why it is commented out. It may fit or it may have the bevels facing the wrong way or it might be too big or too small. I considered adding feet to it as well that slide on so it isn't so tippy but it stood up well enough I didn't finish it...

Does your model actually need lcd_ex_offset at all? The reason I use lcd_window_offset to expand the size of the case is because I want all the spacings to be the same (EDIT: or at least the outer sides), but your model doesn't have that symmetry. Looks like I can remove lcd_ex_offset from your...

Haha funny you should mention that, I just realized on Sunday that I hadn't added pidint support so that will be added. It is pretty easy to add support for message types as you've noticed, the only thing to be wary of is RAM footprint and processing time. I'm trying to keep the library as lean...

Great thanks, I'll see if I can merge them. Just need to figure out how to reconcile my misuse of lcd_window_offset to expand the size of the case for some reason I can't remember but I will blame on beer. Working on different demo for an ESP32 using the library (with updates to make it...

Looks great! If you can share the module dimensions you used I can update the official scad file to support both of them.

Yeah it is mentioned on the Thingiverse page, if your displays are too flickery then just add capacitors until it stops. I added 3x of the 100uF/10V kind that are part of the HeaterMeter BoM. Only a couple of the colors flickered so it may or may not be necessary. I'll add that to the README in...

Ah dangit, I didn't realize that. I'll see if I can find the right size ones. EDIT: Why the heck are virtually all the modules for the clock / doubledot version?

Oh geez, not sure how I forgot to include those in the readme, thanks for pointing that one. Actually I should probably remove TaskScheduler. I used it because I use it for a lot of projects and thought I'd use it here too but the only task is outputting some debug info so I'll remove that...

I've worked through importing the EAGLE files for the HeaterMeter base and LCD board into KiCad and spent a day fixing the one million tiny problems with the import. Moving forward all PCB development will be done in KiCad and the latest files are now in GitHub. I've also already received a...

I've added a simple wiring diagram and parts list to the github README. It is just two parts so it is pretty easy to put together. Wire 5V from the Wemos D1 Mini to the 5V pin on all 4 LED displays. Wire GND from the Wemos D1 Mini to the GND pin on all 4 LED displays. Wire D1 from the Wemos D1...

Switching to Pi OS would mean everything would have to be rewritten for whatever platform we'd use there. The existing code won't run on Pi OS as far as I know. We'd have to pick a new platform (apache+???) and integrate some system admin stuff too like backups and wifi configuring. It would be...

Oh haha I completely forgot that the probes have to get out as well. I didn't notice the PVC elbows. Yeah that should work, and keep everything dry!

Yeah all configuration persists across reboots. You can tell if alarms are enabled for a probe because it has a little bell icon on the home page. There's no way the system can get confused and configure the setpoint to change on alarm unless you set one in the alarms screen. They're also stored...

hehe actually I'd prefer if it were. The story goes that LEDE split off from OpenWRT and all the developers I knew (from their work) went to LEDE so I converted everything to follow that project, which meant rebasing patches as they were converting the way the project was layout. Then, like six...

No it is based on unreleased LEDE Reboot git version 94491a15712732c56dccbf4593000376ae275134 from Nov 6, 2017. It doesn't even have the wifi driver defined so we patch it in. The driver blob is from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git dated 2017-09-06

As I said, I can't do anything about how the Pi's wifi works. It's a binary blob so you get what Broadcomm gives you. It's not happening in user space. There might be a newer version available but we'll evaluate that when everything is brought up to the latest version. EDIT: Actually I forgot...