# The intercept of the German BOS radio is strictly
# prohibited and will be prosecuted.
# The use is only authorized personnel permitted!
#
[BOSWatch]
# set loglevel for logfile
# 10 = debug
# 20 = info
# 30 = warning
# 40 = error
# 50 = critical
loglevel=10
# BOSWatch uses a rotating logfile
# Rotating is at midnight
# You can set the backupCount here
# backupCount = 7 (keeps logfiles for 7 days)
backupCount=7
# if you want to start BOSWatch as a daemon with rc2.d,
# you have to set the path to rtl_fm and multimon-ng !
# both pathes have to end with an /
#rtl_path = /usr/local/bin/
#multimon_path = /usr/local/bin/
# if you are using many plugins or plugins with a long execution time
# you can execute them in an asynchronous manner
# It must be pointed out that enabling (0|1) this consumes time,
# so don't use it for one rapid plugin
processAlarmAsync=0
# Using RegEx-filter (0 - off | 1 - on)
# filter-configuration in section [Filters]
# if you are using the RegEx filter you must add filter rules to forward alarms
useRegExFilter=0
# for double check save the last n IDs
# it is used in combination with double_ignore_time
# 1 is required if you want to use the double alarm filter
doubleFilter_ignore_entries=10
# time to ignore same alarm (only ID is checked) (sec)
doubleFilter_ignore_time=5
# ignore msg is only usefull for POCSAG (0 - off | 1 - on)
# 0: double check ignores the msg-text (only check ID + function)
# 1: if you want to differentiate between with/ without msg
# f.e. if they use quick-alarm (without text, then same RIC with msg)
# you will get more then one alarm anyway if the msg is different (receiving-problems)
doubleFilter_check_msg=0
# writes the multimon-ng raw data stream into a text file named mm_raw.txt
writeMultimonRaw=0
[FMS]
# look-up-table for adding a description
# using description (0 - off | 1 - on)
# descriptions are loaded from csv/fms.csv
idDescribed=0
# Check for correct CRC-information is provided by multimon-ng
# As this seems to be incorrect in many cases it might be useful to disable this
# (0 - off | 1 - on)
# Better use RegEX to verify the correct data
checkCRC=0
[ZVEI]
# look-up-table for adding a description
# using description (0 - off | 1 - on)
# descriptions are loaded from csv/zvei.csv
idDescribed=0
[POC]
# some very simple filters:
# Allow only this RICs (empty: allow all, separator ",")
# f.e.: allow_ric = 1234566,1234567,1234568
allow_ric=
# Deny this RICs (empty: allow all, separator ",")
# f.e.: deny_ric = 1234566,1234567,1234568
deny_ric=
# start and end of an allowed filter range
filter_range_start=0000000
filter_range_end=9999999
# look-up-table for adding a description
# using description (0 - off | 1 - on)
# descriptions are loaded from csv/poc.csv
idDescribed=0
# Static Massages for Subrics.
rica=Feuer
ricb=TH
ricc=AGT
ricd=Unwetter
# RIC for net identification
# Usually sent periodically, separated by comma
netIdent_ric=0174760, 1398098
# you can hold one entry per netIdent_ric [0] or the whole history [1]
netIdent_history=0
# With some message, coordinates can be sent to determine the destination
# Do you want to enable this feature? (0 - off | 1 - on)
geo_enable=0
# If a RIC contains coordinates, specify the regex used to decode them
geo_format=#C(\d{2})(\d{5}),(\d{2})(\d{5})#
geo_order=LON, lon, LAT, lat
[multicastAlarm]
# Configure multicastAlarm if your POCSAG network uses an optimized transmission scheme for alarms with more than one RIC (often found in Swissphone networks).
# In this optimized transmission scheme, a POCSAG telegram with each RIC that needs to be alarmed will be send in a sequence. These telegrams are send without a text message. This sequence is directly followed by a telegram with a specific RIC and the text message that belongs to the sequnece send right before.
# A POCSAG pager (DME) can be configured to start an acoustic alarm if a specific RIC without text has been received. If afterwards the specific RIC with the text message will be received, the pager will show the message in it's display.
# multicastAlarm enables BOSwatch to process the all received RICs joined with the text message.
#
# enable multicastAlarm (0 - off | 1 - on)
multicastAlarm=0
# time limit for alarms that do not belong to the multicastAlarm sequence in seconds
multicastAlarm_ignore_time=15
# multicastAlarm delimiter RIC (usually used as a starting point for a alarm sequence). Needs to be empty if multicastAlarms are interrupted by normal alarms.
multicastAlarm_delimiter_ric=
# multicastAlarm RIC (one or more, separated by comma) used to send the text message
multicastAlarm_ric=
[Filters]
# RegEX Filter Configuration
# http://www.regexr.com/ - RegEX Test Tool an Documentation
# If RegEX is enabled - only alloewd data will pass!
# how often should Pushover re-alert in seconds (emergency-messages)
retry=30
# when should Pushover stop to re-alert in seconds (emergency-messages)
expire=90
# use HTML in messages (0/1)
html=1
[Telegram]
# This is your unique BOT token. You will get it from the BotFather once you have created your BOT.
BOTTokenAPIKey=
# Create a group chat with your BOT and enter the chat ID here.
# The plugin will send messages as your BOT and post everything in this group chat.
BOTChatIDAPIKey=
# The plugin can extract a location from the POCSAG message.
# However, this will be done for the following RIC only (7 digits e.g. 0012345).
RICforLocationAPIKey=
# This is your Google API key.
# Required if you want to create a map based on location information received with the above RIC.
GoogleAPIKey=
# Define your start address for the routing
# Use the following format: CityOfOrigin+Street+Number
RoutingOrigin=MyCity+MyStreet+MyNumber
#Wildcards can be used, see end of the file!
FMS_message=%DATE% %TIME%: %FMS%
#Wildcards can be used, see end of the file!
ZVEI_message=%DATE% %TIME%: %ZVEI%
#Wildcards can be used, see end of the file!
POC_message=%MSG%
[yowsup]
# number or chat-number who whants to become the news
empfaenger=
# WhatsApp-number of that the news comes
sender=
# password from this number
password=
#Wildcards can be used, see end of the file!
fms_message=%DATE% %TIME%: %FMS%
#Wildcards can be used, see end of the file!
zvei_message=%DATE% %TIME%: %ZVEI%
#Wildcards can be used, see end of the file!
poc_message=%MSG%
[hue]
# For API access please read https://www.developers.meethue.com/documentation/getting-started (registration required)
# or https://www.google.com/search?q=philips+hue+how+to+get+api+key
# IP address of the hue bridge
bridgeip=
# the numeric ID of the device (only one device supported)
deviceid=
# the authentication string used to access the bridge
apikey=
# Timing parameters for switching on/off
# Every on/off cycle adds delay to BOSwatch if it operates in synchronous mode. Consider to configure "processAlarmAsync = 1" to activate asynchronous operation in BOSwatch if you switch on/off multiple times.
# If a light bulb is connected, you can keep it blinking for a while
repeat=2
timeon=2
timeoff=1
# configure 0 to keep the switch on for infinite time or configure >=1 to keep it for the value in seconds to on, before switching to off.
keepon=60
[Divera]
# See https://api.divera247.com/ for Api-Documentation
# Title: Alarm-Stichwort (max. 50 Zeichen, in der kostenlosen Version max. 30 Zeichen)
# Text: Alarm-Text (in der kostenlosen Version wird dies nicht übernommen)
# Priority: true / false.
# Wird ein anderer Wert oder gar keiner gesetzt, so wird die Divera-Alarmierung nicht durchgeführt.
# Divera API Key
accesskey=
# Section for POCSAG
# Adapt Pocsag Subric (a,b,c,d) to Divera Priorities (true/false)
SubA=true
SubB=false
SubC=
SubD=
poc_title=%DESCR%: %MSG%
poc_text=%DATE% %TIME% - %DESCR%: %MSG%
# Section for ZVEI
# default prio for all ZVEI - except you specify it different