Display Error - Alarm Rules Scheduler
Describe the bug Display errors have been identified in the Alarm Rules scheduler when specific time intervals are selected. As of today, we cannot yet say whether these are merely display errors or if alarm processing is also affected; we will continue to investigate this over the next few days.
Your Server Environment
- own setup
- Deployment: monolith and microservices
- Deployment type: deb, k8s
- ThingsBoard Version 4.3.1.3.
- Professional Edition
Your Client Environment
Desktop (please complete the following information):
To Reproduce Steps to reproduce the behavior:
- Create a new Alarm Rule & Enter a Alarm type name
- Select Device Profile and Arguments
- In the Trigger conditions section go to Schedule
- Enter specific time intervals & observe Display Errors
Expected behavior There are no display errors for specific time intervals, which may confuse users.
Screenshots We have set alarms from 8:00 p.m. to 5:00 a.m. The display shows an alarm from 12 a.m. (12:00 a.m.) to 5 a.m. (5:00 a.m.; that's correct) and from 8 p.m. (8:00 p.m.) to 12 p.m. (12:00 p.m.—noon).
Additional tests: 00:00 to 00:00 is displayed as 12 a.m. to 12:00 p.m. - ERROR
From 00:00. to 12:00 works.
From 12:00 p.m. to 12:00 p.m. displayed as: 12:00 a.m. to 12:00 p.m. and 12:00 p.m. to 12:00 p.m. – ERROR.
Disclaimer
We appreciate your contribution whether it is a bug report, feature request, or pull request with improvement (hopefully). Please comply with the Community ethics policy, and do not expect us to answer your requests immediately. Also, do not treat GitHub issues as a support channel.
Source: thingsboard/thingsboard