Merry Christmas! I’m sorry for the inconvenience. I’ll do my best to provide a solution for you as fast as possible.
I’ve now created a GitHub issue for this bug. If you have a GitHub account we can add additional information to this issue, otherwise we can continue in this thread and I’ll update the issue with any relevant information. Let me know what you prefer.
In order to provide a good fix for this I would ask you to try these URL’s in a web browser:
http:///api/fwversion
http:///api/sceneCollections/
http:///api/scheduledevents
The first response will make it possible for me to determine which Hub version and/or firmware you are using, which can be used by the binding to determine which features to support.
The next two requests is a test of availability of two specific features.
Next, do you know the feature Scene Groups from the PowerView app? Have you ever been able to create scene groups, i.e. a special type of sceres containing other scenes?
Last, are you able to use automations with your hub?
Short update, I’ve provided a first version of a fix. Please see the GitHub issue for link.
I you have additional time and strength, please have a look at my comment about sniffing packets from the Android app. If one of you would be able to pull this off, I should be able to correctly support scene groups for Hub v1.
@mark_leonard_tuil - above will not be needed. With help from @Jeevs I was able find the root cause for this issue with the v1 hub. JAR is available here..