Jump to content

Time discrepancies in UD mobile vs ISY?


dbwarner5

Recommended Posts

Posted

I have. program that sends me text with certain integer values. The texts are arriving each hour and time stamped when received per the text system. 

The last one I receive at night is before 11pm and reported a value for one of the variable as 94. See below. Text is at 9:06pmEastern:  (the 9:02 in the upper left is 9:02am the next day when I took the screenshot)

IMG_441C79589690-1.thumb.jpeg.f9a466c43b5e741aaa1f56dfe93b0b80.jpeg

 

However at 12:17am (next day), I checked my UD mobile to see what the value was. It had increased as expected, however the time it notes as "last changed" is at 6:59pm, which is BEFORE the above text and is incorrect. Is UD mobile defaulting to west coast time, or other? The time in my ISY is correct. (eastern). See below screen shot. 

IMG_6C6DA200BF85-1.thumb.jpeg.ee288d3230603facde37766661a9e6f0.jpeg

Posted

Hi @dbwarner5,

This time is published by the ISY as a string and not modified by UD Mobile.  You may notice there are two formats as the REST and Subscription strings differ.   The times should match the last run time in the Admin Console. 

Sometimes messages via email, or email to carrier to sms,  can be delayed or arrive out of order.  In my personal use I add a timestamp the message, although it is not needed as much now with Push Over. When I was using the email to sms for my messages some would arrived 12-18 hours late.

Also be sure you are on the latest firmware as I recall the time being an issue in previous firmware versions.

  • Like 1
Posted

agree with the time stamp. I have added that as well and switched to pushover for the notification, but it still doesn't explain the time stamp of the UD mobile variable. The text messages were coming in regularly every hour as expected and increasing with time as expected. 

The value of the NS integer was the correct ending day value, but the time showed it changed at 6:59pm, which I know is 100% incorrect. 

Posted

@Javi please look at the screen shots attached. The problem is not with UD Mobile as I originally thought. It appears that the ISY is using GMT time for variable changes, which is the time that UD mobile is picking up as you suggested. 

Look at the two variables: I_Thermostat_ML_Minutes and I_Thermostat_UP_Minutes.

These variables increment by 1 every minute based on two programs: Thermostat ML Monitoring and Thermostat UP monitoring. 

In the screen shots you will see that the programs are running, their times /status is correct. The variables changed, and the times for them changing did update, but are off by 5 hours (early) which my time zone is GMT+5.

Let me know if you need more.

Screen Shot 2022-02-28 at 1.05.00 PM.jpg

Screen Shot 2022-02-28 at 1.04.49 PM.jpg

Screen Shot 2022-02-28 at 1.04.02 PM.jpg

Screen Shot 2022-02-28 at 1.04.16 PM.jpg

Screen Shot 2022-02-28 at 1.04.02 PM.jpg

Posted (edited)
9 hours ago, dbwarner5 said:

@Javi please look at the screen shots attached. The problem is not with UD Mobile as I originally thought. It appears that the ISY is using GMT time for variable changes, which is the time that UD mobile is picking up as you suggested. 

Look at the two variables: I_Thermostat_ML_Minutes and I_Thermostat_UP_Minutes.

These variables increment by 1 every minute based on two programs: Thermostat ML Monitoring and Thermostat UP monitoring. 

In the screen shots you will see that the programs are running, their times /status is correct. The variables changed, and the times for them changing did update, but are off by 5 hours (early) which my time zone is GMT+5.

Let me know if you need more.

Screen Shot 2022-02-28 at 1.05.00 PM.jpg

Screen Shot 2022-02-28 at 1.04.49 PM.jpg

Screen Shot 2022-02-28 at 1.04.02 PM.jpg

Screen Shot 2022-02-28 at 1.04.16 PM.jpg

Screen Shot 2022-02-28 at 1.04.02 PM.jpg

@Michel Kohanim I have the same problem with my polisy clock(s).

Program changes to variable record them 5 hours too early (I am in EST)
Manual vaiable value changes report the correct times.
I also found the system [minutes since beginning of day] uses about 5 PM as a base time instead of 12:00 PM.

Admin console shows current time and sunset/sunrise as correct.

I have opened tickets for both these problems since I ported ISY9994 code over to polisy.

Edited by larryllix
  • Like 1
Posted
12 minutes ago, dbwarner5 said:

I have a separate session planned with Michel later today and will show him live....problem is easily reproduced.

I always wonder how Michel finds the time for these individual sessions. I have had the benefit of several of these and it shows extraordinary commitment.

  • Like 2
Posted
45 minutes ago, asbril said:

I always wonder how Michel finds the time for these individual sessions. I have had the benefit of several of these and it shows extraordinary commitment.

Totally agree. I know he works long hours and in the >15 years I have been using UD, he has always been involved at this level. Amazing! and one fo the reasons that I never take advantage of his generosity in refunding $15 for an outdated module I purchased for $45 etc...

Guest
This topic is now closed to further replies.

×
×
  • Create New...