Random Ideas for the Roadmap

[mtwo]

Figured I'd add some random ideas here, not in any particular order:

• Make NeoHub able to run directly on Home Assistant, either as an app (previously called add-ons), or by rewriting it into Python and having it run natively as an integration by merging it into NeoHub-Home-Assistant-Integration. A native integration would be preferable (it would be easier to set up and would enable auto discovery), but would be way more work.
• Adding a function to bypass zones. The most useful would be a quick action to bypass currently open zones, equivalent to pressing **<<**## on a keypad. Could also be useful for temporarily bypassing smoke detectors while cooking.
• Long-term I suppose that it could be nice to bring in some management features like creating / destroying codes, renaming zones, etc. However this isn't nearly as critical as the stuff that has already been delivered and likely requires a fair amount of work.

[piotrantosik]

Make NeoHub able to run directly on Home Assistant, either as an app (previously called add-ons), or by rewriting it into Python and having it run natively as an integration by merging it into NeoHub-Home-Assistant-Integration. A native integration would be ideal, but would be way more work.

Building an HA app is the way to go. This/next week I’ll try to connect my DSC with NeoHub and HA, and I can help with the work on this.

[piotrantosik]

writing also here for visibility, my suggestion about HA APP: #8 (reply in thread)

[BrianHumlicek]

So, one of the driving forces behind creating the protocol documentation is so an agent can leverage that to recreate it. I'd be willing to bet that Claude could probably generate a monolithic HA integration with the information in this repository. I might even give it a go when I get a minute. If someone else wants to take a run at it, be my guest.

Brian

[BrianHumlicek]

Regarding the Zone bypass feature; ironically despite my technical immersion into the ITv2 protocol, I know relatively little about the panel and what it can do. My first time actually arming/disarming my own panel that I have been testing with was immediately before I started testing the Arm/Disarm functionality of NeoHub a few weeks ago. I'll brush up on what it can do, and see if I can figure out how to make it happen from NeoHub and then make it happen from Home Assistant.

[piotrantosik]

I added autodiscovery in app and integration - piotrantosik/neohub-ha-app#1 and BrianHumlicek/NeoHub-Home-Assistant-Integration#3

I'm thinking about how to set the device class. Currently, NeoHub reports everything as a door. The DSC panel doesn't provide info on the device type—whether it's a motion sensor, smoke detector, etc.

What do you think about adding a zone settings section in NeoHub? Something like mapping Zones to Device Classes? Of course, this can be overridden directly in HA, but I’m not sure if that’s the ideal solution.

[nfreeze]

I have a node.js implementation of ITv2 protocol and am stumped on how to bypass zones. If someone can do a wireshark capture of the ITV2 traffic while bypassing a zone from the DSC phone app, we just need to see 2-3 packets from the server side right around the bypass. The 0x0820 confirmation from the panel will bracket it so we know exactly which packets are the bypass command sequence. Should be a quick implementation once we see the wire format.

https://www.npmjs.com/package/dsc-itv2-client

[nfreeze]

Actually I just figured it out:

1. Send 0x0704 (Enter Config Mode): [Partition VarBytes][Type=0x03][AccessCode ByteArray][Mode=0x01]
   - AccessCode = raw digit values, one byte per digit: "1234" → [0x01,0x02,0x03,0x04]
   - NOT ASCII, NOT BCD — panel rejects both with InvalidUserCredentials
2. Wait for 0x0702 (Config Status) notification (~250ms) — COMMAND_RESPONSE is just an intermediate ack
3. Send 0x074A (Zone Bypass Write): [Partition VarBytes][Zone VarBytes][BypassState 1B (0x01=bypass, 0x00=unbypass)]
4. Panel confirms via 0x0820 (SingleZoneBypassStatus), often batched in 0x0623
5. Send 0x0701 (Exit Config Mode): [Partition VarBytes]

// 0x0703 (AccessCodeWrapper) is not supported on Neo — returns InvalidCommand.
// 0x074A without config mode returns 0x10 (Not In Correct Programming Mode).

[piotrantosik]

Confirmed, it's working. I've already started a few fixes in NeoHub, so I'll prepare the bypass implementation right away.

[BrianHumlicek]

This is awesome! I have had to change gears and focus on some other projects for the moment so it's great to see the needle keep moving on this!

Test it out and make a pull request and I'll merge it in.

Thank you all again!
Brian

[Villhahallon]

Would it be possible to get images from the wireless IR cameras and pass them to the neohub or even home Assistant ? 👀

If no other is running these I would like some pointers to see if I could get it goings myself

[BrianHumlicek]

I didn't even know they had cameras. I guess let's start with what do we know about them. Do they connect to Ethernet? Where can you view the feed, in app, on the keypad, or?? How many cameras?

Brian

[Villhahallon]

they have a panel that acts as the wireless receiver. I have multiple wireless zones connected. all with battery. The camera sends an image when it's activated in an armed area. I'm a bit lost in how it worked but I know it would send the image to the alarm receiver company when it was active. I think the dsc app also had the images. Not sure if any live view was possible.

It is the Power G products, I'm using the PG8934 IR currently link
and the panel is called HS2LCDRF link

It works well with Neohub :)