Bug in 2.3.8.134 - notification hub variables time & date broken

dJOS · March 26, 2024, 6:01am

This is the rule that I noticed wasn’t working:

This is the result:

And this is how it worked before updating this arvo:

@bcopeland @gopher.ny @bobbyD

dJOS · March 26, 2024, 10:22am

I’ve now rolled back to .133 and this fixed the issue for me.

a.mcdear · March 27, 2024, 5:04am

Same here.

Seems to only effect the %date% variable in notifications sent from Rule Machine. Notifications sent from the Notifications app seem uneffected.

dJOS · March 27, 2024, 6:02am

I’m glad it’s not my imagination!

Evilborg · March 28, 2024, 5:20am

Was this reported ??

dJOS · March 28, 2024, 5:35am

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.

Evilborg · March 28, 2024, 5:49am

@gopher.ny

You can alert @bravenel also

dJOS · March 28, 2024, 6:04am

I did tag those chaps, minus Bruce.

Evilborg · March 28, 2024, 6:16am

ahh sorry I didnt see that...

dJOS · March 28, 2024, 6:37am

All good.

rvrolyk · March 29, 2024, 12:07am

I have a similar problem with the use of %time%

dJOS · March 29, 2024, 12:11am

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.

@mike.maxwell @support_team

mexpsdw · March 31, 2024, 7:07pm

Replying to follow. I’ve got this in another thread so it’s definitely a thing!

danabw · April 1, 2024, 2:38am

Fix is coming.

dJOS · April 2, 2024, 2:52am

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.