Based on your other posts, I'm going to assume you have a firewall or other network configuration blocking your hub from reaching its default NTP servers on the Internet. To avoid this drift, you'll either need to figure out and fix that or change it manually to local NTP servers you can access, using instructions like these: Issues in 2.2.4 Latest - #7 by gopher.ny
Your Room Lighting setup has almost no configuration. You're telling to to vary by time period, but you don't need that if all you want to do is "Activate" at some time and "Turn off" at some other time. But even if you do, you don't actually have any time periods configured on your Set Up Lighting Periods page. I'd guess this might just use your same, only settings all the time then, but I'm thinking it might actually do nothing at all, as your table on the main page is blank, and I believe that will normally show what it would do right now if it were to activate. So, I'd start by disabling time periods entirely -- there's no reason to use this setting in the first place if you don't really need it -- though you could also actually configure one (typically more than one) if you do.
You'd need this setting if you want to do different "activation" settings at different times of day. You don't need it just to turn something on at some time every day. For that matter, RL itself is a bit overkill for this kind of automation if you only have one device, as you could use Basic Rule or other options to get the same result. (It can be nice if you have multiple devices to configure, more nuanced configuration needed, or want to use Zigbee Group Messaging as you might if you're controlling multiple Sengled bulbs in unison.)
Looks like that is just the time that you installed the RL app and created this child device, which got initialized to a set of default values -- not a problem.
