Fix geocoded crash, report expected minimum accuracy for location #832
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.
Fixes: #830
Also fixes a edge case where sometimes we were sending an invalid
gps_accuracy
attribute which was less than 0.Example error from HA:
Received invalid webhook payload: value must be at least 0 for dictionary value @ data['gps_accuracy']. Got -2147478
andReceived invalid webhook payload: value must be at least 0 for dictionary value @ data['gps_accuracy']. Got -2147471
During these errors all updates do not come through so when we detect that accuracy >= 0 we will send the real value, otherwise we will send
0
which is the bare minimum that HA will accept