Well I don't think OP was trying to help everyone immediately, but he is at least making a start.
The beta API someone threw up on github obviously isn't going to help the average consumer, but it might be the start of a community of enthusiasts. Maybe one day those enthusiasts build a robust system with wider adoption and a company behind it.
If you want something that 'just works', then github is probably not the first place you should look.
> If you want something that 'just works', then github is probably not the first place you should look.
Yes, and that's my point. The expressed problem was that somebody renovating a home looked at a bunch of the options and said that they were too much hassle, too much risk. When somebody says, "This technology doesn't look like something I want to deal with for 20 years," it seems to miss the point to add, "Hey, here's some source code to something even less likely to last 20 years."
I'm not saying it's bad to try write code for fun. I too have a GitHub repository with some dubious home automation code. [1] But as a developer, when a user talks about a problem, I think it's vital to truly listen to the problem and then only talk about a solution if it actually solves something for them.
The beta API someone threw up on github obviously isn't going to help the average consumer, but it might be the start of a community of enthusiasts. Maybe one day those enthusiasts build a robust system with wider adoption and a company behind it.
If you want something that 'just works', then github is probably not the first place you should look.