Paradox EVO Binding

polychronov · October 2, 2019, 9:53am

Is there anything after these two entries in the log:
OH-thingHandler-5 2019-10-01 08:09:25.736 [DEBUG] [l.communication.AbstractCommunicator] - Socket time out occurred. Informing listener. Request={}. Exception=
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:210) ~[?:?]
at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[?:?]
at java.io.DataInputStream.read(DataInputStream.java:100) ~[?:?]
at org.openhab.binding.paradoxalarm.internal.communication.AbstractCommunicator.receivePacket(AbstractCommunicator.java:141) ~[?:?]
at org.openhab.binding.paradoxalarm.internal.communication.AbstractCommunicator.communicateToParadox(AbstractCommunicator.java:105) ~[?:?]
at org.openhab.binding.paradoxalarm.internal.communication.AbstractCommunicator.communicateToParadox(AbstractCommunicator.java:112) ~[?:?]
at org.openhab.binding.paradoxalarm.internal.communication.AbstractCommunicator.submitRequest(AbstractCommunicator.java:98) ~[?:?]
at org.openhab.binding.paradoxalarm.internal.communication.EvoCommunicator.readRAM(EvoCommunicator.java:229) ~[?:?]
at org.openhab.binding.paradoxalarm.internal.communication.EvoCommunicator.refreshMemoryMap(EvoCommunicator.java:218) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
OH-thingHandler-5 2019-10-01 08:09:25.745 [TRACE] [arm.internal.communication.SyncQueue] - Removing from queue request=RamRequest [getType()=RAM, getRamBlockNumber()=9]

Anything during the same time in the openhab.log?

kovacsi2899 · October 2, 2019, 2:27pm

Nothing after that. I have copied opehnab.log in the TXT and there was no relevant line.You can see that this is the time what in paradox log as well. It is strange for me, that’s why I had mentioned that I had internet outage in that time, probably it caused mess. Normally it should not affect it, as it communicates locally. I have restated and will see next ones.

polychronov · October 3, 2019, 5:45pm

OK. Thanks.
As I don’t see this behavior locally at home and I also don’t see in the code a meaningful reason the bridge handler to be null when the timeout occurs, I will have to simulate that. I have some ideas how to do so.
Please give me some time. Hope I can have a look at it during the weekend…

isabellep · October 3, 2019, 9:41pm

Hello all,

I am rather new to openhab but I have thus far managed to get quite a few things working (Insteon, Zwave, Rachio, …).

I just started trying to use the Paradox binding to communicate with my IP150/EVO192. After installing the binding I added the following paradox.things file, based on the online doc:


Bridge paradoxalarm:ip150:ip150 [refresh=5, panelType="EVO192", ip150Password="XXX", ipAddress="192.168.0.200", port=10000 ] {
        Thing panel panel
        Thing partition partition1 [id=1]
        Thing zone Fumee [id=1]
}

Note that for the real value of ip150Password given in my file is the same one as I need to type in the field “Panel user code” in order to do a manual login through the IP150 web page at 192.168.0.200. Perhaps this is not correct?

After restarting openhab, I found in the log that the things file has been read in. However, a bit later in the log I get the following warning:


2019-10-03 16:59:56.556 [WARN ] [l.handlers.ParadoxIP150BridgeHandler] - Initial communicator not coming up online for 10000 seconds. Probably there is something wrong with communication.

And just a bit later the following error message:


2019-10-03 17:13:07.819 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception: 
java.lang.NullPointerException: null
	at org.openhab.binding.paradoxalarm.internal.model.ParadoxPanel.isPanelSupported(ParadoxPanel.java:75) ~[?:?]
	at org.openhab.binding.paradoxalarm.internal.handlers.EntityBaseHandler.initializeDelayed(EntityBaseHandler.java:58) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) ~[?:?]
	at java.util.concurrent.FutureTask.run(Unknown Source) ~[?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source) ~[?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]
	at java.lang.Thread.run(Unknown Source) [?:?]

Any suggestions?

Many thanks,

polychronov · October 4, 2019, 2:44pm

