Closed joreilly closed 1 year ago
So this is a change in the V2 API for Hue Bridges. The devices now use HTTPS certificates for encrypting local traffic. However, since this is a local IP, there is no certificate authority to verify the certificate. By default, Shade defers the validation of the certificate to your system. However, if you have not or cannot manually trust a certificate for the connection on a system level you have other options:
This requires a properties file (default location is ~/.shade-cli.properties
). For this you will need both the hostname id and IP of the hue bridge. Set the security
type to hue
:
security=hue
hostname=01234xxabcdef
ip=192.168.1.5
This is similar to how the V1 API operated. For this you can simply use the --insecure
flag. Or alternatively, set the security
type to insecure
in the properties file. This is, as the name suggests, less secure since it ignores the validity of the http certificate.
For the SDK, there are similar details in the Advanced Initialization section. The properties file is documented in [KDocs](http://shade.lighting/reference/latest/structures/inkapplications.shade.structures/-properties-file-configuration/index.html?query=class%20PropertiesFileConfiguration(file:%20File%20=%20File(%20%20%20%20%20%20%20%20System.getProperty(%22user.home%22)%20%20%20%20%20%20%20%20%20%20%20%20.takeIf%20{%20it.isNullOrEmpty()%20==%20false%20},%20%20%20%20%20%20%20%20%22.shade-cli.properties%22%20%20%20%20))%20:%20HueConfigurationContainer)
I'll keep this ticket open to improve the CLI docs a bit with all of these links. In the CLI docs, It's briefly mentioned here
Shade Info:
Getting following error when using
authorize
(discover
request is working)