The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Iot_devices Alternatives
Similar projects and alternatives to iot_devices
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
realworld
"The mother of all demo apps" — Exemplary fullstack Medium.com clone powered by React, Angular, Node, Django, and many more
-
PixiJS
The HTML5 Creation Engine: Create beautiful digital content with the fastest, most flexible 2D WebGL renderer.
-
Filestash
🦄 A modern web client for SFTP, S3, FTP, WebDAV, Git, Minio, LDAP, CalDAV, CardDAV, Mysql, Backblaze, ...
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
todomvc
Helping you select an MV* framework - Todo apps for React.js, Ember.js, Angular, and many more
-
mnm
mnm implements TMTP protocol. Let Internet sites message members directly, instead of unreliable, insecure email. Contributors welcome! (Server)
-
awayto
Awayto is a curated development platform, producing great value with minimal investment. With all the ways there are to reach a solution, it's important to understand the landscape of tools to use.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
iot_devices reviews and mentions
-
Ask HN: Tell us about your project that's not done yet but you want feedback on
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.
-
How I wrote my own Smart Home software
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.
-
Ask HN: Who Wants to Collaborate?
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.
-
Home automation dashboard generator in the terminal
Source code can be found here: https://github.com/EternityForest/iot_devices
- Minimalistic framework for creating IoT reusable Python IoT device drivers
-
A note from our sponsor - WorkOS
workos.com | 19 Apr 2024
Stats
EternityForest/iot_devices is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of iot_devices is Python.