# Updates - node-red-contrib-bigtimer - HELP

**URL:** <https://discourse.nodered.org/t/updates-node-red-contrib-bigtimer-help/7475>\
**Category:** General\
**Created:** [1 February 2019 12:05 UTC](https://discourse.nodered.org/t/updates-node-red-contrib-bigtimer-help/7475 "2019-02-01T12:05:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![scargill](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/scargill/32/1118_2.png) [@scargill](https://discourse.nodered.org/u/scargill)\
**Post date:** [1 February 2019 12:05 UTC](https://discourse.nodered.org/t/updates-node-red-contrib-bigtimer-help/7475/1 "2019-02-01T12:05:23Z")

</div>

This morning I've updated node-red-contrib-bigtimer to get rid of a nasty bug in moonrise-moonset detection (the module suncalc (getMoonTimes.alwaysUp and alwaysDown don't seem to correctly support FALSE) - fixed and I'm up to v2.1.3 and that's live on NPM - but node-red-flows is still showing 2.1.1 - 2 versions behind.

---

<div class="post-metadata">

**Author:** ![scargill](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/scargill/32/1118_2.png) [@scargill](https://discourse.nodered.org/u/scargill)\
**Post date:** [1 February 2019 12:23 UTC](https://discourse.nodered.org/t/updates-node-red-contrib-bigtimer-help/7475/2 "2019-02-01T12:23:32Z")

</div>

It's now been updated, sorry for the intrusion
