This is the rule that I noticed wasnāt working:
This is the result:
And this is how it worked before updating this arvo:
Iāve now rolled back to .133 and this fixed the issue for me.
1 Like
Same here.
Seems to only effect the %date% variable in notifications sent from Rule Machine. Notifications sent from the Notifications app seem uneffected.
1 Like
Iām glad itās not my imagination!
1 Like
Was this reported ??
In not in the beta program, so Iām only aware of this forum for reporting bugs.
@bcopeland usually responds to these sort of topics fairly promptly, I just assumed heād had enough of me finding issues in his software and was ignoring me. 
ahh sorry I didnt see that...
1 Like
All good. 
1 Like
I have a similar problem with the use of %time%
1 Like
I had to roll back to .133 as my security logging was basically useless due to the bug.
Iām a little surprised that the Hubitat team seem to be MIA on this issue. Just an acknowledgment would be nice.
1 Like
Replying to follow. Iāve got this in another thread so itās definitely a thing!
Fix is coming.
2 Likes
I realised that if you link to the current known issues thread, itāll show up in the list below the post. Iāll definitely be doing this for confirmed bugs in the future.
1 Like
Hi, I'm still having this issue, even though i've updated to 2.3.8.140.
I'm using Rule Machine to display time and date for when a door has been left open.
I've tried updating this rule, but it still won't display the actual time/date on my Android phone when I get the notification.
I noticed no one else has posted in a while, so I'm wondering is it just me?
Nope, itās still an issue. I think the entire dev team are writing on a new dashboard and mobile app. Hopefully the current bug list will get some attention too.
The fix for this is in 2.3.9, now in beta. All of the recent 2.3.8 releases, since this bug was addressed, have been base system releases without app updates.
2 Likes
