telethings teleCityLight-2L-A Smart Light Control User Manual
- June 1, 2024
- Telethings
Table of Contents
telethings teleCityLight-2L-A Smart Light Control
Product Information
Specifications
- Dimensions: 845934 mm
- Material: ABS
- Power supply: (5A/250VAC), (5A/30VDC)
- Frequency: EU: 868, US: 915
- Protection: Class C
- Relay control: Yes
- Dimming control: 0-10 V
- LoRaWAN Frequency: Selected on purchase
- Activation Method: ABP
- Encryption: AES128
- LoRaWAN version: V1.0.2
Product Usage Instructions
-
Assembly and Device Wiring
This device is intended for outdoor usage and is protected from moisture and water. Follow the instructions in the manual for proper assembly. -
Device Working Principle
The device can control lighting based on geographical data or a predefined schedule. It automatically calculates sunrise and sunset values or uses predefined times set by the user. -
Adding Device to Telethings IoT Cloud
To control the device remotely, you need to add it to the Telethings IoT cloud. Follow the steps outlined in the manual for device registration and control. -
Device Settings
Adjust the device settings according to your preferences for automatic or manual control of lighting elements.
FAQ
-
Q: Can the device be used in urban environments?
A: Yes, the device is suitable for smart light control in rural, urban, or similar environments. -
Q: What is the range of the LoRaWAN device?
A: The LoRaWAN device offers long-range connectivity for remote monitoring and control.
TELETHINGS D.O.O.
A: Gračaničkih gazija b.b., 75320 Gračanica, Bosna i Hercegovina
T: +387 (0)35 700 209 • F: +387 (0)35 700 201 • E:
[email protected] • W:
www.telethings.com
BASIC DEVICE INFORMATION
teleCityLight-2L-A is a device intended for smart light control in rural, urban or other similar environments. The device is integrated with lighting part that is being controlled and connected to the main grid as any other lightning system used in public lighting. It is intendent to be used in LoRaWAN networks, and it gives the ability for remote monitoring and control of specific lightning element. Because it is a LoRaWAN device , long range and other benefits of this product are secured.
Device Characteristics
| Dimensions: | 845934 mm |
|---|---|
| Material: | ABS |
| Power supply:* | 100 – 240 VAC |
| Frequency: | 50/60 Hz |
| Protection: | IP65 |
| Relay control: | (5A/250VAC),(5A/30VDC) |
| Dimming control: | 0-10 V |
| LoRaWAN | |
| Frequency:* | EU: 868, US: 915 |
| Class: | Class C |
| Activation Method: | ABP |
| Encyption: | AES128 |
| LoRaWAN version: | V1.0.2 |
| Automatic and manual control of lighting |
Lighting control based on geographical data (automatic calculation of
Sunset/Sunrise)|
Lighting control based on fixed parameters (device works by predefined fixed
weekly schedule)|
- Values are selected on purchase!
Assembly and device wiring
- This device is intended for outdoor usage, so it has all needed protections from moisture, water, etc. Physical construction of the device is given in the picture below.
- The device has a connector for power supply and lighting control. Device is connected to power supply and lighting with connector that is show on the picture below.
| WIRE COLOR | DESCRIPTION |
|---|---|
| COLOR 1 | INPUT 220 VAC (L) |
| COLOR 2 | INPUT NULL (N) |
| COLOR 3 | OUTPUT DIMMER (D+) |
| COLOR 4 | OUTPUT DIMMER (D-) |
| COLOR 5 | RELAY CONNECTOR (RL) |
| COLOR 6 | RELAY CONNECTOR (RL) |
DEVICE WORKING PRINCIPLE
The device will initiate a join procedure when it is switched on, considering that it is C class device, the device creates a communication session with the server. The whole time the device works by a predefined weekly schedule and based on that it controls output states (relay and dimming value). Working schedule is stored in a non-volatile memory, so in cases of power supply outage the schedule is always kept in the memory. The device has predefined settings for every day in the week, and those settings are read from the memory on the beginning of every day (00:00).
Data that is being read from memory is listed below:
- Dimming value after sunrise (e.g. 0%)
- Dimming value after sunset (e.g. 90%)
- Dimming value after midnight (e.g. 65%)
- Relay state after sunrise (e.g. OFF)
- Relay state after sunset (e.g. ON)
- Relay state after midnight (e.g. ON)
- Twilight control
- Automatic: device calculates sunrise and sunset values by using geographical settings defined by user, and adds time offsets to the results (it they exist). Those offsets are from -60 to +60 minutes.
- Manual: device uses predefined times for sunrise and sunset
For example, if user can define those settings:
During normal work device is continuously checking, based on the current time,
which mode is active, for example if for current day sunrise is set to 6:45,
sunset to 18:30, midnight time is set to 00:00 and current time is 18:45
device can easily determine that current mode is mode after sunset and before
midnight so it controls output states based on settings from memory (for
example dimming value after sunset is 90% and relay state is ON).
Simultaneously to that process, device also sends periodically data to the
server about current relay and dimmer state and current device timestamp in
terms of time synchronization.
ADDING DEVICE TO THE TELETHINGS IOT CLOUD AND DEVICE CONTROL
- Firstly user needs to login to the TeleThings IoT Cloud service by clicking on the link https://iot.telethings.com/home . User can login, or sing up to create a new account.
- If user does not have any devices on his user account, he can claim devices as many as he owns by clicking on button Claim Device and scanning QR code. After successfully device claim, proper message is being generated in order to inform user about adding device to his account and proper button for accessing devices is shown after that (picture 3.2).
- By clicking on button for access to the TeleCityLight devices, access to the device dashboard is opened (picture 3.3).
- On this dashboard, user has access to two tables. Table for configuring zones (left) and table for configuring and control devices (right).
- On the left table it is possible to add zones as the user needs and also delete them. Every zone has also devices as many as the user needs. Zones can be cities, part of cities, streets etc., and the user can rename the zones as he will.
- On the right table it is possible to configure claimed devices, assign or remove zones that are/aren’t related to them, and also rename the devices.
ZONE SETTINGS
- Clicking on one of the rows inside table Zones, the dashboard for configuring the zones is opened (picture 3.1.1) where user can change settings for the zone that is selected inside Zones table.
- On this dashboard user has 3 levels of settings:
- Device list inside zone
- Defining LoRa communication period for selected zone
- Weekly schedule
DEVICE LIST INSIDE ZONE
- In this part of settings user can search and view devices that belong to the selected zone. The user can have as many zones as he wants but every device can only be assigned to one zone at the time (duplicated relations are forbidden).
- By clicking on any of devices from picture 3.1.2, the device specific dashboard is opened which enables control and monitoring (picture 3.1.3).
- From this dashboard it is possible to manually control device relay output state by sending ON or OFF commands using bulb widget, also user can review device output control data through history (up to 1 year backward).
Controls on this dashboard are explained below:
- Bulb widget: Control for manually sending ON/OFF commands to the device relay output
- Digital gauge: Control that shows current dimmer value that is applied by device (0-100%)
- Relay output state graph: On this graph user can review relay output states through past (up to 1 year backward)
- Regulation history: On this graph user can review dimmer value states through past (up to 1 year backward)
DEFINING LORA COMMUNICATION PERIOD FOR SELECTED ZONE
- This form sends LoRa communication period value to all devices that belong to the selected zone. The value is send in minutes (from 1 to 60) to every device inside zone.
- By clicking on the button Submit data (10 minutes) is send to the all devices (in table Zone devices). Every 500 ms data to the device is sent, so if user has 100 devices the time needed to send data to all devices is 50 seconds, 500 ms timeout is implemented in order to avoid overload of the LoRaWAN network.
WEEKLY SCHEDULE
This part of settings is the most complex part of the whole system, it
consists of several settings that will be explained in the rest of the
document.
Daily settings
- This settings are configuring sunrise, sunset and twilight control. Twilight control option checkbox defines how to set sunrise and sunset values, so user has two options:
- Twilight control option enabled: User defines possible offsets for sunrise and sunset (from -60 to 60 minutes), and the sunrise and sunset times are automatically calculated
- Twilight control option disabled: User defines fixed sunrise and sunset times by picking value from time picker
- Midnight time is independent from twilight control and has a fixed value.
Relay state settings
- In this part of settings user defines relay states for all working modes (sunrise, sunset and midnight). User can define when he wants to enable or disable the relay output, and based on those settings device will set the relay states depending on the working mode.
- For example as shown on picture 3.1.6, relay is in ON state in midnight and sunset mode and in OFF state in sunrise mode.
Dimmer settings
- In this part of settings user can set dimmer value for all of the working modes.
- As shown on picture 3.1.7, it is possible to define dimmer value (from 0 to 100 %). Value 0 means that dimmer is not active and relay state for that mode should be in OFF state.
Geographic coordinates settings
- Considering the fact that device has the option of automatic calculation of sunrise and sunset times for every day, it is necessary to define some geographic parameters that are used for calculation.
- In this part of settings user must define several things:
- Geographical lattitude
- Geographical longitude
- Elevation
- Timezone
- Based on those parameters the device calculates sunrise and sunset times.
- By clicking on the button Save and send schedule (picture 3.1.9), if data is correct, is sent to all devices belonging the specific zone. If some of parameters inside weekly schedule settings are incorrect data will not be sent or saved until correct values are entered.
DEVICE SETTINGS
- As mentioned before, user has access to the two types of tables (Zones and User devices table).
- As shown on the picture 3.2.1, user can search and review all devices that he claimed. The more important thing is that user can configure certain settings for every of those devices by clicking on some of the options in right corner (picture 3.2.2).
Picture 3.2.2. Device settings menu
- In this menu user has access to several types of settings:
- Device settings
- Device zone settings
- Device name settings
- By clicking on device settings, dashboard for device parameters settings is opened (picture 15)
- This part of settings is used for defining LoRa communication interval and current dimming value.
- By clicking on device zone settings a pop-up window (Picture 3.2.4) is shown where user can assign a device to a specific zone. The device also can have no zone assigned.
- As previously mentioned, user can edit current device zone settings or delete or create new device zone settings (picture 3.2.5).
- By clicking on button Add, user can define new zone for device where he needs to select Asset as Zone type and pick one of already defined zones (picture 3.2.6).
- User as a type of Zone should select Asset, any other type is considered as error and settings will not be saved.
- By clicking on device name settings a pop-up window (picture 3.2.7) for changing name is shown, where user can see current device name or change it if it is required.