Igniter needs to be cleaned fairly often.Depending on where you live, this could be more expensive than gas or charcoal. Briqs cost around $4 - $8 each and need to be ordered from Spark.At $1,099 for the basic grill package, this is not a cheap grill.But mostly I just like that this thing cooks my food well more or less every time, with very little guesswork or room for human error, while I drink a spritz and chill outside. It's gas but with the taste of charcoal it's charcoal but with the ease of gas. Now I live in a place with a back patio, and since getting a Spark grill last summer, I’ve realized just how much I’ve come to rely on it-and even enjoy cooking on it. At friends’ houses and Airbnbs, gas canisters seemed to always run out as soon as the food hit the grill-with no backup in sight. If you had asked me to describe “the flavor of charcoal” I would say “burnt,” and I could not tell you what was so convenient about gas. Which is all to say, I was not out here looking for a Spark grill, a Bluetooth-enabled “smart grill” that promises the flavor of charcoal with the convenience of gas. Meanwhile I moved from a college dorm room to a series of airless NYC apartments, where the closest I got to grilling was roasting my ass on some fire escape grates. I was in college by the time my parents bought a little Weber, which sat in the garage and got wheeled out for the occasional burger night. I grew up in the suburbs with a backyard-but no grill in sight. I’ve added some documentation on how to track changes in the development branch.Before I became a Spark Grill person, I was not a Grill Person at all. The “develop” branch is already moving ahead:Īs you can see, it’s all made up of “briqs” which can be added and enabled as needed. Let’s see how it evolves, and please do comment and hack on it if you are interested. Which is all a long-winded way of saying that HouseMon is still in its very early stages. There is currently very little error checking and error messages can (will!) be cryptic. Part of the process is getting to grips with complexity: multiple sensor values per reading, “de-multiplexing” different types of packets from the ookRelay, mapping node ID’s to locations, ignoring some repeated data which contains no extra information, and more real-world messiness… This diagram is still too complicated for my tastes. The dotted lines indicate that logged and archived data is being saved but not used yet (logged data is the raw incoming text from serial interfaces, etc – archived data is per-sensor information, aggregated hourly). Here’s an attempt to map out what’s in the 0.5.x release: There seems to be no other way to go through this than just bite bullet, get a basic release out in the wild, and see how it holds up when installed in more places. I suspect that this project will lead to more questions than answers at this stage, but I guess that’s what you get when following the “release early, release often” approach of open source software. After that, all web accesses will be a lot snappier than in development mode.īut let’s not get ahead of ourselves… tons of work to do before HM becomes useful! To get an idea of the true performance on a Raspberry Pi, you should start up as follows (make sure HouseMon is not running already): cd ~/housemon & SS_ENV=production node app.js – this’ll take a few minutes while SocketStream combines and “minifies” everything the first time around. Note that the instructions so far were all about development. It feels a bit odd to give this piece a software a version number, since it’s all so early still, but I’m releasing it as HouseMon 0.5.1 anyway, to set a baseline for future development.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |