Fix issues accessing the ZHA gateway #252
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The gateway could now also be a gateway proxy object that stores the HASS object under
hass
instead of_hass
and the HASS object is no longer available in the non-proxy object since it lives in the new ZHA (non-HA) library.Having access to the proxy object is useful to get the
hass
object, but accessing the application controller needs to be done through the actual gateway. Therefore, a helper method has been added with simple duck-type checking to reach the gateway through thegateway
property of the proxy.Fixes: #251