sbts-install VS iot_devices

Back in 2011 I made a commercial product that ran on the earliest plug computers from global scale technologies. I only sold 20 of 'em and every single one of them was being returned with SD card corruption problems. I had to quickly pivot to keeping the rootfs read-only. I've been a fan ever since.

Incidentally, that early commercial product was a home security product with a very small amount of home automation. I released this into open source with a new name in 2021 and now runs on the Jetson series SBCs (https://github.com/hcfman/sbts-install). Except then including high end YOLO models as triggers.

Because it was intended to be a standalone product it supported https with a GUI wrapper around all of the certificate operations. This still exists in my open source version, making it easy to use self signed certificates for intra-device rest calls.

But I've kept and expanded upon the multi-partition memory overlayFS approach and the installation of this system first asks you to install the sbts-base system, which installs the multi-partition memory overlayFS so that other's can use this as their own base systems.

Is anyone else using the StalkedByTheState security system? It runs on Jetson SBCs and works with the full sized yolov6 and yolov7 models.

Super proactive detection and response

https://github.com/hcfman/sbts-install

I use StalkedByTheState (https://github.com/hcfman/sbts-install) with 15 cameras all being evaluated with an NVIDIA GPU with large model yolov6 and matches double checked with large yolov7. Practically never get a false positive in a complex environment and never get a miss. The port to the Orin series still needs to be completed though.

Sweet! If you are prepared to spend more for more GPU compute power from Jetson SBCs you could use larger models. I’m busy adding the

https://www.deepfaune.cnrs.fr/

model to my security system software

https://github.com/hcfman/sbts-install

It’s almost there but still have to finish the install scripts for the Orin series.

The deep fauna model can be used for all of France’s fauna which includes foxes and badgers (and wolves, bears, lynxes and more of course).

Nice that you should say that :) I also wrote a home automation system.

Well... actually, it's a kinda burglar alarm except it's focus is alerting way ahead of actually getting inside. I added home automation bits (minimal) just so one can elicit a real world response, but I do use it for minimal home automation (Lights, heating control and letting the chickens in and out).

I have yet to announce on on hacker news and so because I still have to write a bunch of documentation. It uses the latest state of the art computer vision triggering, currently yolov7 and I'm about to release support for yolov6. It's multimodel, so you can double check it's result with more than one model, even for specific parts of an image.

The architecture diagam and installation instructions are here:

https://github.com/hcfman/sbts-install

I actually, started writing this in 2008 and most of the current state in terms of the user interface were finished in 2012 but I only released it into open source last year really. In 2019 I add support for yolov3 and have been adding models even since.

It's written in Java and installs in just two commands on nvidia jetsons at the moment (Not in containers). The inference framework is a simple websocket based wrapper around other models so it's easy to add new models and that's written in python.

Well I finish the new release to introduce yolov6 and support for the seeed studios platforms I'll make an announcement on hacker news, note I still have a lot of work to do on documentation.

Wow, what a great idea for a thread!

I'm trying to pare down my personal projects to just the really exciting ones, so I don't have much, butni think the most appropriate to the thread is https://github.com/EternityForest/iot_devices

It's mean to be a cross-framework library for creating device integrations, so you can, say, write a handler for RTL SDR weather stations, and use it in a simple script up to a mega framework.

I kind of dislike the way HASS and others handle automations where they have special purpose primitives for everything that needs lots of hand written code.

I just have config entries, they must be strings, and data points, they can be strings, numbers, bytes, or objects. You can put metadata on them. There's also a few other utilities like the ability to make subdevices, and the ability to request things from the host.

There are no special subclasses, a light bulb is just a device with a brightness point.

It currently runs my security system with object detection recording, QR decoding if desired, multiple regions, motion detection without decoding every frame, and subsecond latency streaming to the browser, a nice recordings browser that can view a recording while it's being made, etc.

My HA platform project started in 2013. Every few months or so I check back to see if HA has progressed far enough that I can ditch one of the last custom apps in my life.

It's getting there. But it's not quite there yet. Last I checked the logging still saves every change, it's not easy to set up so that it will only save average/min/max over time to save SD wear.

Creating new integrations is easy but still not quite a five minute job like it is with my extension API(https://github.com/EternityForest/iot_devices)

But yet, having custom software in one's life is generally IMHO far more of a liability than an asset.

So what I actually do is just use YoLink and Google assistant for everything I possibly can, and use custom software for video recording and unusual stuff YoLink doesn't do.

I'd love to have a one size fits all "If it need automating, use this" platform, and HA seems like it's got the potential.... but just using the YoLink proprietary platform is the lazy, trouble free, super cheap way.

I'm working on a standard for easy drop-in home IoT drivers: https://github.com/EternityForest/iot_devices

Maybe you could go one level of meta up and instead of working on reusable components, work on reusable definitions for component interfaces.

Reuse is hard because you need a bunch of glue code. But if you had, like a standard for a toolbar, that knew how to find all the ToolbarAble objects, and the shopping cart icon just showed up, etc, things would get easier.

The shopping cart could know to look for all the payment requesting components declared in your Big Project File or whatever, and everything could stay modular ish?

GitHub is already the standard place to share generic projects.

Source code can be found here: https://github.com/EternityForest/iot_devices