#1 First monthly is free
Shared Notification is all about sharing alerts with a selected group of homeowners. We don’t charge any subscription or monthly fees for self-monitoring and data logging type of neighbourhood structure. Many of our platform integrations features are absolutely free.
After registering for a Shared Notification account, you can forget about outrageous cost of monitoring your homes and enjoy a more effective monitoring system – Neighbourhood Monitoring Centres (NMC).
#2 Shared-Notification works superbly in almost every neighbourhood
Shared-Notification understand that traditional Commercial Monitoring Centers are ineffective mostly due to long dispatch-time to the scene of the alert which can be considered meaningless deterrent. When unauthorize guest understand that your neighbour is protected by possibly legal gun-toting neighbours, the deterrent is self-evident.
#3 Dispatching-time is reduced to seconds
The reliance on reducing dispatching-time to service the alert was the primary purpose of Shared-Notification. Most people would be surprise to know that large amount of people at home in the day. Neighbourhood watch has been proven to be the most superior form of monitoring.
#4 Shared-Notification work seamlessly with many smart home devices
We approach smart home monitoring with a philosophy of being easy-to-implement and increasing the magnitude deterrent level to the highest without infringing on our rights.
Shared-Notification is easy to integrations into your system. If your smart home is capable of communicating with a REST based-sensor then most likely your smart home can form neighbourhood watch.
#5 There are currently (5) neighbourhood watch structure to choose from
All structures are great selection. Your choice is mostly depending on the type of neighbourhood you’re in and how you interact with your community.
For those who are the leaders of their neighbourhood and is leading the drive to setup a Shared-Notification Neighbourhood Watch, a Private structure might be best.
For those who are more technologically savvy, an Exclusive neighbourhood structure might be best. Members in Exclusive neighbourhood have the same Neighbourhood Identification (NID).
For those who just want to be included in a neighbourhood watch try an Open neighbourhood structure where your neighbour is determine by the propagation radius you selected. Don’t use a propagation radius too large because it defeats the purpose of Neighbourhood Monitoring Centre.
An Enhanced neighbourhood is a combination of Open and Exclusive neighbourhood structure. This allows you to limit your Open neighbourhood to a limited radius of your choice.
Data Logging neighbourhood structure is where individual neighbour doesn’t shared alert but only stores alerts on the cloud.
#6 Shared-Notification understand that it takes a village to effectively protect your home and neighbourhood
Shared-Notification understand that you and your family alone can’t effectively monitoring your home or community. Even with a Commercial Monitoring Centre (CMC) such as ADT or Brinks, it still does provide a better solution than neighbourhood watch.
#7 With the added features to QGroundControl, drones add another layer of deterrent
Software detects and upload waypoint maps to alert’s location for a quicker response time to real-time monitor alerts via drone. The software is free to utilize as another tool in effectively monitoring your neighbourhood.
#8 Similar to ADT/Brink, anyone can form a Neighbourhood Monitoring Centre (NMC)
Instead of members in your neighbourhood paying an exorbitant amount for monthly monitoring, pay someone in your neighbourhood to locally monitoring your home which lessen the dispatching-time to inspect your home.
#9 Shared-Notification only broadcast the information you want to tell your neighbours
You’re allow to choose your broadcast name which will be display to your neighbourhood watch. All private information remains private. If your neighbourhood pose a high risk of retaliation, you have the option to only broadcast a non-specific address of the alert.
#10 Shared-Notification is quicker and simpler method to creating a neighbourhood watch and it is here to stay so get onboard
Contact us for information on how to start your Shared-Notification Neighbourhood Watch or how to start your Neighbourhood Monitoring Centre.
Now you know and knowing is half the battle!
Shared-Notification can truly make neighbourhood monitoring easier, better, and more convenient. We encourage you to dig deeper into resources on our website, shoot us a question if you want to, and hopefully we can assist you in becoming a leader of your secure neighbourhood.
If you’re like me, wasting money and depending on an obsolete archaic technology to monitor your home isn’t my cup of tea. So instead of wasting money, let’s use our and our neighbour’s smarthome device to protect our home and neighbourhood while making money at the same time.
Our traditional Commercial Monitoring Centre (CMC) was developed over 70 years ago and their method of monitoring require revolutionizing. Let us begin by first considering totally abandoning CMC and reverting to a more effective method of deterrent – Neighbourhood Monitoring Centre (NMC).
If your alarm system is capable of sending and receiving HTTP request, most specifically GET and POST then let’s start by first registering for a Shared Notification account or asking someone who already have a Shared-Notification account for API-Key and NID.
With and API-Key and NID (optional), posting your alert to Shared-Notification server is very simple. For example, the server assigned you the following information:
NID: 1682389630392-42177
API-Key: 66c5b8a0-e30c-11ed-bc4f-053451ed971b
HID: 1682706990354-17286
You’ll also need to choose a broadcast name, address, and a non-specific address. This information will be display to your neighbours so care should be taken when choosing it. Non-Specific Address are used in communities where retaliation is a strong possibility.
Broadcast Name (bcname): ELZINIE
Address (from): 123 Evergreen Terrace
Non-Specific Address (ns_address): 100 – 140 Evergreen Terrace
An example of how to shared a PANIC alert with your community, create an automation where the automation is triggered when the panic button is a long_press. There is no condition on this automation.
The actions will be to execute a script to share this press with sharednotification.com, notify all devices, and turn_on siren for a specific duration and audio level.
The script uses the above information from the Share-Notification to communicate with it.
rest_command.yaml
------------------------------------------------------------------------------------------------------
post_panic_request:
url: https://sharenotification.com/api/notifier?apikey={{API_KEY}}
method: POST
headers:
accept: "application/json"
content_type: 'application/json; charset=utf-8'
payload: '{"type": "{{PAYLOAD_TYPE}}", "bcname": "{{PAYLOAD_BCNAME}}", "msg": "{{PAYLOAD_MSG}}", "tt": "{{PAYLOAD_TT}}", "hid": "{{PAYLOAD_HID}}", "location": {"position": {"latitude": {{PAYLOAD_LATITUDE}}, "longitude": {{PAYLOAD_LONGITUDE}}}}}'
scripts.yaml
----------------------------------------------------------------------------------------------------------------
execute_panic_alert:
alias: 'Transmit PANIC alert to server'
sequence:
- service: rest_command.post_panic_request
data:
{"PAYLOAD_TYPE": PANIC,
"PAYLOAD_BCNAME": ELZINIE,
"PAYLOAD_MSG": Panic Alert Triggered,
"PAYLOAD_TT": "{{ now().timestamp() | timestamp_custom('%a %m-%d-%Y %-I:%M %p') }}",
"PAYLOAD_HID": 1689789583296-98503,
"PAYLOAD_LATITUDE": 43.788013441318974,
"PAYLOAD_LONGITUDE": -79.66491194227804,
"API-KEY": 66c5b8a0-e30c-11ed-bc4f-053451ed971b}
mode: singleautomations.yaml
------------------------------------------------------------------------------------------------------------
- id: '1689090843657'
alias: handle_panic_button
description: Send PANIC Alert to Shared-Notification server
trigger:
- device_id: 091f77a709485d572fbdcd2c8b2bab1b
domain: zha
platform: device
type: remote_button_long_press
subtype: button
condition: []
action:
- service: siren.turn_on
data:
volume_level: 0.45
duration: '60'
target:
device_id: 15ed99c05b3ffe4c768541d5e5246c1a
- service: notify.mobile_app_mani_iphone
data:
message: Panic Alert was triggered - 44 Oklahoma Drive
title: Neighbourhood Watch (ELZINIE)
- service: notify.mobile_app_noahs_iphone
data:
title: Neighbourhood Watch (ELZINIE)
message: Panic Alert was triggered - 44 Oklahoma Drive
- service: script.execute_panic_alert
data:
title: Neighbourhood Watch (ELZINIE)
message: Panic Alert was triggered - 44 Oklahoma Drive
- type: turn_off
device_id: 49accc88f383f1ce7b6903b07e3f2a07
entity_id: bf4aab00641bd93a005977e35f8b73b6
domain: light
mode: singleTo receive updates from Shared-Notification server, you can either periodically request updates or the server can push updates to you when it’s available. Updates are alerts from your neighbours who are in your neighbourhood network. You have the option to block update from any neighbour if desire.
For Shared-Notification to push updates to you, you need to create a webhook automation with HID be the webhook ID (webhook_id).
Automations.yaml
--------------------------------------------------------------------------------------------------------------------
- alias: sharednotification will send neighbourhood alerts to this webhook
trigger:
- platform: webhook
webhook_id: 1682706990354-17286
allowed_methods:
- POST
local_only: true
action:
- service: notify.persistent_notification
data:
title: Neighbourhood Watch - {{ trigger.json.bcname }}
message: '{{ trigger.json.msg }} - {{ trigger.json.from }}'
- service: notify.mobile_app_mani_iphone
data:
title: Neighbourhood Watch - {{ trigger.json.bcname }}
message: '{{ trigger.json.msg }} - {{ trigger.json.from }}'
- service: siren.turn_on
data:
volume_level: 0.45
duration: '15'
target:
device_id: 15ed99c05b3ffe4c768541d5e5246c1a
id: 2465443cf382444f9e8d3a7dace8616d
For periodically requesting updates, you need to create a REST sensor with a long scan interval (scan_interval). This example uses a 1-year interval (31557600 seconds) and uses automation to force the periodical request for updates. Home Assistant uses homeassistant.update_entity to force reset.
automations.yaml
------------------------------------------------------------------------------------------------------
- alias: update_request
trigger:
- platform: time_pattern
minutes: /1
action:
- service: homeassistant.update_entity
entity_id: sensor.sharednotification
- service: notify.mobile_app_mani_iphone
data:
message: '{{ state_attr(''sensor.sharednotification'',''msg'') }}'
title: '{{ state_attr(''sensor.sharednotification'',''bcname'') }}'
- service: persistent_notification.create
data:
message: '{{ state_attr(''sensor.sharednotification'',''msg'') }}'
title: '{{ state_attr(''sensor.sharednotification'',''bcname'') }}'
id: 45360775688a4f9ab39865aaa8f9ff9f sensor.yaml
_______________________________________________________________________________________________________________________________
- platform: rest
name: sharednotification
scan_interval: 31557600
resource_template: "http://sharednotification.com/api/inbox/gethidanddelete?hid=1689789583296-98503&apikey=66c5b8a0-e30c-11ed-bc4f-053451ed971b"
json_attributes:
- bcname
- message
- from
- msg
value_template: '{{ value_json }}'
We can never expect Neighbourhood Monitoring Centre (NMC) to completely replace our traditional Commercial Monitoring Centre (CMC). The function of NMC is to provide a more effective method of monitoring our neighbourhood. You might be wondering what is wrong with today’s CMC.
How do you measure the effectiveness of your CMC? How quickly does your CMC dispatches an officer to your property after a break-in? What level of deterrent does your CMC provided?
Firstly, unwanted entry will never cease. Burgling will always exist. They’re people who believes they’re entitled to other’s belongings. They’re others who think stealing is their last resort. In any case, an ounce of prevention is worth a pound of cure. While CMC does provide a sense of security and hinder break-in, it simply isn’t an effective use of your hardworking money.
Secondly, most CMC will send officer to inspect your premises for additional charges. An actual or false alarm will trigger these extra charges if an officer was to show up at your property. Thirdly, CMC response time only benefits unlawful individual, themselves, and insurance companies.
So, you have decided to shared your alert with your neighbours? The first thing you need to do is decide on the structure of your neighbourhood watch. The idea of linking neighbour’s Home Assistant or smart alarm system under one user/account seems intriguing and indeed it is. Under such an arrangement you’re basically creating a Monitoring Centre where one can manage each neighbour’s setting. In this structure, all neighbours share the same Neighbourhood Identification (NID) and same API-Key and receive the same alert notifications. This type of neighbourhood is known as Private.
Create a Shared Notification account
All devices/neighbours are managed by a single user. Devices uses the same NID and API-Key. Method of propagation is communal. This is known as Private Neighbourhood Watch.
The second neighbourhood watch structure is similar to the above expect each neighbours create and manages their own account. This gives users a unique API-Key but same NID. Each neighbour will still receive alerts from other neighbours with the same NID. Method of propagation is also communal. This type of neighbourhood is known as Exclusive.
Devices (A, B, C) are managed by a single account user. Device (D) is managed by a separate user. All devices use the same NID. Device (A, B, C) uses the same API-Key while device (D) uses a unique API-Key. Method of propagation for all is communal.
The third neighbourhood watch structure is having each neighbour register for Shared-Notification account and set alerts propagation radius. Currently, they’re five (5) Radial Propagation: 500m, 1km, 2km, 5 km, and 10 km. Radial Propagation is the maximum distance an alert shared between neighbours. This type of neighbourhood is known as Open.
Devices (A, B, C) are managed by a single user. Device (D) is managed by a separate user. The four (4) devices belong to the same Communal Neighbourhood network. Device (F) is managed by a single account user with a unique API-Key. This device (F) doesn’t have NID because its method of propagation is radial meaning alerts are shared based only on the distance you set. Device (F) will not share notification with NID and visa-versa.
The fourth neighbourhood watch structure isn’t necessarily a neighbourhood watch since it requires you to keep your NID and API-Key private. Since no neighbour belong to your NID, your alerts are only shared with you and possibly your family. This structure mainly function has a data logger where sharednotificaion.com stores your alert on the cloud. This type of neighbourhood is known as Data Logging.
Device (E) are managed by a single user with unique API-Key and NID isn’t used by no other device. Since device (D) alerts aren’t shared, this device only function as a datalogger.
The fifth and final neighbourhood watch structure is creating a Radial Propagation account and joining a neighbourhood watch by using an existing NID. This option allows you to be part of a larger established neighbourhood watch while belonging to another community that is limited by distance. This type of neighbourhood is known as Enhance.
Device (G) is managed by a single account with a unique API-Key and method of propagation is Radial. Notifications are shared with other radial devices within the specified radial distance. Since device (G) also has a NID, notifications are also shared with devices with the same NID that are within the specified radial distance.
Shared Notification was originally developed to remotely connect data-loggers, alarm systems, and other IoT devices to share alerts among users with similar task requirement, expertise, and proximity to these devices. The ultimate mission of Share-Notification is to share alerts and data among users of these devices to effectively servicing the alerts and relaying information.
So how can I use Shared-Notification to form a neighbourhood network hence replacing the traditional Commercial Monitoring Centre (CMC) with a more effective method of monitoring our homes and communities.
The first step to forming a neighbourhood watch is to decide the structure of the monitoring network. There are five (5) Shared-Notification structure but only 4 applies to neighbourhood watch: Private, Exclusive, Data Logging, Open, and Enhanced. Private structure is where one user creates a Shared-Notification account and add all users of the neighbourhood watch. All alerts are shared among all users that are added by the account owner. Exclusive structure requires all user to create an account using the same Neighbourhood Identification (NID). All alerts are shared among all users with the same NID. Open structure also requires each user to create an account; however, for this neighbourhood structure the user must select the maximum range in which alerts will be shared. The default maximum range is 500 meters which means you will only accept alerts from neighbours within 500 meters range. Enhanced structure is a combination of Open and Exclusive. This neighbourhood structure also all user to create an account with radial maximum range and enter a known NID. User will share alerts with everyone with same NID and everyone within the maximum allowable range.
The second step is to register for a Shared-Notification account based on the neighbourhood structure you decided. You will be assigned an API-Key, Hardware Identification (HID), and possibly NID.
The third step is to used the assigned information in step 2 to share alert with Shared-Notification server. The server will push alerts originated from other neighbours to you or you can periodically request updates/alerts from server. To share your alert with your neighbourhood used HTTP POST with json payload. Below are sample examples of how to communicate with Shared-Notification server using Home Assistance.
Neighbourhood Monitoring Centre (NMC) currently has five (5) structure to choose from: Private, Exclusive, Data Logging, Open, and Enhanced. Depending on the type of neighbourhood watch you and your neighbours would like to form your neighbourhood watch could consist exclusively of selective neighbours, tens, hundreds, or thousands of neighbours, or neighbours within a specific radius of your home. So how do I select the structure that best suits my neighbourhood watch?
A Private Neighbourhood Watch requires the head/leader of the neighbourhood to register for a Communal Shared-Notification account. The server will be assigned an API Key, Neighbourhood Identification (NID), and Hardware Identification (HID). API-Key and NID are shared with all members of the Open Neighbourhood Watch. The leader of the neighbourhood watch is capable of adding and removing member. Alert from any member is propagate to all members of your Open Neighbourhood Watch.
An Exclusive Neighbourhood Watch requires each member of your neighbourhood to register for a Communal Shared-Notification account with the same NID. The server will assign each member a unique API-Key and HID. Alerts are propagated to all members with the same NID.
Data Logging Neighbourhood Watch is not necessarily a neighbourhood watch since it doesn’t shared alerts with any members. This structure only logs alert to the server and nothing else.
An Open Neighbourhood Watch doesn’t propagate alerts base on NID but on a preset maximum radius in which each member desires to operate. Each member is required to register for a Shared-Notification account with method of propagation set to Radial and set a maximum propagation radius. The server will assign a HID and a unique API Key. An Enhanced Neighbourhood Watch is a combination of Open and Exclusive Neighbourhood Watch. This type of neighbourhood watch allows a member to limit the operating radius in which alerts are shared and also belonging to another neighbourhood watch.
What Shared-Notifications does
Shared-Notifications allow nodes/users to create groups in which nodes can share notifications for the purpose of monitoring, analyzing, and servicing to these notifications.
Who can be a User
- Anyone who an IoT device can register for a Shared-Notification account.
- Anyone who wants to manage, analyze, and service alerts/data.
- Anyone who wants to start a Neighbourhood-Watch Monitoring centre (NMC).
- Anyone who wants to store alerts/data on the cloud.
Why would I want to share my alert/data
- To allow the nearest member within proximity to the alert to service it.
- To manage groups IoT devices on a single platform.
- For my group to analyze and compare data.
- To help protect my community by setting up a neighbourhood watch.
- Because my neighbours might be better equipped and closer to my house than the old archaic monitoring centres.
Basically, to create deterrent, superior dispatch-time, analyzing data, and sharing information.
What type of info are Shared
- The best way to answer that question is to ask you what type of information you want to share?
- For Neighbourhood Monitoring centres, you can share your address, Broadcast Name, triggered sensor name, or anything.
- For community where retaliation is high for snitching, you can share your approximate area such as sharing only street name, a range of non-specific address, or anything.
The shared payload is:
{
"bcname": "ELZINIE",
"msg": "Front Door triggered @ 9:48AM Aug 3, 2023",
"from": "51 Seahorse Avenue"
}In the above example, Shared-Notification server, shares broadcast name, message, and the location of the alert to members of the group because that what ELZINIE wants to share.
How Shared-Notification works
- Upon registering for a Shared-Notification account, an API Key, Hardware Identification (HID), and possibly NID are assigned to you. This information is required to communicate with the server.
- Devices transmit alerts to Shared-Notification server via HTTP request.
To receive notifications/alerts, the device either periodically send a HTTP GET request to server or server send notifications/alerts to device whenever it’s available.
