Latest news for those, who stuck on Paradox IP150 module with v4.xx firmware. I managed to downgrade it back to v3.01! I again can use direct BabyWare connection to configure my panel!!!
I will wait few weeks, until more people, who have same problem, will see this message ant then will share all the tools and instructions how to do downgrade. Until this time I’m recommending disconnect IP150 modules from internet. IP150 firmware from V4.xx updates itself on every IP150 module power cycle, so Paradox can fix their bugs and release update, which can remove possibility of downgrade.
My final conclusion about Paradox - DO NOT TRUST THIS COMPANY AND DO NOT BUY THEIR PRODUCTS ANYMORE!
I pointed them with finger to their security holes and they even didn’t fixed them all in two weeks time. They even didn’t said “Thank you” to me… because swear words are not allowed, i don’t have what to say anymore about this company.
Anyone interested in an updated script for SP based devices, obviously I can’t test other devices since I only own an SP7000.
It’s a fork of @Tertius_Hyman’s original…and so if wanted, or can possibly be merged back in…if it’s compatible with EVO and other devices.
If you’re already running it, maybe take a backup, updates are coming thick an fast as I make changes, and some of them are breaking as I test on one machine then run on another - and I see faults as they come up.
update: I changed some options in config.ini and I got mqtt messages under Paradox/Labels/# but still no Labels:
Pincode: #### ;PC Password (from Winload/Babyware)
Mqtt_Username = paradox ;MQTT username, without qoutes
Mqtt_Password = passwd ;MQTT password, without qoutes
Alarm_Model = ParadoxMG5050 ;Currently not used
Alarm_Registry_Map = ParadoxMG5050 ;This is used to map to the correct dictionary class within the ParadoxMap.py package. The word "Registers" is appended before loadi
Alarm_Event_Map = ParadoxMG5050 ;This is used to map to the correct dictionary class within the ParadoxMap.py package. The word "EventMap" is appended before loadin
Zone_Amount = 32
Topic_Publish_Events = Paradox/Events ;The main topic used to publish all events
Events_Payload_Numeric = 0 ;1=Events are reported using numeric value [not replaced by the dictionary]. 0=Events are translated to more meaningful text from the
dictionary, if your alarm is supported.
Topic_Subscribe_Control=Paradox/C/ ;All controls are given through this high-level topic
Startup_Publish_All_Info = True ;Upon startup publish all labels from the alarm (configured names of things), only application when reading (updating) labels
Topic_Publish_Labels = Paradox/Labels ;The topic used to publish labels
Topic_Publish_AppState = Paradox/State ;Publishes the scripts internal states, useful to check if connection is alive
Topic_Publish_ZoneState = Paradox/Zone ;Publishes the zone status' with the zone name as the next topic group (1 for open, 0 for closed)
Topic_Publish_ArmState = Paradox/Partition ; Publishes the partition status 1 for armed, 0 for disarmed.
Topic_Publish_Heartbeat = Paradox/Heartbeat ; Publishes a periodic message, and it a last will and teastament of the mqtt connection
Topic_Publish_Status = Paradox/Status ; publishes specific parts of the 6 zone status messages (0 - 5)
Publish_Static_Topic = 1 ;Publish events emulated as topics, E.g. Paradox/Events/0/20
Debug_Mode = 0 ;0=Minimal, 1=Basic, 2=Verbose
Startup_Update_All_Labels = True ;Upon startup collect all labels from the alarm (configured names of things). Required for config item: Topic_Publish_Labels. If you
see the script stuck at trying to update the labels, then disable this option
Log_File = /var/log/paradox/paradox.log
Auto_Logoff = True ;When detecting another 3rd party connection to the IP module, logoff for the Logoff_Delay duration (3rd party connection ma
y need to re-attempt their connections
Logoff_Delay = 120 ;Delay before reconnection after a 3rd party connection attempt
Lols, I just replied with some details in message (rather than in public).
So now you’re getting the voltages etc off the panel, and panel date time? Plus all the label ids? have a look in the logs (they’re quite noisy) you’ll see almost every 6 seconds your zone statuses and partition statuses.
There’s two config items one for update/read all the zone labels and one for publish them. Make sure they’re both on. TBH I never played with the labels topics, so can’t actually confirm if they work…I prefer to list them all in the Paradox/Zones/ topic.