Luuk Wester
Luuk Wester
Alright! I think I can come up with a PR to rework some of the internals and add support for groups one of these days. I'd also like to add...
Alright, I'll try to make a couple of smaller PR's, but I might have to wait until they get accepted, or fork off them to create the next PR then.
Seems great so far :smiley:
I went through some online docs I found and I implemented the "config", "group" and "schedule" API's, but I can't seem to find docs pertaining to scenes. Did you ever...
I don't think that that is true. If i create a scene on one device, I can see and activate that scene from another device as well.
I'm implementing support for schedules currently, and since the documentation is a bit lacking I am looking at the JSON for schedules and I noticed this command performed my one...
No I haven't been able to find a truly comprehensive source that explains which fields are required and which are not, so the current implementation is on a best-effort basis....
Sure this seems like a reasonable enhancement. Two issues come to mind about implementing this, namely that it requires a breaking change to almost every function in the library if...
Sure but the downside would then be that we have to duplicate almost all functions: `Bucket::create_with_headers`, `Bucket::update_with_headers`, ... Maybe that we can create a function like `Client::set_headers`, with the new...
Right that sounds feasible. As a contributor, do you have an idea about how we could best integrate such a library?