install VS Commander.js

The middle board looks like you might be able to use the browser based Tasmota installer https://tasmota.github.io/install/ to flash and use however you like. I'm not sure what the config would be after you flash it, though.

Web Installer is up. https://tasmota.github.io/install/.

Its not no soldering but it is low effort soldering. Pulling from a couple guides here.

Tasmota is local first.

Get a wemos D1 and a https://www.ikea.com/us/en/p/vindriktning-air-quality-sensor...

https://tasmota.github.io/install/ flash the unofficial all sensors build.

https://github.com/Hypfer/esp8266-vindriktning-particle-sens... Solder as follows GND to GND on ESP, 5V to 5V on ESP and finally the last one to D2 on the ESP.

Guides I am stealing from. https://github.com/Hypfer/esp8266-vindriktning-particle-sens... Has most of the hardware side. But its using a different software.

https://blakadder.com/vindriktning-tasmota/ is where I got most of the rest of the info but he uses a separate voltage regulator. If you use the Wemos D1 Mini you should not need that.

After that the internet has plenty of info for hooking tasmota and say home assistant together.

Tasmotizer or the Tasmota Web Installer are another couple easy-mode installers. Tasmotizer requires installation, but will allow you to upload a custom bin; not just Tasmota bins. The Tasmota Web Installer doesn't require install, but getting to HAAA will be a two step process: You'll have to upload Tasmota first, then reflash to HAAA.

I use this USB to TTL adapter, but there are tons in the ~$5-10 range that work. I'd stick to genuine FT232RL or CH340G based ones though. Most of the time, you don't even need software anymore, as you can flash straight from Chrome now.

Visit the Commander.js reference.

In the previous article, I looked at a Commander to configure and accept cli options and assign it to a variable called program.

You can write a command line utility using zx or commander.js. Hit a public api, spit stuff out in the console, etc.

In your index.js you can do whatever you want, even create an interactive CLI (check commander).

There is clearly a whole load of repetition, so this should be fairly easy to build and parameterise. Essentially this will all just be string building so we won't need to use any particular libraries for most of this script. We will need a way to call ffmpeg though - and ffmpeg will need to be present too, of course. To call a CLI command we can use the package commander.

Commander.js is an NPM package that makes it easier to build CLI tools. You can find its documentation over here

You can also use npm package commander to make more complex command line tool with lot of options and sub commands.

commander - npm - Required. A library that lets you define the commands and their arguments, options, help, etc.

Throughout my time writing and updating my static-site generator, I've been using npm from the very foundation I use an npm package called commander. Therefore, it is obvious that for the tool that I will be using to publish my ssg, I will do so with npm.

The command line has thousands of tools, such as awk, sed, grep, and find available at your disposal that cut development time and automate tedious tasks. Creating a command line tool in Node.js isn't very complicated, thanks to a powerful library like Commander.js.