GalaxyGuy

Okay, thanks for the update. I'll look into the reordering of the message elements. Nobody had mentioned it before.

Thanks for the feedback. I'm not sure why the notifications aren't being forwarded to the watch. I test on the emulator, as I don't have an apple watch to test with. I'll see if I can pick up a watch to test with. It may make sense to reorder the push notifications, as the sequence information is less important.

Yes, I imagine most companies feel the pain of apps. You can't just write the app, then forget about it. There's various certs and backend services to manage and each time there's a major new release for a new shiny phone model, the app needs updated, causing backwards compatibility issues for existing users with older devices. I think with something like an alarm panel, it would be easier just implementing a secure webserver and decent API in the Ethernet device. At least that way, as a manufacturer, you have more control over things.

You can always opt for selfmon. At least you'll have someone to call if you have an issue with Comms. Otherwise, with the free service, you just have to suck it up until Honeywell can be bothered fixing the issue. With iOS apps it can take a while to release a new version.

It will if you have the GSM/GPRS module fitted. You can have quadruple path PSTN/Ethernet/GSM/GPRS. Totally agree they're a pain for alarm companies.

You could swap the control panel for a Galaxy G2 or Flex with RF portal and all the radio components (with exception of any wireless sounder and keypad) will be compatible with the new (much better than Domonial) panel.

Wiring multiple devices gives 1k all closed and 2k,3k,4k,5k for various states of open. However, if possible, only add one detector per zone as it's not good practice to combine detectors on the same zone - root causing problem detectors becomes more complex. The push to set is a single operation. After you have pushed once, the circuit is ignored - you can press again and it will do nothing. It certainly will not unset the system in the way a keyswitch type zone would.

Seems like a lot of hassle for £10. At least it stops landfill I suppose.

Go into diagnostics menu 61 then select latest, comm's devices sub menu and gsm module. Pressing 'ent' on the device menus will show signal strength and sim card status etc.

Just to note that the panel you're looking at on eBay is cheap for a reason. It's not new and looks like it has been a swap out. That is, the installer has a fault on an installed system and they then switch out the PCB. If you look at the PCB, you can see that the screw terminals have been used. The PCB serial number doesn't match the box serial number and that's a classic sign of this type of swap out. I suspect that this panel will not boot, so if you do buy, don't put it on the wall without thoroughly testing it. I've had quite a few people who have bought these returns - some are luck

C was the old pre - back wall tamper version.

The E1 is the European region 1 which includes the UK with English and settings that comply with UK standards for a grade 3 panel. E2 Etc are for other regions and include various languages and country specific settings If in the UK, make sure you get an E1 at version 7.03. There are a few customer returns from Europe being sold on eBay.

No, RIO's are not compulsory. There are 12 wired onboard zones on a Flex and 16 on a Dimension. Only if you need the additional wired or wireless zones, then you will need a RIO or RF portal. I'm saying that you really don't want to limit the panel capacity, as when you add more home automation based sensors, then you can easily reach the panel 12 zone capacity. If you buy an FX100+, then you can start at 12 hard wired zones and expand at a later date if you need to. The + panels also support many 'links' which are needed for home automation. There is no tie-in wit

The development is a SelfMon product and will eventually support an MQTT based receiver at the SelfMon side and transmit panel SIA events via MQTT. As you can see from the image above, the virtual RIO devices have 8 inputs and 4 outputs and I've enabled 4 virtual module addresses on the test panel. The outputs are driven by the panel and can be forwarded links of zone status or just standard outputs like bells, set, etc. The panel sees the module as if it were a hardware RIO. When the output is set by the panel, the module forwards the status change to the MQTT server (broker) and it can be

jelockwood, have you tried this and managed to get it to run? I tried with npm and docker on my mac, but although it seemed to build, the image would just exit with no messages. I have an FX100+ sitting testing on the bench to test the software out. I've not used typescript at all so I may be missing something. These new abstracted languages seem really convoluted sometimes. Just a bunch of yaml files with abstract commands. Great when they work, but not so great when there's an issue. I don't think the author ever responded to previous questions, but his repo build instruction is definitely