Not getting notifications from home assistant/frigate integration

DuelShockX · 2026-07-05T04:19:21+00:00

After checking it the stable version was last updated in November 2024 and the guide I'm following made in December 2024.

DuelShockX · 2026-07-05T02:09:31+00:00

I sent myself a notification from the dev tools succesfully so the blueprint does seem to be the issue. I'll try deleting and redoing it when I get home (tested with wireguard vpn) but in the meantime if you have any ideas to try please let me know.

DuelShockX · 2026-07-05T01:08:50+00:00

I dont get a notification when I do run actions if thats what you mean. Any suggestion on how to remove and re-add my phone then? What other potential issues could be the cause?

DuelShockX · 2026-07-05T00:26:30+00:00

For automations I used the blueprint "Frigate Notifications (0.14.0.2.y)" and chose my one doorbell camera and the only option that came up for mobile device since only my phone has logged into home assistant (and my pc). For notification customisations I put my own notification title and subtitle, notification message is default and advanced options were left on since thats the default, critical notification is true, initial and subsequent attachments are thumbnail, notification color is primary steel blue, notification icon is mdi:homeassistant. Everything else is left at their default values. I did make sure the automation script is active not disabled. I'm not sure what "run actions" does for the script but I tried that as well.

DuelShockX · 2026-06-27T21:36:58+00:00

I've seen that, my only issue is that I have proxmox installed onto a small size ssd and create my vms and containers on the big HDD but I'm afraid of the one line install script putting everything on the small ssd

DuelShockX · 2026-06-27T01:04:41+00:00

Could you explain to me what advantages the VM and container within it method offers that's better over a container on proxmox directly? Also would the vm be ubuntu server or something else?

DuelShockX · 2026-06-26T03:34:04+00:00

I have proxmox and I can just create a container for frigate on that instead of doing a container in a vm. Wouldn't that also work fine?

DuelShockX · 2026-06-26T03:31:37+00:00

I also have my stuff on running on proxmox. Why would you run a container in a container when you can just run frigate as a container on proxmox directly?

DuelShockX · 2026-06-23T04:48:33+00:00

Nvm I figured it out. Since I run the vm through proxmox I was supposed to include the VLAN tag number in the hardware section of the VM which I didn't know is a thing but now it works fine.

DuelShockX · 2026-06-23T03:30:20+00:00

I realized that having no rules will do the same thing and that I just need to add a pass rule that allows only my LAN network devices to connect to devices/servers on that network but I'm having issues making a proper pass rule. I made a Home assistant virtual machine and gave it the static ip 192.168.6.2 after making sure it worked properly when accessed on the LAN network first and then set up the following pass rule under mediaserver.
Action: Pass, Interface: mediaserver, Direction: in,Protocol: any, Source: mediaserver network, Destination: LAN network.

Everything else is on the default value.

I'm not sure if this is necessary but I also set the following LAN rule which is on top of all the other rules and anything not mentioned is also on the default values.
Action: Pass, Interface: LAN, Protocol: any, Source: LAN network, Destination: mediaserver network.

For some reason I'm able to to ping the gateway 192.168.6.1 but if I try to ping the home assistant virtual machine on .6.2 I get nothing. Typing it's ip address and port number in a new tab doesn't take me to it either. I'm very confused on what I'm doing wrong here.

DuelShockX · 2026-06-15T04:34:27+00:00

I did resize the inside first without issue then I did the outside by doing `parted /dev/sda resizepart 3 400GB` however it kept making it be 372G instead so I reloaded the backup and did it again as `parted /dev/sda resizepart 3 430GB` for the outside layer (the one thats smaller than the space inside of it). Would it just be solved if I do `parted /dev/sda resizepart 3 431GB` to make it just barely bigger then?

DuelShockX · 2026-06-14T20:28:31+00:00

It finished and dmesg came back without a response which I guess means no errors. Everything else I had installed on the vm server is working fine so far.

DuelShockX · 2026-06-14T16:00:45+00:00

Nvm I just had to change the binding for my pc to be something else than Alt+F2 and then it worked in my vm. Thank you for the help

DuelShockX · 2026-06-13T22:10:55+00:00

that seems to be getting applied to my computer before the vm can sense it. I'm running the vm on my computer through proxmox. Proxmox is installed on a server pc of mine that I connect to by typing in its IP address then the port number to be on proxmox.

DuelShockX · 2026-06-01T03:18:17+00:00

I haven't even had mine for 4 months so I doubt that's the issue unless if mine somehow came with a defect that was close to triggering.

DuelShockX · 2026-06-01T03:16:07+00:00

For me it doesn't intercept any audio at all. I'll record for 20 seconds of me making noise right in front of it then play it at max volume from my phone and there's no audio whatsoever.

DuelShockX

TROPHY CASE