Same exact issue as @terminal3 here... but check out the "in use by". Something is super squirrelly.
So I decided to just go recreate all of our alarms under the new RM5.0 and hub variables system. It's a bit of a mess. Maybe I'm doing something wrong, because it sure feels that way.
I get an invalid date on the dashboard unless I set a date, but if I don't set the date carefully, DST seems to come into play?
Edit: It appears that I can't actually change the date from the dashboard if I set the tile to Variable Date.
FYI the variables and rules that use them seem to working fine, I just can't change the value on the dashboard.
OK, this is a different issue affecting the dashboard, we'll look into it.
2 Likes
+1 on the dashboard tiles showing the current time, not the time from the connector (to an RM Legacy time variable)
The connector device shows the right time.
Now my dashboard won't display a date time at all. I updated to 2.2.8.138 last night. Thinking back I don't think I ever went and looked at the dashboard tile so I guess that broke it. I had decided I would just move the rule over to RM 5.0. I created a timedate hub variable and made it a connector. I then added it to my dashboard so I could see how it looked. I assume it was the firmware update and not the adding of a hub variable that broke the dashboard.
The hub variable only can be a datetime, and my current RM legacy rule uses a global time only variable so I was going to have to make some changes to my rule. It won't display the HUB or legacy global variable on the dashboard.
It creates a space that is being occupied by a tile but you can't edit or remove it from the dashboard, see below.
Try setting the tile to a variable string for now. That's what I'm doing as a temp fix till it's solved.
1 Like
It's not something I edit that often and otherwise the rule is working. So I will just give it a few days and see if they get it fixed. I can still edit via the hub variable page if I really need to.
I have two tiles one for Sunrise time and one for Sunset time . The cloud dashboard on the mobile app shows the current time, the local dashboard on the mobile app shows the correct information. I am still on 2.2.7.138. Mobile App version 1.2.1 IOS. Might not be related but similar issues.
Can you try again for cloud dashboard?
My dashboards are working now.
1 Like
@moncho1138 everything is displaying much better, but when I attempt to edit a DateTime variable without a date, the inserted text still shows an error.
Also, the issue where DST seems to impact the interface on the hub is still present. See the Value in the table vs the editable value in the field below.
The cloud dashboard is working now.
1 Like
I got the following when I tried to update the time on a dashboard tile:
I'm trying to get a time into aconnector-variable to use in a legacy RM. This setup worked great before.
2.2.8-141 C7
Please try again with new build 143
Still not working here on local dash.
DateTime variables accessed via Variable Time on the dashboard seem to be working correctly on the dashboard when no date is applied, but there is still an issue when both a time and date are entered.
In the screenshot below, I manually entered 06:30 AM am on each tile, but the connector tile on the right is displaying 5:30 am. When I change the date to today, it displays the time correctly.
A related issue is also present in the RM5 display. If I delete the date entirely a 6:30 am value is shown as 5:30 am. I'll have to see what time it actually goes off with a test rule that isn't waking me up an hour earlier than I expect it to!
We know there is a bug in this release causing this. We will get it sorted.
3 Likes
Would this known bug also cause a date/time parsing error in RM5?
Context: I have a RM4 rule that sets a color temperature fade twice a day using a virtual dimmer. At sunrise, it starts to fade the dimmer up from 0 to 100 until noon. And at noon, it fades the dimmer down from 100 to 0 until sundown. Idea is to have this dimmer track to the circadian rhythm. I then use this virtual dimmer to set color temperature by bulb type throughout the house. Worked great for awhile!
Recently it stopped working. I’m getting the below error. I suspect this has to do with the time variable now including date. Could that be right? If so, will this error go away when you solve the bug you mention above, or do I need to use different logic to calculate time difference now that time variable includes date? I’ve also pasted the rule at the bottom of the thread.
app:2612021-07-29 11:40:46.942 pmerrorjava.time.format.DateTimeParseException: Text '9999-99-99T12:00:00.000-04:00' could not be parsed: Invalid value for MonthOfYear (valid values 1 - 12): 99 on line 6610 (method appButtonHandler)
Two questions:
- Have you updated to 2.2.8.145? If not please do so, as it had fixes for this error (if Rule-4.1 or Rule 5.0).
- Is this rule a Rule-4.1, Rule-4.0, or Rule 5.0?
