¶ Integration Note
| Manufacturer | Adhan Cloud |
| Model | Any |
| Driver Name | Adhan Cloud |
| Driver Version | 26.07.12.00 |
| Document / Driver Revision |
Jul 12, 2026
|
| Core Min / Max Tested | 8.8.xx |
¶ Overview
The driver can get all adhan information for multiple locations on a single controller. No Hardware is required.
¶ Supported Features
- Adhan for 7 Days
- Sunrise and Sunset Times for 7 Days
- Midnight and Imsak for 7 Days
- Event triggers for each data point that reset on a daily basis
- Hijri and Gregorian Calendar dates
- On and Off Triggers
- Sunrise / Sunset / Midnight / Imsak
- Fajr / Dhuhr / Asr / Maghrib / Isha
¶ Device Configuration
- The Driver doesn’t use IP addresses. That field is non-configurable
- The driver uses information retrieved from the cloud. An internet connection is required at all times the driver is in use.
- Times displayed may not be an exact time for the local location. Use the Offset to calibrate.
¶ Driver Configuration
The driver uses cloud-based information from https://aladhan.com. No API key is required.
Obtain the Latitude and Longitude of the location you wish to track
- You can obtain the Lat / Long from Google maps or a website such as https://www.latlong.net/.
- You can also obtain the Lat / Long from Elan’s Location and Weather System tab in the configurator
- Copy and paste those values in the driver
¶ Driver Installation
Install under Input / Output as a Sense Input
- NOTE: If installing multiple locations (multiple instances of the driver), name the Input controller based on location here. You will not be able to change the Sense Input after it is installed.
- Fill in the
- Innovo issued API Key – or leave blank if evaluating for 90 days.
- Add the Latitude and Longitude of the location you wish to track from the step above.
- Add as many digits here as possible to get accurate times. If the times displayed are not exact, adjust this value to be as close as possible to the location.
- Choose the required settings for Polling time, Method, School, Midnight Mode, Latitude Adjustment and Language.
- NEW FEATURE: Set offset time if desired. This time is used to advance or delay announcement and display of prayer time. It will also advance or delay event triggers. You can use + or – values in this field. Add a positive number to advance, meaning it will trigger the event and change the trigger time to before the real time. Add negative value to delay meaning the event will trigger after the real time.
¶ Custom Tabs
Create Custom Tabs by following this video tutorial https://youtu.be/_QdvatziWVE
¶ Custom Pages
- The driver has several included custom pages: Import and Connect each element to the proper variable as needed
- The templates are included in the driver. Import them into a custom page under Interfaces
- Connect the elements to the matching names in the driver
Use the following video tutorial as a reference.
https://www.youtube.com/watch?v=pRp4ePOfjMc
Create Event Maps for the Reload button by using the build in variables for the driver under Input / Output
- Note: In this driver we tried to compact the output lines so that the dealer doesn’t have to connect too many elements. Make sure you take your customer’s Viewers into consideration and check that the screens are readable on their screens.
Use only fields you deem necessary
¶ Event Maps
Each location will have sense inputs - To create a trigger, Right click the trigger name under the driver and create the necessary event.
For example, Sunrise Off - On means Sunrise has happened. The Sunrise On – Off is not used.
¶ Using The Driver
The driver will display several data points including the time remaining till the next event.
¶ Troubleshooting
Driver not Activated. Wait 10 seconds after Apply
- Information not populated. Check internet connection.
- If the driver is deleted and reinstalled, the interface pages will have to be remapped. It’s best to update the driver than delete and reinstall.
- Prayer Times are off: Adjust lat / lon to be as accurate as possible. Use offset to adjust the time.
- Fajr / Maghrib / Isha do not match the local timetable: check the Method setting and choose the calculation authority the customer follows (e.g. Moonsighting Committee, Gulf Region). On versions before 26.07.12.00 update the driver first: Method choices after Egyptian computed the wrong authority.
¶ Changelog
¶ Version 26.07.12.00
- Fixed the Method dropdown mapping: selections after "Egyptian General Authority" computed the wrong calculation authority (for example Gulf Region returned Tehran times, showing Maghrib about 30 minutes after sunset). All methods now compute the authority selected.
- Trial period extended from 30 to 90 days and the Innovo license check modernized.
- Reliability improvements to the status-update timer.
¶ Version 25.09.14.00