(I know: stupid question. But here goes.)
I'm double checking myself as I am still not 100% sure.
I have (or will have) devices connected which will want to know the time.
They may not need to know it every second but at ..... intervals. Or maybe a one off, every now and then.
So, I set up a
MQTT channel listening for 'time requests'. At this stage the message will be formatted so: --IP address-- --interval--
(Sorry formatting didn't like my use of < and >)
This is so the time message can be sent to that device rather than a broadcast.
But the nature of MQTT it doesn't really matter, does it.
I can just set up a
MQTT TIME channel and when ever a period has passed, the time gets published.
There is no savings in overheads sending it to a specific device on a specific channel because it will go everywhere all the same.
So really the IP address is redundant. Needed only if that request is no longer needed and the interval can be removed from the list of publishes.
(Just wanting a sanity check.)