Bug in new UI preferences pages.. time inputs not working

submit of preferences with a time variable does not work.. the save and save and close do nothing.. no errors in logs whatsoever..

@bravenel

1 Like

this does not work.. have your tried it.

input "toTime", "time", title: "To", required:false

it works the first time.. them puts some huge time number in the field and then no matter what you do never works agian..

i just tested and added to various device handlers and same issue.

1 Like

ya i am not talking about variable connectors probably related.. i am talking about an input preference direct in a device handler.

doesnt matter.l. found in tesla driver. but as i said i added the preference line to two other drivers .. just for testing and had the same issue.

someone else mentioned that time may no longer be a valid input type.. as it is no longer in the docs.. which is really going to make it hard to code arouund that.. guess ill will need 4 number types from fromtime and totime
hours minutes and have to convert what a pain in the ■■■..

i did not enter the date time above.. i used the picker and it had something like 10 : 00

on submit it changed to that huge date time which is why i think it breaks..

1 Like

I noticed this change months ago. I have some custom apps that take times in settings, and they broke last fall with some update, before 2.4. I found that time was now giving me a different time string when things broke.

I was parsing the time string to create schedules, and my parser broke due to the change. I rewrote my parser to use the new format, but I wish I had of known then that I could have just switched to using datetime, as I think time used to just return the standard datetime string for the current day.

1 Like

i am sure datetime is a good so=olution that is not documented as a valid input preference.. we really need hubitat to fix this

@gopher.ny

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.