[Wiki] HTTP Features and Endpoints

[bobbyD]

@syepes

Exactly, don't test any of this in your main / production Hub

And for that matter, why would you want to keep them in plain sight, maybe remove the links so accidents don't happen?

[lewis.heidrick]

Too late! I already saved em. Had a feeling you'd be around sooner or later.

[neonturbo]

@Evilborg

this probably wouldn't have happened if the HE people had been more forthcoming especially when they aren't giving proper attribution to the open source code/projects they are using which is a license violation.

Bad behavior is rarely if ever an excuse for other poor behavior.

[Hasty1]

Why I think the list of links is a great resource. I also think the point here was to gather useful "undocumented features" With out knowing what they do they aren't really a feature.

[djw1191]

I’m not sure there is any relevance to your thoughts about how they are handling open source projects. These are links to various endpoints in their closed source product.

I don’t think as consumers we are necessarily entitled to know every unpublished and undocumented endpoint. If you’re interested in knowing every possible detail of the software, perhaps it’s time to move onto an actual open source product to serve your home automation needs? Just my .02..

[neonturbo]

@djw1191

I’m not sure there is any relevance to your thoughts about how they are handling open source projects. These are links to various endpoints in their closed source product.

I don’t think as consumers we are necessarily entitled to know every unpublished and undocumented endpoint. If you’re interested in knowing every possible detail of the software, perhaps it’s time to move onto an actual open source product to serve your home automation needs? Just my .02..

Seems like there is some agenda here by certain people to want Hubitat to fail.

[bobbyD]

@lewis.heidrick

Had a feeling you'd be around sooner or later.

LOL. I didn't suggest to remove the post, just the links so it's not a matter of clicking on one of them, and hoping for the best

[kevin]

@neonturbo

Seems like there is some agenda here by certain people to want Hubitat to fail.

I don't see that at all, just be a little more open. Some of the aspects of Hubitat's (reluctance to) release information/code seems unhelpful and overly paranoid and discourages developers who have to publish open source.

If they want to respect people's right to have closed source they should release a mechanism for developers to protect their apps (not something I believe in) ... but open source works two ways.

[Evilborg]

I was only pointing out the resistance to even legit requests that have been relatively ignored....

[lewis.heidrick]

Nah, i have a c5 to play with which is otherwise a potato on a shelf doing nothing.

[Evilborg]

@neonturbo

Seems like there is some agenda here by certain people to want Hubitat to fail.

oh mon frere in fact I would love to see HE dominate the world

@kevin

but open source works two ways.

I absolutely agree with this statement. HE insists you follow their license and rules but they ignore the same when it comes to all the open source code they use in the FW they will not share and attribute that properly.

Many requests for all the open source code they use has been requested more than once and even ignored...

List of open source libraries

Bump. @mike.maxwell do you have the list with licenses and any modifications you have made?

Hubitat OpenSource Driver Repository - Let's Vote!

I agree that they are not going to post their source code, if you've read through some of the other posts by the staff members of Hubitat you will see they don't believe in open source. They are not even meeting the minimum requirements of the open source libraries they are using. Take for instance the h2 database. they are supposed to provide a statement about their usage of it but have not even done that. They have also not posted a list of open source libraries they are using. It is a rea…

Bruce says they don't have the resources to list any open source libraries/code they are using.

Hubitat OpenSource Driver Repository - Let's Vote!

Actually, you missed. We have been aware of this issue, and have taken steps to offer the desired documentation. That effort got sidetracked recently due to resource constraints. Our tardiness in making this available in no way reflects our attitudes about open source software. We do care about open source, as obviously we are a beneficiary of it. The list will be published. We have our business reasons for keeping the source code that we have developed closed. This topic has run its use…

[djw1191]

Like I said, personally I’m not sure if that’s really relevant for this specific item. You’re welcome to be bothered by those other issues, but in this context I don’t see them as related. License terms != unpublished api endpoints.

Pretty much every web based product is going to have undocumented HTTP endpoints and I personally don’t have an expectation that a vendor is going to advertise and tell me all about them. I suppose you’re welcome to try and discover them all.

I think from a support perspective, it can certainly cause issues if people start hitting endpoints without understanding what they do. If anything it, they might be moved to want to gate undocumented functionality behind some sort of config flag to avoid unwanted support headaches.

[bcopeland]

I see some of these are already getting clicked on.. While most are harmless there are some that I wouldn't use unless instructed by Hubitat staff.

[kevin]

@djw1191

These are links to various endpoints in their closed source product

I agree... where I think they could be more helpful is with their driver code. The main code I don't have a particular issue with closed source (assuming they attribute any components accordingly). Closed source is their own business decision.

It's a little unfortunate they seemed to have four prominent coders onboard at formation and now lost two and added two , so still only have four. Leaving things like dashboard stagnating. There are some very knowlegeable people in the community here that could have helped there.

[Evilborg]

I think you are missing the point here.... the resistance to even post attributes to open source libraries/code is more than likely reason the current thread has been created.

The thirst for knowledge is strong.

[bcopeland]

@kevin

4 great coders onboard at formation and now only have three

I'm curious where you are getting your numbers from. There are more than that.

[kevin]

@bcopeland

I'm curious where you are getting your numbers from. There are more than that.

Sorry I forgot one , and edited my post so four.... are there more maybe locked in a cage / less visible ? Losing Chuck 'unannounced' has caused me MQTT issues.

[lewis.heidrick]

I've called a support desk once about 10 years ago. Ended up figuring out the problem on my own before they put me in contact with an engineer. Never bothered with em since.

[bcopeland]

There is even more.. but that is the quantity of developers who are active in the community.. so good guess..

[djw1191]

Haha ok, you do you. I’m not missing anything, just a difference in opinion is all. They aren’t required to document and share every facet of their product is my point, that is completely unrelated to any sort of license requirements.

I enjoy information and tinkering as much as the next guy, I’m just not under the impression that Hubitat is going to share every API endpoint with me.

My opinion has been shared, that was my goal, I’ll conclude my participation at this point.