This repository has been archived by the owner on Jan 15, 2024. It is now read-only.
Implemented the /profile API for user profile data parsing #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Dont use the /profiles API to try to match username to profile as this is no longer possible in Z-Way v2.3.7. The undocumented /session API is much better for this purpose.
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
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 Z-Way API exposes an undocumented /session point which contains user information of the currently authenticated user including dashboard devices. This should be used instead of the qrcode parsing hack we previously used which is no longer possible on Z-Way 2.3.7.
This closes #1