Shared-Notification allows you to share data within a group. It serves as an effective method of informing peers, strangers, neighbourhoods, friends, researchers, etc of messages that requires immediate attention. Individual can easily team up to form a neighbourhood watch. Researchers/scientist can analyze sensor data from anywhere in the world. You can use it to store/log data. Easily start your own Monitoring Center business. The possibilities are endless.
First, decide on the type of Sharednotification network you wish to implement. Possible options: Private, Exclusive, Open, Data Logging, and Enhanced.
Next, the registration info to setup your app and hardware.
Finally, depending on your application you can implement Sharednotification API in you system or setup the hardware you acquire.
They’re currently five (5) structure we can create to share data: Private, Exclusive, Open, Data Logging, and Enhanced.
If you wish to gather data from numerous devices in different locations for analysis. If you’re the head of your neighbourhood watch and a little tech-savy, you have implement Sharednotification. If you and your friends require remote access to data then Sharednotification private structure is your answer.
If you’re an individual who loves full management control over your alerts. If you want to option to easily block notifications from a specific device/individual/home then Exclusive structure is your answer. Any device can be added to Sharednotification ‘Exclusive’ network by setting up your device using the same Network Identification (NID).
Still wanting full managemential control over your group just like Exclusive network. And if you don’t mind being in a group with a range/radius limitation then Sharednotification Open structure is your answer.
Similar to Sharednotification ‘Exclusive’ network, you have full managemential control except your require to keep you’re Network Identification (NID) and API Key a secret. The group basically function as a cloud by saving your data to it.
This structure is used mainly by Neighbourhood Watch Program (NWP). watch structure is creating a Radial Propagation account and joining a neighbourhood watch by using an existing NID. This group allows you to join a larger group (Exclusive or Private) while belonging to another group/community that is limited by distance
Depending on your group/network( Private, Exclusive, Open, Data Logging, or Enhanced), you’re assigned API-Key, Hardware Identification (HID), Network Identification (NID), or a combination of two. Please DO NOT share your API-Key.
Sharednotification Private group is manage by a single administrator with it credentials. All devices are manage with anyone with these credentials. One credential to many devices[1 – many]
Sharednotification Exclusive group is also managed by anyone with the credentials; however, each device has its own dashboard and credential/access code. One credential to one device [1 – 1] is one device to one credential managemential structure.
Sharednotification Open group is only manage by each individual device administrator. One to One management. [1 – 1]
Sharednotification Data Logging group isn’t necessarily a group; however, this is also a one-to-one management structure.
Sharednotiifcation Enhance group is a one-to-one management structure.
The short answer is NO. We currently have no plans to implement automatic drones response features.
Drones automatic response feature is which software upload flight plan to a drone whenever it receives an alert.
- Data Loggers
- Environmential Remote Monitoring
- Smarthome
- Educational
- HOAs
- Neighbourhood Watch
YES. OPEN-UI uses Sharednotification API with drones security softwares to develop a complete security package for their clients.
Any digitalize information can be shared.
For information on implementing Sharednotification API se Developer’s Handbook.
Click on the this link for Developer’s Handbook
We made the decision to base on the founder’s love of open-source to use a widely available program; hence, Home Assistant was decided on. Sample yaml codes are available Gevelopers Guide.
Below is a sample json payload with the most important fields. This is a SERVICE message that is broadcast to everyone within group.
{
"hid": "12345ABCDE-6790",
"bcname": "YOUNG",
"type": "SERVICE-CHILDCARE",
"to": "",
"co": "",
"tt": 1754586175.054292,
"tt_string": "12:18AM Sep 2, 2025",
"msg": {
"ad": "<p>Are you looking for a responsible, friendly, and dependable babysitter? I’m here to help!<br />My name is Susan, and I have 20 years of experience working with children of all ages — from infants to pre-teens. Whether you need a night out, regular after-school care, or occasional help, I offer a safe and nurturing environment where your kids will feel happy and engaged.</p><p>What I Offer:<br />- Weekday availability (flexible hours)<br />- Homework help & fun educational activities<br />- Meals as and when required<br />- Non-smoker and pet-friendly<br />Rates: Competitive and negotiable<br />$250 per week (Monday to Friday)</p><p>Contact me for weekend availability<br />References: Available upon request</p>",
"subject": "Friendly Babysitter",
"email": "susan.elzinie@sharednotification.com",
"tele": "(416) 328-7448",
"website": "www.sharednotification.com",
},
"position": {
"latitude": 43.788218697279,
"longitude": -79.66514795440051
}
}hid – is the Hardware Identification (HID) which is assigned upon registration.
bcname – is broadcast name you used for your community/neighbourhood/group to identify you.
type – is type of message this json payload contain. SERVICE -> CHILDCARE
tt: triggered time – time message was sent.
tt_string: string format of triggered time.
position – is the geographical location of where the message was sent.
msg – is the service details message.
subject – message’s subject
email – email address of the sender. This is visible to everyone
tele – telephone number of the sender. This is visible to everyone
website: website address of the sender. This is visible to everyone.
When your home is broken into your alarm system broadcast a SENSOR alert to all members in their group/neighbourhood. Below is an example for the payload:
{
“hid”: “12345ABCDE-6790”,
“bcname”: “GRUMPY MAN HOUSE”,
“type”: “SENSOR”,
“to”: “”,
“co”: “”,
“tt”: 1754586175.054292,
“tt_string”: “12:18AM Sep 2, 2025”,
“msg”: “Rare window broken & motion trigger @ 12:20AM”,
“position”: {
“latitude”: 43.788218697279,
“longitude”: -79.66514795440051
}
}
This GRUMPY MAN HOUSE broadcast a SENSOR alarm at 12:18AM on September 2, 2025 stating that their back window as broken into and motion sensor was triggered 2 minutes ago.
PANIC alert message is similar to SENSOR alert message See below for an example json payload:
{
“hid”: “90125POIUY-6540”,
“bcname”: “OLD HOUSE AT CORNER”,
“type”: “PANIC”,
“to”: “”,
“co”: “”,
“tt”: 1754586175.054292,
“tt_string”: “9:02PM Oct 31, 2025”,
“msg”: “Susan Ebanks send Panic Alert @ 9:02 PM”,
“position”: {
“latitude”: 43.788218697279,
“longitude”: -79.66514795440051
}
}
OLD HOUSE AT CORNER broadcast a PANIC alert at 9:02PM on October 31, 2025 stating that Susan Ebanks is in distress.
What other members sees on your screen: OLD HOUSE AT CORNER send PANIC alert [Susan Ebanks send Panic Alert @ 9:02 PM] at 9:02PM