It’s similar in spirit (talking locally to an alarm panel and exposing zones / arm / disarm), but it’s not the same setup.
That GitHub project is built for their Hunter Pro panel and requires extra hardware – the “home automation kit” or a net4pro / serial connection plus a Raspberry Pi (or similar) to sit in the middle.
The project I’m working on uses the newer firmware on my panel, which already exposes a TCP connection directly on the LAN. I’m not using the home-automation kit or a serial link at all – just the built-in network connection, with Node-RED as the TCP bridge and Hubitat on the other side.
So: same general idea (local alarm integration), but different hardware path and a different integration stack.
The general idea is similar, but the software and protocol are not the same.
The GitHub project you linked uses a different communication method (their hardware add-on / serial / Net4Pro interface), and that interface uses its own protocol layer designed for that specific hardware.
In my case, the panel’s new firmware exposes a completely different TCP protocol natively over the LAN.
No extra hardware module, no serial bridge.
The frame structure, commands, counters, keepalives, and event format are unique to this firmware and are not compatible with the protocol used in that GitHub project.
So in short:
• Conceptually similar (local alarm integration)
• Technically different (different hardware, different transport, different protocol)
