-
Notifications
You must be signed in to change notification settings - Fork 73
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.
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
The Device telemetry display stops around midnight #569
Comments
Hi @KiwiBryn |
Hi @YingXue I have run Azure IoT explorer since DST change and it stopped. Will run again tonight to double check |
We made a new release with updated Event Hub SDK: |
Hi
It's 7:am here in NZ, will try tonight so there will be a delay
Bryn
…________________________________
From: YingXue ***@***.***>
Sent: Tuesday, November 22, 2022 7:13:49 AM
To: Azure/azure-iot-explorer ***@***.***>
Cc: Bryn Lewis ***@***.***>; Mention ***@***.***>
Subject: Re: [Azure/azure-iot-explorer] The Device telemetry display stops around midnight (Issue #569)
We made a new release with updated Event Hub SDK:
https://github.com/Azure/azure-iot-explorer/releases/tag/v0.15.2
Haven't got a chance to verify at midnight myself, but simply want to share an update.
If you got to verify the fix before I do, I would much appreciate an update :)
—
Reply to this email directly, view it on GitHub<#569 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADB7JOKTCB4JR7ASWMEIFFLWJO3V3ANCNFSM6AAAAAARYVAU4I>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi Tried 3 or 4 times, still failing just before midnight. Bryn |
Hi Not certain if this is related? This had happened overnight not certain when. Sorry about multiple screen captures the dialog box was quite tall. Didn't noticed the one with the message box initially |
Describe the bug
The device telemetry stops around midnight. I sometimes(yeah right) work late and if I leave Azure IoT Explorer running telemetry appears to stop just before midnight (roughly half the duration of the gap between updates). If I stop then restart telemetry it starts working
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should run over midnight
Screenshots
This is snip of screen following morning. If I restart telemetry updates start working
Desktop (please complete the following information):
Additional context
New Zealand is currently UTC+13 because of daylight savings time. I really hope I'm not wasting your time
The text was updated successfully, but these errors were encountered: