Table of Contents：

• 1.  Introduction
  • 1.1  What is PB05 LoRaWAN Push Button
  • 1.2  Features
  • 1.3  Power Consumption
  • 1.4  Storage & Operation Temperature
  • 1.5  Applications
• 2.  Operation Mode
  • 2.1  How it work?
  • 2.2  How to Activate PB05?
  • 2.3  Example to join LoRaWAN network
  • 2.4  Uplink Payload
    • 2.4.1  Uplink FPORT=5, Device Status
    • 2.4.2  Uplink FPORT=2, Real time sensor value
    • 2.4.3  Uplink FPORT=3, Datalog sensor value
  • 2.5 Show data on Datacake
  • 2.6  Datalog Feature
    • 2.6.1  Unix TimeStamp
    • 2.6.2 Set Device Time
    • 2.6.3 Poll sensor value
    • 2.6.4  Datalog Uplink payload
  • 2.7  Button
  • 2.8  LED Indicator
  • 2.9  Buzzer
• 3.  Configure PB05 via AT command or LoRaWAN downlink
  • 3.1  Downlink Command Set
  • 3.2  Set Password
  • 3.3  Set button sound and ACK sound
  • 3.4  Set buzzer music type(0~4)
  • 3.5  Set Valid Push Time
• 4.  Battery & How to replace
  • 4.1  Battery Type and replace
  • 4.2  Power Consumption Analyze
