To compile against the latest OH master branch source needed to be updated to conform to the requirements; Copyright, Author, Build properties.
Rather than a hardcoded username of 'envoy', added the ability to let the user configure the username the binding uses when authenticating against the Envoy device.
When testing the changes I did see authentication errors, if the binding uses a user/pass that fails than the user/pass is updated to the correct ones the binding still fails, with the below Warning.
Currently the workaround is to restart Openhab. When the server restarts and uses the correct credentials initially no errors are seen and the data is pulled from the Inverters page. If the correct credentials are used initially, the authentication process is successful.
To compile against the latest OH master branch source needed to be updated to conform to the requirements; Copyright, Author, Build properties.
Rather than a hardcoded username of 'envoy', added the ability to let the user configure the username the binding uses when authenticating against the Envoy device.
When testing the changes I did see authentication errors, if the binding uses a user/pass that fails than the user/pass is updated to the correct ones the binding still fails, with the below Warning.
2019-01-08 21:55:31.481 [WARN ] [.e.i.EnphaseEnvoyBridgeHandler:295 ] - envoy scanner update failed: unsupported auth scheme: [���A]Currently the workaround is to restart Openhab. When the server restarts and uses the correct credentials initially no errors are seen and the data is pulled from the Inverters page. If the correct credentials are used initially, the authentication process is successful.