11-01-2023, 01:01 AM
(This post was last modified: 11-01-2023, 01:01 AM by iliaslamprou.)
Hi,
τhe application does not act as a controller that runs the schedule and sends the state to the controller.
It should only be used to create a schedule and send it to the device.
The "Schedule Display" widget shows us the next schedule time when the state will change.
The Json message contains the time the user sends the schedule.
This may be useful for clock synchronization in case we are connected directly to a device and not through an MQTT broker because the broker may have kept the schedule with an older date than the current one.
I think RTC is necessary in the device.
Widgets are only needed to send a schedule to the device. The device itself should read the correct time from an NTP server and contain an RTC.
τhe application does not act as a controller that runs the schedule and sends the state to the controller.
It should only be used to create a schedule and send it to the device.
The "Schedule Display" widget shows us the next schedule time when the state will change.
The Json message contains the time the user sends the schedule.
This may be useful for clock synchronization in case we are connected directly to a device and not through an MQTT broker because the broker may have kept the schedule with an older date than the current one.
I think RTC is necessary in the device.
Widgets are only needed to send a schedule to the device. The device itself should read the correct time from an NTP server and contain an RTC.