Custom Component: Crow Runner / Arrowhead AAP 8/16 Alarm IP Module

Share your Projects! Custom Integrations
224

this is awesome - thanks so much everyone for developing this - especiall @febalci … only wish i found it before I purchased a load of Konnected stuff. I have just flashed my IP module with the firmware from 2017. telnet via putty gives me a NOP status. I’ve installed the custom_component “crowipmodule” from GitHub - febalci/pycrowipmodule: Async API package for Crow/AAP IP Module but my home assistant is throwing:

ModuleNotFoundError: No module named ‘pycrowipmodule’

File “/config/custom_components/crowipmodule/init.py”, line 83, in async_setup
from pycrowipmodule import CrowIPAlarmPanel

can anyone tell me what i’ve missed?

thanks!

225

Hey @paulthemann , nice that you join our tiny group. It looks like there are 2 problems:

  1. telnet giving NOP status:
    Make sure the flashed firmware version is the custom firmware “Ver 2.10.3628 2017 Oct 20 09:48:43”. You can check it from the home page of IP Module settings webpage. If the version is correct, try to telnet to the IP Module (with the port you defined in IP Module web settings, it is probably 5000, 5001 or 5002). On connection, write STATUS with all upper case letters and press enter button. If the status comes back than everything is OK.
  2. pycrowipmodule Module not found: For whatever reason, HA did not downloaded the required pycrowipmodule python library. Normally, when you install a new custom component, HA looks into its manifest.json file and downloads the library which is indicated in the “requirements:” section from pypi.org automatically. But in your case it did not. You can delete everything from the custom_components/crowipmodule directory and reinstall the custom component once more. Make sure including the manifest.json file there should be a total of 7 files in that directory (The 7th file is CHANGES file which is not important). If you still have problems drop me a message, in pypi.org there is a v0.27 and also a v0.27b0 which may confuse HA so the second file might be the problem.
226

Added version key in manifest.json as per new HA requirements. Forgot to put a comma there but since @paulthemann warned me, i corrected it on github. Now his copy seems working as well. Thanks @paulthemann.

1 Like
227

Hey Guys,
Sorry I have not been around much (real life gets in the way!) but it looks like you had loads of progress on this component!
So it seems that others have had the IP module disconnection issues that I was having… What was the solution in the end? Was it putting the IP on its own VLAN or did something get changed in the code?
If I can get a reliable connection then that will be great, I was thinking of going the Konnected route but then I thought, No we can fix this…

228

For me it was 100% fixed by putting it on its own VLAN. There was definitely something on the main LAN sending packets that caused it to lock up.

229

OK, Thanks. Just need to figure out Vlans on my USG now. Never done those before.

230

Same for me; separate VLAN completely fixed my disconnection issues. It’s been rock solid for the last 6 months.

231

Ah thats great news.

So, last night I tried to set this all up. I have HA running in Proxmox and use a Unifi USG and AP’s.

