Version 4.5.8.5

Correct me if I'm wrong, but doesn't 0.0.0.0 act as a wildcard? Doesn't that effectively allow ALL IPs negating the filter?


Sent from my iPhone using Tapatalk

I hope not. I think if I use *.*.*.* that will act as wildcard. 0.0.0.0 may just limit an ipaddress that comes from no where or itself. I think this maybe a bug with the software. Because as soon as I remove 0.0.0.0 from the limit list. Pictures won't come through.
 
I did packet captures and there is no attempted connection from the mobile device to retrieve any image. So there is either an issue with the way the push notification is sent or something in the iOS app itself which is preventing any attempted connection.
 
Last edited:
Still broken here. Pretty sure the issue is on the iOS app's side rather than server side.
Mine started working when I modified the BI web server to run on the same port number that I was forwarding through the firewall.
 
So for example, if you were using port 82 for the BI web server, yours worked after forwarding port 82 through your firewall?

I believe mine is already set that way - wouldn't it have to be in order to remotely view the cams from the BI iOS app?
 
I am already using the same port number that is being forwarded so there is some other issue as well.

I believe mine is already set that way - wouldn't it have to be in order to remotely view the cams from the BI iOS app?

You can port forward an external port to a different internal port. For example, running BI on port 81 and forwarding external port 82 to port 81.
 
Are people still having issues with rich notifications? I can't get mine to work even after trying the suggestions in this thread.
 
Are people still having issues with rich notifications? I can't get mine to work even after trying the suggestions in this thread.

They've never worked for me even after trying everything in the thread, and still don't work to this day. I don't know whether the developer even knows about the issue.
 
I think it’s been posted that he’s working on it but as with any issue, doesn’t hurt to politely let him know you’re still experiencing the issue with the version your on and you’re looking forward to having whatever feature working
 
So I have my rich notifications working after emailing the developer. Ken mentioned that they depend on the WAN IP being correct, and after double checking my setup I realized the use of a DDNS name might be tripping up the retrieval of the images. After changing the webserver to just use my actual WAN IP -- voila, it just works. Something worth trying for anyone else still unable to receive rich notifications.
 
  • Like
Reactions: fenderman
So I have my rich notifications working after emailing the developer. Ken mentioned that they depend on the WAN IP being correct, and after double checking my setup I realized the use of a DDNS name might be tripping up the retrieval of the images. After changing the webserver to just use my actual WAN IP -- voila, it just works. Something worth trying for anyone else still unable to receive rich notifications.

Already using the WAN IP and still doesn't work here.
 
Already using the WAN IP and still doesn't work here.

That's too bad, but even if that did work it wouldn't be a long-term solution as most don't have static WAN IP addresses.

What I have found is that when notification images work (usually never), by the time I click on the notification, the activity has already passed.. Tap that notification and it's a shortcut to our live porch cam which shows nothing. What works best for me is the SMS text message option in camera properties > alerts. With SMS, I can specify image quality/scale, and it's just as easy to open up app if I need to monitor what's going on based on that pic (I usually don't even do that). And I can go back in that SMS thread and see all the triggers, open up that image to inspect in greater detail. Far as I know you can't do that with notifications.

I'm genuinely curios as to why people need/want notification images vs SMS images? Is it just that tapping it opens up that live cam?
 
That's too bad, but even if that did work it wouldn't be a long-term solution as most don't have static WAN IP addresses.

What I have found is that when notification images work (usually never), by the time I click on the notification, the activity has already passed.. Tap that notification and it's a shortcut to our live porch cam which shows nothing. What works best for me is the SMS text message option in camera properties > alerts. With SMS, I can specify image quality/scale, and it's just as easy to open up app if I need to monitor what's going on based on that pic (I usually don't even do that). And I can go back in that SMS thread and see all the triggers, open up that image to inspect in greater detail. Far as I know you can't do that with notifications.

I'm genuinely curios as to why people need/want notification images vs SMS images? Is it just that tapping it opens up that live cam?

Good tip. After never having the push images come through, I was pretty resigned to just lacking the feature. Then I installed Blue Iris on a different system with a working configuration to receive regular Apple push messages, and those don't even come through! Test pushes work fine, but actual pushes triggered by the camera fail to send to 1 of my devices, but go to my other device, even though Blue Iris is saying "push sent to 2 devices".

So I just took your advice and setup SMS texts. Like you, I almost never care to review the video. Seeing a picture of the motion is fine for me.
 
Already using the WAN IP and still doesn't work here.

Well, that sucks. Ken said he doesn't know of any outstanding issues with rich notifications, so you probably want to talk with him directly to work out whatever issue is still affecting certain people's setups such as yours.
 
I emailed Ken asking about the lack of pictures on push notifications, and here is what he said:
[to receive pics with push notifications] There are a couple of requirements...

The WAN address must be valid and reachable on the login page in the app.

The WAN address must be an IP address UNLESS you are also using HTTPS in which case it can be a domain name.

On my home setup, I previously was using Blue Iris behind a reverse proxy. I was also plugging in my FDQN into the WAN interface info on my Blue Iris app. In accordance with Ken's advice, I've disabled the reverse proxy and configured Blue Iris on my iDevices to call Blue Iris via direct IP. I will post again my experiences when my cameras get triggered sometime later today!
 
I set the WAN address to the IP address instead of a domain, but still no picture push notifications. The LAN address has always been an IP, but I've never gotten picture push notifications on LAN either. I'll try switching to HTTPS.
 
Indeed. I tried Ken's proposed fixes and no success with pics with my push notifications. I'll contact him and continue troubleshooting with him.
 
Indeed. I tried Ken's proposed fixes and no success with pics with my push notifications. I'll contact him and continue troubleshooting with him.

Yeah, I'm already using those recommendations and don't have images either. I did some previous troubleshooting and saw no outbound connections from the phone to the server either. So there is either an issue in the way the push notification is being sent or something in the iOS app that is preventing an attempt to grab the image.
 
Just curious.. For those of you having trouble with this feature, why not set up SMS alerts instead? Almost identical functionality other than it not being a link to the live camera.