Changes I'm working on and zwave clocks

[ash77]

I'm currently working on extensive refactoring and usability improvements to Domoticz, and I will be starting discussions about a variety of topics to help guide the changes I'm making.

First question is for users with zwave devices with a clock (only example I know of is thermostats). Domoticz shows a clock device with a dialog to select the day of week, hour, and minute. It then sets the time to what you entered. I think this is the wrong approach. The computer should already know the correct time, so I think there should just be a button to set the time, and the Domoticz server can use the time it already has.

I can think of only two reasons this wouldn't be better:
1. The user wants to deliberately set the thermostat to the wrong time, but why would someone want to do that?
2. The thermostat is in a different time zone, which would only apply to Razberry. In this case, however, the server would be configured with the clock's time zone, and it can still use its internal time.

What do you think about a button instead?

[nayr]

uh, Domoticz knows the correct time and it is the one controlling things.. it has really no impact if your thermostat clock is correct or not.

My Thermostat clock has never been correct in 3 years, and its never bothered me a single bit.. but the device is exposed so if you wanted to write a lua script to send the correct time every few hours then go for it.. why modify the core behavior, if you want to help.. improve functionality that people actually use.

There is no need to make it a switch type device and have a button do anything.. if you want to do something automatically, write a script.