Author Topic: DateTime Formatting Bug?  (Read 612 times)

Offline edgebinary

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +0/-0
DateTime Formatting Bug?
« on: February 26, 2018, 10:34:20 pm »
Richard,

I'm currently writing this in the message section of a standard vera alert notification: {DateTime(CurrentTime,%A %B %d, %Y at %H:%M)}
However, when I save the scene, run it, it says this, literally: {DateTime(CurrentTime, f i, d at m:>)}

When I go back in and check the scene, it looks like: {DateTime(CurrentTime, f i, d at m:>)}

{DateTime(CurrentTime %H:%M)} turns into {DateTime(CurrentTime s:h)}

I am on firmware version 1.7.3015 with VeraPlus. The weirdest thing is that I have this working on another scene, but I'm too afraid to start editing it because I may be in the same boat after I tinker with it. This all started a few days ago when I removed a little bit of text from the alert and saved.

Any thoughts?

Offline edgebinary

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +0/-0
Re: DateTime Formatting Bug?
« Reply #1 on: February 27, 2018, 07:13:39 pm »
I updated to the latest firmware. Still have the same issue. Now when I go to create a new scene with this DateTime format string in it, they don't even show up on the scenes tab.

Offline edgebinary

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +0/-0
Re: DateTime Formatting Bug?
« Reply #2 on: February 27, 2018, 07:53:54 pm »
When I entered this into a vera alert notification: {tone:2}{BGColor:Green}Welcome home, Nathaniel. The local time is {DateTime(CurrentTime %H)}

This is what I got when I tailed /var/log/cmh/LuaUPnP.log:


01      02/27/18 19:49:14.100   sbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfo <0x77285520>
08      02/27/18 19:49:14.101   JobHandler_LuaUPnP::HandleActionRequest device: 43 service: urn:richardgreen:serviceId:VeraAlert1 action: SendAlert <0x77285520>
08      02/27/18 19:49:14.101   JobHandler_LuaUPnP::HandleActionRequest argument Message={tone:2}{BGColor:Green}Welcome home, Nathaniel. The local time is {DateTime(CurrentTime e)} <0x77285520>
08      02/27/18 19:49:14.101   JobHandler_LuaUPnP::HandleActionRequest argument Recipients=nathaniel <0x77285520>
08      02/27/18 19:49:14.102   JobHandler_LuaUPnP::HandleActionRequest argument HouseModeMask= <0x77285520>
06      02/27/18 19:49:14.453   Device_Variable::m_szValue_set device: 43 service: urn:richardgreen:serviceId:VeraAlert1 variable: LastMsgSent was: 19:46:41 Tue Feb 27 now: 19:49:14 Tue Feb 27 #hooks: 0 upnp: 0 skip: 0 v:0x12d3348/NONE duplicate:0 <0x77e36320>
04      02/27/18 19:49:14.465   <Job ID="10" Name="" Device="43" Created="2018-02-27 19:49:14" Started="2018-02-27 19:49:14" Completed="2018-02-27 19:49:14" Duration="0.360865000" Runtime="0.360331000" Status="Successful" LastNote=""/> <0x77e36320>

Offline edgebinary

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +0/-0
Re: DateTime Formatting Bug?
« Reply #3 on: May 21, 2018, 09:38:12 pm »
Richard, are you alive, buddy? Got any words of wisdom for me?

Offline RichardTSchaefer

  • Moderator
  • Master Member
  • *****
  • Posts: 10059
  • Karma: +759/-141
Re: DateTime Formatting Bug?
« Reply #4 on: May 21, 2018, 11:10:13 pm »
I entered your time strings into "Send Alert Now" from Vera Alerts ... all worked as expected.

Offline edgebinary

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +0/-0
Re: DateTime Formatting Bug?
« Reply #5 on: May 22, 2018, 06:17:33 pm »
The Send now function it works fine, Richard. Try creating a scene with it.

Offline edgebinary

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +0/-0
Re: DateTime Formatting Bug?
« Reply #6 on: May 30, 2018, 04:19:59 pm »
I entered your time strings into "Send Alert Now" from Vera Alerts ... all worked as expected.

Richard, try creating an actual scene with it. It works fine in the "Send Alert Now," but not in scenes.