Releases · htilburgs/MMM-MyPrayerTimes

24 Jun 21:13

fee0dba

v2.0 Latest

Latest

Update node_helper.js

Nodejs Request
As of Feb 11th 2020, request is fully deprecated. No new changes are expected land. In fact, none have landed for some time.

Rewrite node_helper.js
Because nodejs request has been deprecated, I've updated the node_helper.js to nodejs fetch
This is done to preserve issues with the request module.

Assets 2

22 Nov 13:06

htilburgs

v1.2.1

0e9261c

Added Time Offset (mptOffset)

The mathematical side of how the calculation should work is generally agreed upon in the Islamic world. Then again, this is an assumption I am making based on the number of countries that use the angle based calculation (and please note that I am not religiously or formally qualified and am providing this information with absolute humility in the hope that it may be useful). However, based on location, government preferences, and other 'factors', there are differences in the methods that produce, sometimes, a substantial variation in timings. If the mathematical side interests you, have a look at this excellent explanation: http://praytimes.org/wiki/Prayer_Times_Calculation.

A calculation method is typically made up of the following:

The Fajr Angle
The Maghrib Angle or minutes after sunset that Maghrib should be
The Isha Angle or minutes after Maghrib that Isha should be
The AlAdhan API has default values for all 3, and most methods only specifically specify Fajr and Isha.

Most countries adhere to one of the above methods, and they then tune the timings further, by adding a few minutes here and there, based on criteria that may seem completely arbitrary. So, even if you use the Gulf Region method and compare the timings to Dubai's IACAD or the UAE's Awqaf, you will see a couple of minutes differing. Usually this difference can be anywhere from 1 to 5 minutes.

The mptOffset option gives the posibility to modify the differences.

Assets 2