HS4 Beta 4.2.0.5 is available

[Paul32]

Did you have the 24 HR log setting in setup unchecked? I tested this with that setting unchecked and it displayed the date correctly (using your format). If you enable the 24 HR log format it formats the date as you are seeing. I guess I could change that to force the date to use the system format but force the time to be 24HR if checked.

Checked and unchecked, both is 24hrs.
P.S. For me it’s not a problem, but the change log suggests that 24hrs should be gone…

[HansSchouten]

So it looks like for your case you would want to keep the 24HR setting unchecked and use your system format, correct? The 24HR setting was put there for users who only want the log in 24HR format but want the system format for all other output. If someone actually wants the log in 24HR time format but wants the date in a different format (or maybe the system format), I would need to make a change. So far I am not aware of that request. But it does make sense to leave the date in the system format and just force the time to 24HR if the setting is enabled.

"So it looks like for your case you would want to keep the 24HR setting unchecked and use your system format, correct?" Yes, that's correct!

You don't have to change anything for me. I leave the 24HR setting unchecked.
Thanks for your quick response.

Regards, Hans

[rjh]

It was removed then put back in for 4.2.0.5. If your regional time setting is set to 24HR then you won't see a change with this setting.

Checked and unchecked, both is 24hrs.
P.S. For me it’s not a problem, but the change log suggests that 24hrs should be gone…

[ahuefner]

This beta release corrected and issue that showed up after installing v4.2. 4.2 caused my UltraM1G plugin to malfunction. With 4.2, TASKs in my ELK security system were automatically activating when the trigger for the event that use to be needed to activate them occurred without any event action. The events that were used to control activation of the ELK TASKS, resulted in a second activation. Some triggers were causing the wrong ELK to be activated. Upgrading to HS4 v4.2.0.5 corrected this condition which requires an event to activate a ELK TASK.

[stefxx]

So it looks like for your case you would want to keep the 24HR setting unchecked and use your system format, correct? The 24HR setting was put there for users who only want the log in 24HR format but want the system format for all other output. If someone actually wants the log in 24HR time format but wants the date in a different format (or maybe the system format), I would need to make a change. So far I am not aware of that request. But it does make sense to leave the date in the system format and just force the time to 24HR if the setting is enabled.

I come from the same country as HansSchouten. I always assumed the log date format was a bug, since I had the "Use 24HR Time Format" enabled as long as I can remember (which in my mind made sense since that is what I wanted). I just disabled it and now the log date AND time format are correct. Thanks!

I suggest to set the date format according to the system setting, regardless of the "Use 24HR" setting. And maybe make that setting a bit more clear ("Use 24HR time format regardless of system settings"?).

Thanks!

[ServiceXp]

So is this a bug (I submitted this to HST), or just something that isn't possible now?

1) Created a Virtual Device, with among others, includes numeric text box features (See pics below).
2) You cannot use the features in an event as the value return "Missing". (See pics below)
3) If you go into the old HS3 Device Management page, you can tick the "Include Value" option and you will then be presented with values to choose from.(See pics below)

4) BUT, you cannot set the features value from an event. Nothing happens.

[rjh]

I will log this and put in a fix.

So is this a bug (I submitted this to HST), or just something that isn't possible now?

1) Created a Virtual Device, with among others, includes numeric text box features (See pics below).
2) You cannot use the features in an event as the value return "Missing". (See pics below)
3) If you go into the old HS3 Device Management page, you can tick the "Include Value" option and you will then be presented with values to choose from.(See pics below)

4) BUT, you cannot set the features value from an event. Nothing happens.

[ServiceXp]

I will log this and put in a fix.

Thank You, After debugging my events for quite some time, I thought I was going crazy.. Well, perhaps that is still true..