quarter VS iot_devices

I am working on a personal time-tracker where I try to make it as effortless as possible to keep track of what activities you spend time on.

Rationale, as a consultant I am often required to use multiple time-tracking software, all made for accountants, all terrible to use. I made this little web application where I can track my daily activities and at the end of the week transfer the result to whatever system needed.

The desktop is the most polished mode, mobile is functional but I mostly use if for viewing.

It's open source, the hosted version has open registrations given a GitHub or GMail account.

I would appreciate feedback on basically anything. I have been using the same system (during many different rewrites) for years so I am pretty blind to what needs improvement.

https://github.com/eliasson/quarter

https://quarterapp.com/

Thanks!

I have this hobby project for personal time tracking I work on from time to time. It's usable enough for my daily use so motivation has dropped since that point.

https://github.com/eliasson/quarter

I've used QuarterApp for personal time tracking. Not sure if it has grouping features though: https://github.com/eliasson/quarter

It has now reached a point where I think it could be of use or interest for others. You can find it here if you're interested https://github.com/eliasson/quarter

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