This post has been originally created by Joao. With this post the conversation and reverse engineering started. Without his project (GitHub - ParadoxAlarmInterface/pai: Paradox Magellan, Spectra and EVO, with MQTT, Signal, Pushbullet, Pushover and others) the binding for openHAB would not be possible.
Big thanks to @jpbarraca and @Jean_Henning for making the reverse engineering which reallty lead to this binding development!
I’ve moved the original post at the end of the text for reference. Here I will add the information about the openhab binding and most common issues/configurations. Anyone feel free to add information as this post has been made a WIKI upon my request and Joao’s agreement.
If I need debug log file of binding in order to fix found bug, you need to configure binding logging as per my preference and either message me the log file or post it in this thread. Please see the bellow post how to do so.
(Konstantin)
General binding information: Paradox Alarm System binding - Bindings | openHAB
Binding latest custom binaries (outside the official and milestone releases): currently all changes are merged into 3.x codebase so custom binaries are not required or available
Installation of custom binaries can be done via putting the jar file under addons folder of openhab.
Tested and confirmed hardware: Paradox EVO192 with IP150 (v.2.x)
Tested and confirmed not supported hardware: Paradox SP-series
How to configure binding log (this configuration logs all paradox binding related information in separate file - paradox.log):
Please open the file ./userdata/etc/log4j2.xml
Under section Appenders add the following:
<!-- Paradox custom file appender -->
<RollingRandomAccessFile fileName="${sys:openhab.logdir}/paradox.log" filePattern="${sys:openhab.logdir}/paradox.log.%i" name="PARADOX">
<PatternLayout pattern="%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5.5p] [%-36.36c] - %m%n"/>
<Policies>
<OnStartupTriggeringPolicy/>
<SizeBasedTriggeringPolicy size="100 MB"/>
</Policies>
</RollingRandomAccessFile>
Under the Loggers Section add the following:
<!-- Paradox custom logger -->
<Logger additivity="false" level="INFO" name="org.openhab.binding.paradoxalarm">
<AppenderRef ref="PARADOX"/>
</Logger>
Here you can change the value of level=“INFO” to level=“TRACE”, “DEBUG”, “ERROR”, etc… Usually for troubleshooting DEBUG level is required, if more info is needed, TRACE should be used. TRACE makes logging of the whole packets so the log file grows a lot with it…
===========================================
Original post by Joao:
Shameless advertising: GitHub - ParadoxAlarmInterface/pai: Paradox Magellan, Spectra and EVO, with MQTT, Signal, Pushbullet, Pushover and others
It supports MG/SP series but it fully processes all messages according to the protocol available. It should not be complicated to add support for the EVO series (probably only change the message parsers, tweak the login process, check the map).
My idea was to also add IP150 as a connection method (besides serial), but I do not have the hardware to test. However, the connection method is already decoupled from the main logic.
If relevant, add new issues in github and help test.
