Does it have to do with a locale / timezone?
Here is the code. All it is doing is taking the timestamp from MQTT and
converting it to your UTC offset. The UTC offset is retrieved from your OS
settings.
updated = moment.unix(epoch).utcOffset($moment_js_utc_offset).format("MMMM
D, YYYY, h:mm:ss a"); // requires moment.js
and here is where $moment_js_utc_offset is retrieved from.
bin/user/belchertown.py
# Setup UTC offset hours for moment.js in index.html
moment_js_stop_struct = time.localtime( time.time() )
moment_js_utc_offset = (calendar.timegm(moment_js_stop_struct) - calendar.
timegm(time.gmtime(time.mktime(moment_js_stop_struct))))/60/60
View source of your page and look for updated = moment.unix(epoch).utcOffset.
What does it show for the offset in ()? Is it right?
Please check your OS settings to make sure you have the right timezone
applied.
On Saturday, September 8, 2018 at 9:44:11 AM UTC-4, Praveen Chandrasekaran
wrote:
>
> Hi Pat,
>
> On mqtt spy the time it shows is fine. However on weewx page it is exactly
> half an hour behind. Will file issues for all.
>
> Regards,
> Praveen
>
> On Sat, 8 Sep 2018 at 18:41, Pat <[email protected] <javascript:>>
> wrote:
>
> Hi, this is not correct. The time comes from weewx's timestamp it
> publishes to MQTT. Please log in to your broker with another client and you
> can verify this. The skin just translate epoch to human readable.
>
> You other issues - I'm losing track of - as mentioned in the latest 0.6
> release notes <https://github.com/poblabs/weewx-belchertown/releases> -
> please create an issue on GitHub
> <https://github.com/poblabs/weewx-belchertown/issues>. This thread is 12
> pages long now and I'm having a hard time keeping up.
>
> 0.7 is coming right around the corner which is my priority to speed up the
> highcharts generation time - but as I'm sure you'll appreciate - family is
> a priority so I'm working on this during any spare time that I have.
>
> Thank you
>
>
> On Saturday, September 8, 2018 at 8:59:33 AM UTC-4, Praveen Chandrasekaran
> wrote:
>
> One more issue, with Mqtt enabled the time updated that it shows is 30
> minutes behind. With archive only its fine.
> The data is fine. Suspecting its just a time display issue.
>
> On Sat, 8 Sep 2018, 16:34 Praveen Chandrasekaran, <[email protected]>
> wrote:
>
> Seeing issues in records too in units. Makes me doubt if I picked the
> latest version of the skin. Is 0.6 the latest version?
>
> Largest Daily Temperature Range 26.7 °C May 14, 2018
> (Min: 62.5 °C - Max: 89.2 °C ) May 14, 2018
> (Min: 62.5 °C - Max: 89.2 °C ) 26.7 °C
> Smallest Daily Temperature Range 5.6 °C January 17, 2018
> (Min: 61.9 °C - Max: 67.5 °C ) January 17, 2018
> (Min: 61.9 °C - Max: 67.5 °C ) 5.6 °C
>
> On Sat, 8 Sep 2018 at 16:31, Praveen Chandrasekaran <[email protected]>
> wrote:
>
> Rain is also in inches in all the charts. Colin's 41south page also seems
> to have same issue though he is on metric. 61mm for the year in records but
> the graphs dont correlate.
>
> On Sat, 8 Sep 2018 at 16:20, Praveen Chandrasekaran <[email protected]>
> wrote:
>
> The rain charts seem to be off in monthly also. The units seem all weird.
> I believe for Colin everything is fine with metric. Not sure whats going
> wrong for me.
>
> On Sat, 8 Sep 2018 at 15:57, Andrew Milner <[email protected]> wrote:
>
> the graphs for week month and year ARE in metric (well Celsius at least) -
> only the day graph shows farenheit values
>
>
>
> On Saturday, 8 September 2018 13:06:49 UTC+3, Praveen Chandrasekaran
>
> ...
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
