Is there a community repository for Drivers and Apps?


I agree Andy. You and Eric were two of the people I thought would be ReadMe only types. I don't think I'm alone in thinking that when a newbie shows up asking "where?" we have a much simplified answer. "Did you look in HubitatCommunity for more ?"

You've just described my nightmare. I don't want to be running something in my house on an old or buggy version of code.

As for the 'use the top message' agreement - I had never heard of it! . . . this is going to be much better!

There's a category of Getting Started and a tag of Code Share. That's where a lot of code gets released. Followed by discussions, improvements, etc. A lot of the time you'll see the originator say words to the effect of: "I've updated the code and updated message 1 to my github."

for example:

@Cobra said it perfectly and was what I was thinking too. I've seen it for years over on the HomeSeer forums and then on the ST forums. This is a hobby and people LIKE to be a lone wolf hacking away at their code, at their own pace. If other people find it useful, that's great! But most coders write code for themselves first, for fun or just for the challenge and then at some point chose to share it with the rest of us.

In my opinion, all that is needed is similar to what ST has had for years...a simple wiki. Something that can list the developers and a sublist of what they offer. Click on the link and it'll take you to their git. :slight_smile:

This is the ST unofficial wiki: Category:Unpublished SmartApps - Things That Are Smart Wiki


I agree with @bptworld. I think the wiki model that was setup by community members on the ST system is a good start.
It's essentially an index to the various GitHub projects developer's have produced/maintained.
It is also a resource for how to install, configure, etc or whatever information the developer or wiki community think you should know..

This is a link to the site that I think is formatted well to help users connect with community apps/drivers.

Regarding developer vs project organization. I lean heavily toward project based. People look for solutions to their issues or new/neat ways to do things. They don't necessarily want to navigate in/out of developer's to locate projects they may use. I may like so-and-so developer but have no clue that this other developer wrote something that addresses a need/want I have if I only go/search by developer.

1 Like

Being new to this, those links provided by @bptworld and @rayzurbock certainly point to forums which appear to have a better structure. allowing easier accesss to the wealth of information that already exists and is growing.
Whether Developer focused or Project focused, ‘search’ would be my friend :+1:t2:

The GitHub organization that @csteele has created actually can have a wiki, too.

We could create that as well - then it would truly be a one-stop shop. Code and commentary, in wiki format. Reasonable/desirable?

1 Like

I am blown away at the seeming lack of interest on this by the community. Storage in Github would make finding and sharing code so much easier, as well as streamline checking for code updates and managing versioning, I mean look at the multisensor 6 as an example. That sensor has 4 different drivers that I am aware of. Some of those drivers have different versions posted in different locations throughout the forum. Wouldn't it be amazing to be able to go to GitHub, click Multisensor 6, and see all the different driver options in one place?

1 Like

Heh. I hear you, my friend. But organization is expensive, and happens slowly. My hope is that people will do what they wish, and if they see techniques that benefit them - like clear releases, single repositories - they'll use them. And if they don't benefit them, they shouldn't!

I suspect that Hubitat has to come up with a way to organize this stuff if they want there to be a good experience in the long run. I hope they have a plan - someone alluded to it. I'd love to hear about it!

There are little hints here and there, but I don't think any details have been shared.

1 Like

I know I'm new here, but here are my thoughts. The Vera "app store" built into the hub is really convenient. I don't have my Hubitat yet, but I know that on the Vera it's a PITA to manually load a plugin (usually at least 4 files, and then manually creating a parent device). The "store" based thing they have makes it easy.

I see people here are arguing that it's better that they maintain their own repos because they do this as a hobby. That's great, and that's what I do. However, when I'm done with my code, I submit it Vera's repo so it's all packaged up and available through their app store. You could do the same thing here, where devs only upload release code to make it easily available to users via a 1-click install inside the Hubitat UI.

Edit: Another thing to mention here is that Vera does a validation process on your code when you submit it. It generally takes them at least a few days. But, I'm sure it's to look it over and make sure people are doing anything malicious in it, and possibly installing it to make sure it doesn't crash LUUP. Having an official place to get apps from, that are vetted, is eventually going to be a requirement for widespread adoption of the platform. Casual users don't even know what github is. And people installing plugins from unknown sources and having problems is going to reflect badly (from the casual user perspective) on Hubitat itself, not the app developer.


Do you know how they pay for this service? Do app authors pay to have apps in the catalog? Or do users pay to get an app from the catalog? Or do you think they make it part of their overhead?

Overhead. Apps are free and it's free to submit. One of the ways to do it here is to have a committee which consists of Hubitat devs and community volunteers, and then submitted apps are assigned or picked up by members of the committee to vet.

There are also tools that can be used to do some automatic assessment of the code and automated testing to reduce manual overhead.


I think the idea is usually that having a viable ecosystem is an enormous boost for a product (viz the iTunes Store) and worth more than it could ever cost. Nokia, IIRC, tried the approach of charging developers to get into their App Store.

1 Like

I have contributed to both pimatic and openhab, I like the openhab model the best. They used have a public wiki page on their github repo that had different categories that anyone could edit and just a link to their repo in it. (Haven't visited in a while so don't know if that still works). Its totally scalable and self-healing. You put your thing in the category you like and people discover it

Something like this?

1 Like

that is probably good enough for govt use - but the major issue is how do people discover that page unless Hubitat puts in a link for community supported apps and drivers link where its visible. This is the openhab page on their main repo in github @mike.maxwell how about a sticky forum post at the top of shared code section pointing to that wiki or some other permanent self-maintaining page.

@bptworld I guess I should learn how to read again :slight_smile: Yeah this is cool. BTW I can't find the edit button, it says everyone can modify but I dont see an Edit button at the bottom.

1 Like

I think you need your 'Owner' title before you can edit.