Using OpenAI with Hubitat

🚧 Developers
1

I decided to combine the day job with the night activities by exposing hubitat endpoints to OpenAI's new-ish Assistants API. This allows a user to intelligently interact with the endpoints without having to write much code at all. The demo starts halfway through the video (the first part is explaining what the Assistants API is).

5 Likes
2

Although WAY over my head, great presentation. We are seeing the first real steps to using AI in Home Automation. Hopefully, HE is looking at this very closely.

Now we just need an app!!! lol

3

Thank you for that! The down side of all of this is that it costs money to call an api / large language model. I suspect that at some point people will have household api subscription.

I'd be surprised if you ever saw an app. It costs a lot of money to make and maintain software.

4

This is brilliant. I’ve been thinking about doing something similar. Exposing patterns of motion and door openings and light switches to Open AI to learn and predict future home states.

5

Let me know if I can help in any way. The focus on my presentation was more on the stuff I do in the day job - there is certainly more meat on the proverbial bone when it comes to hubitat.

6

I would be very surprised if someone didn't come up with something. I've been playing around with this endpoint "https://api.openai.com/v1/chat/completions" for months and getting decent results back. And I'm not a professional programmer.

For most here, the cost of creating an app is simply time. Very few charge for that time and freely give their apps to anyone who would like to use them. Myself included.

I agree the cost of using the API is still a road block, but pricing will continue to come down just as it does with each new model.

Now that's what I'm talking about!

:grin:

2 Likes
7

I think the phrase "making software" is very generic. I had assumed that you were talking about an app that would be released as part of the HE platform. Doing something like that requires not just the time to make it, but also a ridiculous amount of time to support it (especially across platforms and scenarios). Its one thing to release a repo to the world and quite another to have a real-world app.