Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[shelly] Motion: Channel motionTimestamp gets always current time #10237

Closed
markus7017 opened this issue Feb 25, 2021 · 0 comments · Fixed by #10220
Closed

[shelly] Motion: Channel motionTimestamp gets always current time #10237

markus7017 opened this issue Feb 25, 2021 · 0 comments · Fixed by #10220
Assignees
@markus7017
Labels
bug An unexpected problem or unintended behavior of an add-on

Comments

@markus7017
Copy link
Contributor

When motion is triggered the CoAP update set the motionTimestamp to the current time rather than the time reported by the device.
@markus7017 markus7017 added the bug An unexpected problem or unintended behavior of an add-on label Feb 25, 2021
@markus7017 markus7017 self-assigned this Feb 25, 2021
@markus7017 markus7017 linked a pull request Feb 26, 2021 that will close this issue
[shelly] Improved Motion Support, Support CoIoT Unicast, fixes #10220
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@markus7017 markus7017

Labels
bug An unexpected problem or unintended behavior of an add-on
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[shelly] Improved Motion Support, Support CoIoT Unicast, fixes markus7017/openhab-addons
1 participant
@markus7017