GalaxyGuy

Sorry James, only just seen your post. The SelfMon vmod provides a hardware gateway for MQTT on Galaxy (G2, G3, Dimension Flex and even the older Classic). This offers very low latency zone and output status, along with virtualised peripherals all available via MQTT. The module implements multiple virtualised devices including: Virtualised keypad - providing control via MQTT or HTTP Virtualised printer - providing MQTT status of any printed output like alarm triggers Etc. Virtualised RIO modules - providing virtual zones on the control panel to enable MQTT based zone status change and reading of 'linked' outputs Virtualised RF portals - enables mimic of fobs and other RF devices. Providing full/part/night and unsetting via MQTT All zone reading and group status in MQTT available via SIA4 connection to Honeywell Ethernet module Virtualised E080 module - for Dimension, Flex V1, G3, G2 and Classic control panels - supports Honeywell's RSS and GX app encryption along with SelfMon apps (note GX app is only compatible with Dimension and Flex V1) SelfMon encrypted reporting - secure transmisison on a separate MQTT channel An overview is available here: http://www.selfmon.uk/manuals/LCE-K3/LCE-K3-OVERVIEW.pdf

Yes, all G2 panels can be brought up to 1.56. This requires a flash lead or the same can be achieved with a low cost USB TTY lead and a jumper wire.

All sounds fine. 1.56 is the latest firmware, with 1.53 being suggested minimum for SelfMon. You may need to disable the RF portal virtual RIO if it ends up grabbing RIO address 2 that you set on the c072. You can disable the rf portal virtual RIO in menu 51.60

With zones set to NC, you then consume two zones to cover zone and tamper circuits. This is a bit of a waste of zones when you can cover the tamper open/short circuits with the addition of resistors.

You can set the Galaxy zones to N/C like your old system. Each zone can be programmed individually on Dimension and Flex. I would recommend reconfiguring with new sensors or the addition of resistors (I've never had a problem adding 2x 1k resistors in existing sensors for double balanced zones). It may be worthwhile changing the PIR's anyway, as they're very cheap and the pyroelectric element in the sensors do deteriorate over time reducing their sensitivity.

I only have FX100+ PCB's at £90 + £5 delivery. PM me to arrange if you want. Otherwise, the boards aren't sold separately and you'll need a complete panel.

One ISP is my broadband and the other is the mobile provider, so yes not the same provider for me.

On my own system, with dual path IP at the router level, it just doesn't go down, so there aren't any annoying Comms messages. I only worry when I get an intrusion signal or polling failure which means both paths are down and I really need to take action. Hasn't happened yet. Touch wood. Any messages for one of the paths going down would just be extra nuisance due to ISP reboots, temporary mast issues and the like. I see installers moaning about this sort of thing all the time on FB installer forums. I'd much rather have a multi failover IP path that then relies on very short poll intervals. As long as there's a good link between the panel and ARC with secure comm's, then I don't really care what path that link is. With today's network capabilities, we'll probably move to 'always connected' ARC's anyway.

My thoughts on this are to have a battery backed GPRS capable router in a secured location. This offers better future proofing, as it's not just the alarm that needs to keep communications up if there's a broadband / phone line issue. There's CCTV, HA and more. It's more efficient to have an unlimited data SIM, rather than 3 separate SIM's to track and pay for. It's also easier to keep up with the latest tech. I'm already 5G capable - just waiting on my area being upgraded. If your hone network has its own failover, then all you need is polled monitoring with a decent polling interval to alert you of a missing heartbeat.

It doesn't perform set/unset with Galaxy programming. It only performs silent pa. The Selfmon solution is part of home automation integration, so requires mqtt broker etc.

Where do Honeywell say that? Not for Galaxy anyway... Perhaps Domonial. The only way to do it with the flex is with the Selfmon vmod and an automation platform like home assistant / node red etc. The vmod reads any button press to mqtt, so you can then map it back to set the system.

No reboot is required when changing 51.82. Change 51.82 to DC. Using menu 53 program output *99 to something like strobe. Leave at the default which should be L (Latching) POS (positive). Using test option 32, test the strobe output. Measure with your meter on +12V and OP3. The voltage on OP3 should drop to 0V resulting in the meter reading +12V. If this does not happen, then OP3 is faulty - replace the PCB or add a RIO to gain 4 outputs.

Did you change menu 51.82 to change OP3 to: 2 (DC Output) ? The default for OP3 is as an audio output. The trigger module consumes OP1 and OP2, using these signals to multiplex several outputs. Those outputs include new OP1 and OP2 and the 8 trigger outputs. The trigger outputs are low current, but capable of driving a dialler.

I would agree with this. If you don't keep your phone up to date, or buy the latest model and the app isn't kept up to date, then the chances of issues are high. If you have a look at a few apps reviews, you'll soon see posts of unhappy users where phones and OS versions no longer work. As a an app developer myself, I am often forced to update the app in order to keep provisioning on the stores. Some of these forced updates end up dropping support for older devices, leaving users with very old devices none too pleased.

Personal experience. What aspect ?

The Honeywell Galaxy Flex gives all this. Honeywell provide the flash upgrade program and firmware on their website without any login account requirement too. The app and push notification is free and there are low cost alternatives in the event that Honeywell do start charging. Look out for other offerings that integrate cloud services tightly with the panel, as they may not charge at the moment, but you could find yourself held over a barrel in the future.

This has nothing to do with manufacturing quality. It's a country specific setting and depends on the country code / settings selected. OP, if you have picked up a second user panel, set it to factory defaults using menu 51.17 - cold start. If the tamper still exist after that (with the link fitted), then the panel has a fault.

You need to program a link from the silent PA output to the bell output. This will not work on a trigger output, it needs to be a proper output.

Not for me now. I think it's two years since I installed a system and I was totally shattered after an 8hr install. It's much easier selling the kit.

I already had various lighting circuits, heating and garage door controlled by the Galaxy, so now connected through the echo dot. However, my wife does not want the dot in any of the main rooms, so it's in my office. I want each of the rads controlled, but would rather have 12v devices as don't really want to be messing with batteries - not really an option though. Some of the retrofit blind controllers seem a bit big.

Yep, £3k for a sofa which is basically pallet quality wood, polystyrene and fleece wrapped in fabric. Huge markups. Same with beds. Easier than crawling around in attics and under floors...

Combinations of Node-Red, MQTT and Home assistant make for some nice integrations not bound by the logic of an alarm control panel. SelfMon customers have already started building on top of the MQTT interface to the Galaxy panels. I agree that this needs to be more plug and play though. Most setups require too much fiddling with config files. It's not complex, just requires knowledge of all the config file options. A bit like configuring alarm control panels...

What firmware level is the panel at and which address have you set the portal to?

Test the board is working by placing a wire link from 0v to T. If the tamper issue is then resolved, the issue is in your sounder tamper circuits.

I've not gone back to older versions to check, but did start seeing it in W10.