nimble VS esphome

I was using Nim for some of last years Advent of Code problems. I was mostly liking the syntax. Was a bit bother by the standard library have a snake case and camel case reference for each function (if I'm remember that correctly).

At the time nimble also required me to have NPM to install the the Nim package manager, Nimble. This was not ideal, but looking at [the nimble project install docs](https://github.com/nim-lang/nimble#installation) it seems like it is now package with the language.

Might try dusting it off for some AoC puzzles this year :)

nimble develop -g doesn't work A possible solution is to add "g" to where "global" is placed.

I meant it's unfortunate that Nimble has no standard system-wide library management. It's one of the mains thing holding Nim back from being more prevalent in the Linux sphere in my opinion.

`nimble` is the package manager for the programming language `nim` [1].

From [2], we can see that `nimble scss` simply generates the CSS files for the frontend.

The benefit of OSS is you can answer these questions yourself with a bit of poking around! IMO this is a fairly standard installation process, maybe the fact that it's using Nim instead of a more mainstream language makes it look more daunting than it is. The only out-of-the-ordinary thing here, IMO, is `nimble build` instead of `make build`.

[1]: https://github.com/nim-lang/nimble

[2]: https://github.com/zedeus/nitter/blob/master/nitter.nimble

Something I'm excited about: v1.6.2 integrates support for (not yet released) Nimble[1] v0.14, which introduces lockfiles. I've had terrible experiences with lockfiles in JS land, but they are sorely needed for Nim projects as (fingers crossed) they'll allow for reproducible builds without having to resort to the nimbus-build-system[2]. The latter isn't completely horrible — a lot of much appreciated hard work has gone into it, and it's been a real workhorse — but some days it feels like a big ball and chain.

[1] https://github.com/nim-lang/nimble#nimble

[2] https://github.com/status-im/nimbus-build-system

So you wouldn't have a problem with a package manager where the configuration is in the same language, such as Nimble?

if you structure your project with nimble (which can be be used for both libraries and applications) you can use nimble build and nimble run. While I do use nimble for managing dependencies for projects I don't use these commands that often while developing, e.g. because I'm working on a single test or something like that.

Having similar syntax to Ruby makes it easier to port Ruby code to Crystal (ex: digest-crc -> digest-crc.cr). The Crystal stdlib is very complete and they have a growing "shards" ecosystem, roughly the same age as Rust's https://crates.io or Nim's nimble. You should look into Crystal again.

For the ESP32, an hero is in the process of adding LVGL to ESPHome. You can try it out now: https://github.com/esphome/esphome/pull/6363

Here's the (very good!) preview documentation: https://deploy-preview-3678--esphome.netlify.app/components/...

This is such a game-changer for me that I'll be using the ESP32 over the ESP8266 for any projects involving displays from now on.

Solid state relay is probably a bad idea with all the extra heat-sinking, extra cost, and chance of getting counterfeits.

I do this with ESPHome & a J115F21C12VDCS.9 relay (note only the NO side is rated for 40A resistive): https://i.imgur.com/MqqOkoY.png

Choose any of the temperature sensors here for air temperature sensing: https://esphome.io/

Configuration is so easy. For the sensor, just copy the config from here, for example: https://esphome.io/components/sensor/bme280. Add a gpio output (https://esphome.io/components/output/gpio) and a bang-bang climate controller (https://esphome.io/components/climate/bang_bang.html)

You might want to take a look at https://esphome.io/ for an easy integration of an ESP32/8266 into home Assistant.

You can do this with a $30 Sonoff S31 running ESPHome [0]. Since the Sonoff wall switch can run a ping sensor against your server you could create a watchdog automation right on the S31 to shut off the mains power to the S31 switch and turn back on after X seconds.

There are other ways you could have the S31 do operational checks but ultimately ESPHome is probably an interesting consideration and supported by tons of off the shelf hardware.

[0] https://esphome.io/

They're pretty great and compatible with most things. ESPHome [1] is a great resource for getting ESP32's working nicely with HA and you can find lots of projects using it to learn from.

You'll likely need to do soldering if you want to connect sensors, batteries and the like.

Personally I really like what SEEED Studio [2] does with their ESP32 boards and they have nice docs.

1. https://esphome.io/

Maybe you could set up ESPHome on the ESP32. It might make connecting those components easier, plus a decent web server built in. Then your app can be set up to access data provided by the ESPHome web server.

# # Setting pins for sda and scl will be required until https://github.com/esphome/esphome/pull/2970 is released

Probably an unpopular opinion, but for the simple stuff you may just want to use something like EspHome where you just need to create a yaml file. Once you’re comfortable with that maybe get into something a bit more advanced, but esphome make it a breeze. It integrates with home assistant if you already have that in place as well.

ESPHome