Hi guys,
Im new here, trying my best to migrate from hassio. I was getting excited since i saw that the ParadoxAlarm Binding supports only EVO models, i wonder why is this? Why ParadoxAlarm supports all panel models on hassio but not on OpenHAB?
Currently this is the only thing that is hindering me from using OpenHAB, and id like to know if anyone has got the ParadoxAlarm working with MG5050 or if anyone can make it be supported please?
thanks in advance
Look at paradox pai (GitHub project). It reads the alarm and exposes it to mqtt. Then it’s easy to integrate to home assistant, openHAB, homebridge.
When I move from openHAB to home assistant, I only had to integrate the mqtt sensors etc. nothing else needed changing.
There is an official Paradox Alarm binding that openhabo1 is referring to: Paradox Alarm System binding - Bindings | openHAB
Where they differ is that the MG5050 panel is not supported by the binding and explicitly drops the connection even though the format of the messaging should be quite simliar to the EVO series. I have the same panel and see the follwing in the logs:
2024-02-16 20:48:48.373 [INFO ] [nal.communication.CommunicationState] - Login - Login to IP150 - OK
2024-02-16 20:48:48.967 [INFO ] [nal.communication.CommunicationState] - Successfully established communication with the panel.
2024-02-16 20:48:49.167 [INFO ] [l.handlers.ParadoxIP150BridgeHandler] - Found MG5050 panel type.
2024-02-16 20:48:49.168 [INFO ] [l.communication.AbstractCommunicator] - Stopping communication to Paradox system
I do agree that the original middleware is great and is still very usable, but having to run and maintain an extra script/docker container is just another overhead which could be reduced by relaxing the contraint on the original binding maybe?
Yes re benefit of using binding over external middleware.
But you’ve also got to look at the user population for each one. And if you have issues which will be supported better faster.
And if you’re already running mosquito servers and other things, then one more container isn’t really an issue.
2024-04-15 23:30:32.681 [DEBUG] [.handlers.ParadoxAlarmHandlerFactory] - createHandler(): ThingHandler created for paradoxalarm:ip150:849182e1e7
2024-04-15 23:30:32.686 [DEBUG] [l.handlers.ParadoxIP150BridgeHandler] - Start initialize()…
2024-04-15 23:30:32.687 [DEBUG] [l.handlers.ParadoxIP150BridgeHandler] - Starting creation of communicator.
2024-04-15 23:30:32.687 [DEBUG] [l.handlers.ParadoxIP150BridgeHandler] - Finished initialize().
2024-04-15 23:30:32.689 [DEBUG] [l.handlers.ParadoxIP150BridgeHandler] - Configuration file has pannelType=MG5050. Skipping Phase1 (Autodiscovery)
2024-04-15 23:30:35.690 [DEBUG] [l.handlers.ParadoxIP150BridgeHandler] - Phase2 - Creating communicator for panel MG5050
2024-04-15 23:30:35.690 [DEBUG] [.communication.ParadoxBuilderFactory] - Unsupported panel type: MG5050
2024-04-15 23:30:35.691 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
org.openhab.binding.paradoxalarm.internal.exceptions.ParadoxRuntimeException: Unsupported panel type: MG5050
I have been unsuccessful in making this work.
I have asked for assistance from Github ParadoxAlarmInterface/pai and have tried manually following these steps on Github: ParadoxAlarmInterface/pai/wiki/OpenHAB
but i am struggling to connect to the IP150 module and im not sure how to do that via a mqtt bridge.
Where in that documentation does it say i must put the IP150 IP address? how do i connect to it
@polychronov is it possible you can support MG5050 ?
I tried the Addon Binding but as stated it says “unsupported panel”.
However within the code openhab-addons/bundles/org.openhab.binding.paradoxalarm/src/main/java/org/openhab/binding/paradoxalarm/internal/model/PanelType.java at main · openhab/openhab-addons · GitHub it is listed here.
If it could just be allowed to add this panel, maybe it will just work with autodiscover, since it might be similar to the EVO panels.
Can anyone guide me to manually get this panel working? even if its via textual configuration approach.
The Wiki guide on PAI Addon is missing some information it seems?
Hi,
unfortunately it’s very hard to implement it for a panel that I don’t have, as there is a lot of byte-code programming and too many issues while it can be stabilized. Moreover now I don’t have time for such a massive development.
I would advise that you use maybe PAI with some MQTT broker (if it’s supported).
Cheers,
K.