Hi,
have you read the README?
Please make sure you provide both your IP150 password and the so-called PC Password which is something like a PIN from your system setup. Can be seen when entering in configuration mode from keyboard on section 3012. Default value is 0000.
Please check this: https://www.openhab.org/addons/bindings/paradoxalarm/

Cheers,
K.

isabellep · October 4, 2019, 3:16pm

Hi Konstantin,

Not sure what README you are referring to. I had read the bionding doc page but unfortunately I had no clue what “code 3012 setting” meant. Now I think I understand it is part of the programming mechanism available through the keyboard of my alarm panel. And it seems that I need the installer to help me with finding out that code. Right?

Many thanks,

Pierre

polychronov · October 4, 2019, 3:43pm

Yeah. You could always try with pcPassword=0000 which is the default. If it does not work, the installer needs to provide you the value.

Good luck !

polychronov · October 4, 2019, 3:45pm

Hi,
I’ve made a new binary for you. Tested it locally by simulating timeout. Found the bug and now it should be fine. At least I was able to reconnect when simulating.
Please give it a try and let me know if it works so I can make a PR. Hopefully we can make it in the next milestone release.

Cheers,
K.

kovacsi2899 · October 4, 2019, 5:40pm

User name and password is what you can use for IP150 modul:

isabellep · October 4, 2019, 5:41pm

Hi again,

The installer provided me with a 4-digit value for “address 3012” which is different from “0000”. Unfortunately, after entering this new value for pcPassword, I am still getting the very same error messages as before.
Could it be that I also need to provide a value for ip150Password that is also known to the installer and is different from “panel user code” value that I use to login on the ip150 web page (and same as I provide on my alarm keypad)?

kovacsi2899 · October 4, 2019, 5:42pm

Thanks! I installed the new one and restarted OH including clearing TMP and Catch. This way surely binding was restarted. It works fine so far.

isabellep · October 4, 2019, 8:44pm

@kovacsi2899: Thanks for your input. However my login page on the ip150 is only requesting a panel user code, see my screen capture:

The code I need to enter at that point happens to be the same as my pin on the alarm keypad. On the IP150 log it is then reported that “user1: PIERRE” has entered his code. Thus the value I am currently providing for ip150Password is in fact my pin on the alarm keypad. I do not know whether or not I should be provided with a different value.

As explained in my latest reply to Konstantin, the installer provided me with what is apparently the correct value for pcPassword.

Unfortunately using that pair of values in paradox.things does not result in a successful login through openhab.

polychronov · October 5, 2019, 8:35am

That’s just a wild guess that your IP150 is with the “new” firmware. I guess this is the firmware that supports the cloud services but I have no experience with it. Can you post which version is your IP150 pls?

polychronov · October 5, 2019, 8:35am

Yeah. Watchout for “TIMEOUT!” In the logs.

isabellep · October 5, 2019, 3:35pm

@polychronov:

Here is a screen capture of the system info tab of my IP150.

– Pierre

kovacsi2899 · October 5, 2019, 5:56pm

It is the new one. I think it wouldn’t work with that integration. I had bought with old one as it is still in the market. With some tricks new one can be downgraded as well, but it can be done by the installer.

isabellep · October 5, 2019, 10:36pm

Oh: I see… Thanks for your diagnostic. I will check with the installer about “downgrading” my board. Any chance you will be able to integrate the new version in the future? Thanks again!

polychronov · October 7, 2019, 5:52am

Hi,
if Paradox “opens” their API we could integrate that easily but the old way has been a result of reverse-engineering by few people from the community. As far as I know currently there is no any open API by Paradox aside from the one for Windows using a DLL library.

Cheers,

K.

Porcariu_Irinel · October 7, 2019, 10:36am

How can i install this binding?

isabellep · October 7, 2019, 2:15pm

Concerning the downgrade, I assume that this is only a software issue. Is there a particular version I should be looking for? Many thanks!

Le lun. 7 oct. 2019 à 07:23, Konstantin Polychronov via openHAB Community bot@community.openhab.org a écrit :