• 5.  Accessories
• 6.  FAQ
  • 6.1  How to use AT Command to configure PB05
  • 6.2  AT Command and Downlink
  • 6.3  How to upgrade the firmware?
    • 6.3.1 Update firmware (Assume device have bootloader)
    • 6.3.2 Update firmware (Assume device doesn't have bootloader)
  • 6.4  How to change the LoRa Frequency Bands/Region?
• 7.  Order Info
  • 7.1  Main Device
• 7.  Packing Info
• 8.  Support
• 9.  Reference material
• 10.  FCC Warning

1.  Introduction

1.1  What is PB05 LoRaWAN Push Button

PB05 LoRaWAN Button is a LoRaWAN wireless device with 5 push buttons. Once the user presses the button, the PB05 will transmit the signal to the IoT server via remote LoRaWAN wireless protocol.

PB05 supports  2 x AA batteries and works for a long time up to several years*. User can replace the batteries easily after they are finished.

PB05 has a built-in speaker, it can pronouns different sound when press button and get reply from server. The speaker can by disable if user want it.

PB05 is fully compatible with LoRaWAN v1.0.3 protocol, it can work with standard LoRaWAN gateway.

*Battery life depends how often to send data, please see battery analyzer.

1.2  Features

• Wall Attachable.
• LoRaWAN v1.0.3 Class A protocol.
• 5 x push buttons.
• Built-in speaker
• Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
• AT Commands to change parameters
• Remote configure parameters via LoRaWAN Downlink
• Firmware upgradable via program port
• Support 2 x AA LR03 batteries.
• IP Rating: IP52

1.3  Power Consumption

PB05 : Idle: 5uA, Transmit: max 110mA

1.4  Storage & Operation Temperature

-10 ~ 50 °C  or -40 ~ 60 °C (depends on battery type, see FAQ)

1.5  Applications

• Smart Buildings & Home Automation
• Logistics and Supply Chain Management
• Smart Metering
• Smart Agriculture
• Smart Cities
• Smart Factory

2.  Operation Mode

2.1  How it work?

Each PB05 is shipped with a worldwide unique set of LoRaWAN OTAA keys. To use PB05 in a LoRaWAN network, user needs to input the OTAA keys in LoRaWAN network server. After this, if PB05 is under this LoRaWAN network coverage, PB05 can join the LoRaWAN network and start to transmit sensor data. The default period for each uplink is 20 minutes.

2.2  How to Activate PB05?

 1.  Open enclosure from below position.

 2.  Insert 2 x AA LR03 batteries and the node is activated.

 3. Under the above conditions, users can also reactivate the node by long pressing the ACT button.

User can check LED Status to know the working state of PB05.

2.3  Example to join LoRaWAN network

This section shows an example for how to join the TheThingsNetwork LoRaWAN IoT server. Usages with other LoRaWAN IoT servers are of similar procedure.

Assume the LPS8v2 is already set to connect to TTN V3 network . We need to add the PB05 device in TTN V3 portal.  

Step 1:  Create a device in TTN V3 with the OTAA keys from PB05.

Each PB05 is shipped with a sticker with the default DEV EUI as below:

Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:

Create the application.

Add devices to the created Application.

Enter end device specifics manually.

Step 2: Add decoder

In TTN, user can add a custom payload so it shows friendly reading.

Click this link to get the decoder: PB05 decoder.

Below is TTN screen shot:

Step 3: Use ACT button to activate PB05 and it will auto join to the TTN V3 network. After join success, it will start to upload sensor data to TTN V3 and user can see in the panel.

2.4  Uplink Payload

Uplink payloads include two types: Valid Sensor Value and other status / control command.

• Valid Sensor Value: Use FPORT=2
• Other control command: Use FPORT other than 2.

2.4.1  Uplink FPORT=5, Device Status

Users can  get the Device Status uplink through the downlink command:

Downlink:  0x2601

Uplink the device configures with FPORT=5. 

Example Payload (FPort=5):  

Sensor Model: For PB05, this value is 0x3B.

Firmware Version: 0x0100, Means: v1.0.0 version.

Frequency Band:

*0x01: EU868

*0x02: US915

*0x03: IN865

*0x04: AU915

*0x05: KZ865

*0x06: RU864

*0x07: AS923

*0x08: AS923-1

*0x09: AS923-2

*0x0a: AS923-3

Sub-Band: value 0x00 ~ 0x08(only for CN470, AU915,US915. Others are0x00)

BAT: shows the battery voltage for PB05.

Ex1: 0x0C48 = 3144mV

2.4.2  Uplink FPORT=2, Real time sensor value

PB05 will send this uplink after Device Status uplink once join LoRaWAN network successfully. And it will periodically send this uplink. Default interval is 20 minutes and can be changed.

Uplink uses FPORT=2 and every 20 minutes send one uplink by default.

key1 & key2 & key3 & key4 & key5:

Example in TTN.

• Battery:

Check the battery voltage.

Ex1: 0x0CEA = 3306mV

Ex2: 0x0D08 = 3336mV

• Sound_key & Sound_ACK:

Key sound and ACK sound are enabled by default.

Example 1: 0x03

          Sound_ACK: (03>>1) & 0x01=1, OPEN.

          Sound_key:  03 & 0x01=1, OPEN.

Example 2: 0x01

          Sound_ACK: (01>>1) & 0x01=0, CLOSE.

          Sound_key:  01 & 0x01=1, OPEN.

• Alarm:

Key alarm.

Ex1: 0x01 & 0x01=1, "TRUE", key alarm packet.

Ex2: 0x00 & 0x01=0, "FALSE", normal uplink data.

• key1

Displays whether the uplink data is triggered by key 1.

01 (H): (0x01&0x01)=01(H) =0000 0001(B)    bit0=1, "Yes"

02 (H): (0x02&0x01)=0     bit0=0, "No"

• key2

Displays whether the uplink data is triggered by key 2.

02 (H): (0x02>>1)&0x01 =01(H) =0000 0001(B)    bit0=1, "Yes"

04 (H): (0x04>>1)&0x01 =0   bit0=0, "No"

• key3

Displays whether the uplink data is triggered by key 3.

04 (H): (0x04>>2)&0x01 =01(H) =0000 0001(B)    bit0=1, "Yes"

08 (H): (0x08>>2)&0x01 =0   bit0=0, "No"

• key4

Displays whether the uplink data is triggered by key 4.

08 (H): (0x08>>3)&0x01 =01(H) =0000 0001(B)    bit0=1, "Yes"

10 (H): (0x10>>3)&0x01 =0   bit0=0, "No"

• key5

Displays whether the uplink data is triggered by key 5.

10 (H): (0x10>>4)&0x01 =01(H) =0000 0001(B)    bit0=1, "Yes"

01 (H): (0x01>>4)&0x01 =0   bit0=0, "No"

2.4.3  Uplink FPORT=3, Datalog sensor value

PB05 stores sensor value and user can retrieve these history value via downlink command. The Datalog sensor value are sent via FPORT=3.

The historical payload includes one or multiplies entries.

key5 & key4 & key3 & key2 & key1:

Poll message flag & Alarm:

No ACK Message: 1: This message means this payload is fromn Uplink Message which doesn't get ACK from the server before ( for PNACKMD=1 feature)

Poll Message Flag: 1: This message is a poll message reply.

• Each data entry is 11 bytes, to save airtime and battery, PB05 will send max bytes according to the current DR and Frequency bands. 

For example, in US915 band, the max payload for different DR is:

1. DR0: max is 11 bytes so one entry of data
2. DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
3. DR2: total payload includes 11 entries of data
4. DR3: total payload includes 22 entries of data.

If user sends below downlink command:  

Where : Start time: 6722DD98 = time 24/10/31 Thursday 01:30:00 

             Stop time: 672300C0 = time 24/10/31 Thursday 04:00:00 

PB05 will uplink this payload:

000000001000416722E531

000000000800416722E538000000000400416722E540000000000200416722E54A000000000100416722E552000000000000406722E9BA000000000000406722EE6A000000000000406722F31A000000000000406722F7CA000000001000416722F9BA000000001000416722F9F6000000000800416722FB0E000000000000406722FC7A

Where the first 11 bytes is for the first entry:

The first four bytes are reserved, meaningless.

key5 & key4 & key3 & key2 & key1: 10(H)

• key5: ((0x10>>4)&0x01) = 1, "Yes".
• key4: ((0x10>>3)&0x01) = 0, "No".
• key3: ((0x10>>2)&0x01) = 0, "No".
• key2: ((0x10>>2)&0x01) = 0, "No".
• key1: (0x10 & 0x01) = 0, "No".

The sixth byte is reserved, meaningless.

poll message flag & Alarm: 41(H)    means reply data, For Alarm: 0x41&0x01 =1, "True".

Unix time is 0x6722E531= 1730340145s= 24/10/31 02:02:25

If PB05 doesn't have any data in the polling time, it will uplink 11 bytes of 0:

See more info about the Datalog feature.

2.5 Show data on Datacake

Log in to DATACAKE, copy the API under the account.

Copy and paste the TTN decoder here and save.

Visual widgets please read the DATACAKE documentation.

2.6  Datalog Feature

When user want to retrieve sensor value, he can send a poll command from the IoT platform to ask sensor to send value in the required time slot.

2.6.1  Unix TimeStamp

Unix TimeStamp shows the sampling time of uplink payload. format base on

User can get this time from link:  https://www.epochconverter.com/ :

For example: if the Unix Timestamp we got is hex 0x6722DD98, we can convert it to Decimal: 1730338200. and then convert to the time: 2024/10/31 Thursday 01:30:00 (GMT).

2.6.2 Set Device Time

2.6.3 Poll sensor value

User can poll sensor value based on timestamps from the server.

Below is the downlink command.

Timestamp start and Timestamp end use Unix TimeStamp format as mentioned above. Devices will reply with all data log during this time period, use the uplink interval.

For example, downlink command

Is to check 2024/10/31 01:30:00 to 2020/12/1 04:00:00's data

Uplink Internal =5s, means LHT65N will send one packet every 5s. range 5~255s.

2.6.4  Datalog Uplink payload

See Uplink FPORT=3, Datalog sensor value

2.7  Button

• ACT button

Long press this button PB05 will reset and join network again.

• Alarm button

Press the button PB05 will immediately uplink data, and alarm is "TRUE".

2.8  LED Indicator

Hold the ACT green light to rest, then the green flashing node restarts, the blue flashing once upon request for network access, and the green constant light for 5 seconds after successful network access

• When the node is restarted, hold the ACT GREEN lights up , then the GREEN flashing node restarts.The BLUE flashing once upon request for network access, and the GREEN constant light for 5 seconds after successful network access.
• During OTAA Join:
  • For each Join Request uplink: the GREEN LED will blink once.
  • Once Join Successful: the GREEN LED will be solid on for 5 seconds.
• After joined, for each uplink, the BLUE LED or GREEN LED will blink once.
• Press the alarm button，The RED flashes until the node receives the ACK from the platform and the BLUE light stays 5s.

2.9  Buzzer

The PB05 has button sound and ACK sound and users can turn on or off both sounds by using AT+SOUND.

• Button sound is the music produced by the node after the alarm button is pressed.

         Users can use AT+OPTION to set different button sounds.

• ACK sound is the notification tone that the node receives ACK.

3.  Configure PB05 via AT command or LoRaWAN downlink

Users can configure PB05 via AT Command or LoRaWAN Downlink.

• AT Command Connection: See FAQ.

• LoRaWAN Downlink instruction for different platforms: IoT LoRaWAN Server

There are two kinds of commands to configure PB05, they are:

• General Commands:

These commands are to configure:

• General system settings like: uplink interval.

• LoRaWAN protocol & radio-related commands.

They are the same for all Dragino Devices which supports DLWS-005 LoRaWAN Stack(Note**). These commands can be found on the wiki: End Device Downlink Command

• Commands special design for PB05

These commands are only valid for PB05, as below:

3.1  Downlink Command Set

3.2  Set Password

Feature: Set device password, max 9 digits.

AT Command: AT+PWORD

Downlink Command:

No downlink command for this feature.

3.3  Set button sound and ACK sound

Feature: Turn on/off button sound and ACK alarm.

AT Command: AT+SOUND

Downlink Command: 0xA1 

Format: Command Code (0xA1) followed by 2 bytes mode value.

The first byte after 0XA1 sets the button sound, and the second byte after 0XA1 sets the ACK sound. (0: off, 1: on)

• Example: Downlink Payload: A10001                   // Set AT+SOUND=0,1    Turn off the button sound and turn on ACK sound.

3.4  Set buzzer music type(0~4)

Feature: Set different alarm key response sounds.There are five different types of button music.

AT Command: AT+OPTION

Downlink Command: 0xA3

Format: Command Code (0xA3) followed by 1 byte mode value.

• Example: Downlink Payload: A300                   // Set AT+OPTION=0    Set the buzzer music to type 0.

3.5  Set Valid Push Time

Feature: Set the holding time for pressing the alarm button to avoid miscontact. Values range from 0 ~1000ms.

AT Command: AT+STIME

Downlink Command: 0xA2

Format: Command Code (0xA2) followed by 2 bytes mode value.

• Example: Downlink Payload: A203E8                 // Set AT+STIME=1000   

          Explain: Hold the alarm button for 10 seconds before the node will send the alarm packet.

4.  Battery & How to replace

4.1  Battery Type and replace

PB05 uses 2 x AA LR03(1.5v) batteries. If the batteries running low (shows 2.1v in the platform). Users can buy generic AAA battery and replace it.

Note: 

1.  The PB05 doesn't have any screw, users can use nail to open it by the middle.

2.  Make sure the direction is correct when install the AA batteries.

4.2  Power Consumption Analyze

Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.

Instruction to use as below:

Step 1:  Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:

battery calculator

Step 2:   Open it and choose

• Product Model
• Uplink Interval
• Working Mode

And the Life expectation in difference case will be shown on the right.

5.  Accessories

• Program Converter (AS-02)

AS-02 is an optional accessory, it is USB Type-C converter. AS-02 provide below feature:

1. Access AT console of PB05 when used with USB-TTL adapter. See this link.

6.  FAQ

6.1  How to use AT Command to configure PB05

PB05 supports AT Command set. Users can use a USB to TTL adapter plus the Program Cable to connect to PB05 for using AT command, as below.

Connection:

• USB to TTL GND <--> Program Converter GND pin
• USB to TTL RXD  <--> Program Converter D+ pin
• USB to TTL TXD  <--> Program Converter A11 pin

6.2  AT Command and Downlink

6.3  How to upgrade the firmware?

PB05 requires a program converter to upload images to PB05, which is used to upload image to PB05 for:

• Support new features
• For bug fix
• Change LoRaWAN bands.

 PB05 internal program is divided into bootloader and work program, shipping is included bootloader, the user can choose to directly update the work program.

If the bootloader is erased for some reason, users will need to download the boot program and the work program.

6.3.1 Update firmware (Assume device have bootloader)

Step 1: Connect UART as per FAQ 6.1

Step 2: Update follow Instruction for update via DraginoSensorManagerUtility.exe. 

6.3.2 Update firmware (Assume device doesn't have bootloader)

Download both the boot program and the worker program . After update , device will have bootloader so can use above 6.3.1 method to update woke program.

Step 1: Install TremoProgrammer  first.

Step 2: Hardware Connection 

Connect PC and PB05 via USB-TTL adapter .

Note: To download firmware in this way, you need to pull the boot pin(Program Converter D- pin) high to enter the burn mode. After burning, disconnect the boot pin of the node and the 3V3 pin of the USB-TTL adapter, and reset the node to exit the burning mode.

Connection:

• USB-TTL GND <--> Program Converter GND pin
• USB-TTL RXD  <--> Program Converter D+ pin
• USB-TTL TXD  <--> Program Converter A11 pin
• USB-TTL 3V3  <--> Program Converter D- pin

Step 3: Select the device port to be connected, baud rate and bin file to be downloaded.

Users need to reset the node to start downloading the program.
1. Reinstall the battery to reset the node
2. Hold down the ACT button to reset the node.

When this interface appears, it indicates that the download has been completed.

Finally, Disconnect Program Converter D- pin, reset the node again , and the node exits burning mode.

6.4  How to change the LoRa Frequency Bands/Region?

User can follow the introduction for how to upgrade image. When download the images, choose the required image file for download.

7.  Order Info

7.1  Main Device

Part Number: PB05-XX

XX : The default frequency band

• AS923: LoRaWAN AS923 band
• AU915: LoRaWAN AU915 band
• EU433: LoRaWAN EU433 band
• EU868: LoRaWAN EU868 band
• KR920: LoRaWAN KR920 band
• US915: LoRaWAN US915 band
• IN865:  LoRaWAN IN865 band
• CN470: LoRaWAN CN470 band

7.  Packing Info

Package Includes:

• PB05 LoRaWAN Push Button x 1

8.  Support

• Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
• Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to support@dragino.com.

9.  Reference material

• Datasheet, photos, decoder, firmware

10.  FCC Warning

This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:

(1) This device may not cause harmful interference;

(2) this device must accept any interference received,including interference that may cause undesired operation.