I dont suppose you guys have any experience in these do you?
This is what I have done so far-:

  1. In Proxmox added another NIC to my HA VM.
  2. Went to my Unifi (HA Integration) controller and setup (or I think I did) a Vlan just for my alarm on 192.168.2.0
  3. Went to my alarm Web Gui and set my alarm IP to 192.168.2.90
  4. Used IP scanner and confirmed I had the alarm on the above IP and could also see the USG from my desktop.
  5. I also checked that I was able to ping my alarm from my desktop on that network. That was fine also.
  6. Next I used the HA Terminal and logged in. When I typed nmcli device status, it showed that HA now had two IP connections. They were both connected. (this confused me as other threads suggest I would have to connect the new one and name it. Also when I got into the terminal window, below where it says ‘Welcome to the Home Assistant Command Line’ it showed that HA had picked up the VLAN that I had created in the Unifi Controller.
  7. Changed the IP address of the alarm in the Crow setup in my Config.yaml

The component is reporting that it can not connect to the IP module…

Any ideas?

Cheers

Simon

232

@jokkydee @mish

So what do you guys have HA installed on or in?

I can not for the life of me figure out how to get my system working on a VLAN…

Cheers

233

Hi @Crumpy10 , sorry for not replying sooner. It’s been a while since I set up all the VLAN stuff, and once I got it working I forgot about it, but I’ll try to be as helpful as I can. Please ask if anything doesn’t make sense and I’ll try to look into it further.

So, I’m running HA operating system on a VM, using Virtual Box, on a Dell Optiplex i5 machine that is running Windows - it has one hardware ethernet NIC and this NIC supports tagged VLANs natively (It is an Intel I219-LM adapter to be specific). Using the Intel PROSet Adapter Configuration Utility in windows, I created 3 VLANs - ID 0, an untagged VLAN, ID 20, a tagged VLAN for IP cameras, and ID 30, a tagged VLAN just for the alarm. Once I did this, I could see 3 virtual NICs in Network Connections in my windows environment. “MAIN” is the untagged VLAN, which has access to the internet.

image
image1033×156 10.9 KB

The NIC is connected to a managed switch - which deals with routing tagged packets to and from ports on particular VLANs. So my crow runner alarm is connected to a port on my managed switch that has ID 30 VLAN tags attached to it if sending out, and will only receive incoming packets that have ID 30 tags attached to it. The only way the Dell Optiplex NIC can talk to that port is by using the ID 30 virtual NIC.

Now, in virtual box settings for the HA VM, I have exposed two Network Adapters to it. The virtual NICs of VLAN 0 and VLAN 30, as you can see below. These now appear to the VM as two hardware NICs.

image
image

Then, inside HA, I used this guide https://community.home-assistant.io/t/setup-vlan-and-ha-tutorial/87705/6 to create two connections

image

So you can see here which one is the tagged VLAN 30 for the alarm system (enp0s3).

image

I used the IP subnet 10.0.30.x for VLAN 30. HA has the IP address 10.0.30.2, and the Crow Runner is 10.0.30.3

Then, in my config,

image

Not sure how helpful this will be, but hopefully you can get it working.

234

@Crumpy10 I seem to remember having to change or play around with the device names, as I don’t think I had “enp0s3” and “enp0s8” initially… I can’t quite remember what those names mean, but I seem to remember them being important.

By the sounds of it, everything outside of HA seems to be working correctly, so I do wonder if it is down to the nmcli configuration. You may need to delete one or more of those devices and create it again. At least I would suggest making sure you have this part correct.

EDIT: The other thing you may also want to check is that the IP subnet mask is correct. You can see in my case for enp0s3 the subnet mask is /24, meaning 255.255.255.0. I can’t remember if mine was /24 by default. I read that others needed to change this from /8 to /24.

235

@jokkydee Thanks for taking the time to write all this out.
I still havent got it working but what I have done is change a lot of the settings on my alarm through the ULD16 software. I was getting a lot of dialer errors, which I have now sorted out.
FYI in the Ip module install info, its says to enable the dialler. This was giving me errors on my keypad as no phone line is connected. So I tested to see if the IP module still sent out the zone open and closed messages through the module and it does. So I am wondering if thats all had something to do with the issues we have had. Anyway, it been fine for over 24 hours now, only time will tell.

236

Well this module has been working 100% for me and is amazing. Thanks for everyone involved especially @febalci

I’ve now got it in some automations included auto arm at night / when everyone leaves the house. Auto disarm in the morning / when someone comes home.

The last thing I want to do with it is manually trigger an alarm… like the panic button.

any ideas? Do I need to look at relays?

Thanks!

237

Using one of the relays on the IP module would probably be one of the quickest and easiest ways I would say. Make a new zone and have the relay short it. I’m not sure if there is another way to do it without involving actually triggering a zone electrically.

238

Thanks @jokkydee

I’ll need to do some digging to be able to do this!

239

Well in fact there is a “PANIC” command for the IP Module. I do not remember it explicitly if i implemented it or not. Let me check and get back to you, if not, it is very easy to do it. But i need about 2-3 weeks; sending my son to UK for college next week, lots of things to do…

240

Thanks @febalci

I can see the declaration for async_alarm_trigger in alarm_control_panel.py but as far as i can tell it doesn’t do anything…I might have a play if im feeling brave enough

241

I don’t have the manual to hand but I recall there being a KEYS command that sets the panic siren off. You should be able to do it all in software, no need for additional relays. I remember this because I did some experiments and set my sirens off and it was obvious in hindsight!

242

Btw have you tried the service “alarm_control_panel.alarm_trigger” to trigger a panic alarm? It “should” be working but if not at least i know now where to start…

244

Hi Frederico, we are all using 2.10.3628 which was prepared back in 2017. Did AAP offered you another version? Because what you wrote above looks like the version number is the same? Additionally, if there is a new version, personally i do not know the details; and i am not so sure that it will work well with the current custom component since it was specifically written for 2.10.3628.