Thanks, Victor. That fixed it. Changed the type to "Date" (from "time") on the two app.updateSetting() lines:
app.updateSetting("starting#${device.deviceNetworkId}", [type: "Date", value: timeToString(curfewObject.lock_time, "yyyy-MM-dd'T'HH:mm:ss.SSSXX")])
app.updateSetting("ending#${device.deviceNetworkId}", [type: "Date", value: timeToString(curfewObject.unlock_time, "yyyy-MM-dd'T'HH:mm:ss.SSSXX")])
And the resulting app works on both 2.2.9.146 and 2.3.0.111. Thanks so much. I'll pass this on to Dominick Meglio (@dman2306).
I didn't see anything about change in updateSetting in the release notes.
EDIT:
Unrelated Red Herrings
As a comment, when the hub restarted after I edited these two lines, tested on 2.2.9.146, then tried to update, which spun forever and never began the update process, so I reverted to 2.3.0.111 using the previous version on the Hub, I got the Server Error 500 that Victor addressed in another thread, and the following error appeared in the logs:
Edit: The Excluded attribute hubUpdateResp error by the Dashboard app was caused by Jean May's (@thebearmay's) Hubitat Information driver, due to the fact that his attribute was getting filled with the entire voluminous 2.3.0 Release Notes. He has since updated his driver code to version 2.6.10 (on GitHub and Hubitat Package Manager), and the Excluded attribute error appears no more. This was just a red herring, unrelated to the updateSetting() issue described and fixed in this thread.
A reboot from Settings fixed everything, and now everything is well.
Thanks so much, Victor.
