Alexa not discovering Blue Iris
- Thread starter kclubb
- Start date
kclubb
n3wb
- Joined
- Aug 28, 2017
- Messages
- 3
- Reaction score
- 4
Thanks hitljohn. No go for me. I have logged a support ticket with Blue Iris.
I have a home-grown ceiling fan controller that controls two ceiling fans via Alexa that looks like a WeMo device, and that is discovered by Echo OK. To play nice, I just added the Phillips Hue skill (even though i have no hue controller), but that still did not do the job. I somehow feel that the UPNP is not getting past the Windows 10 firewall or something like that.
I have a home-grown ceiling fan controller that controls two ceiling fans via Alexa that looks like a WeMo device, and that is discovered by Echo OK. To play nice, I just added the Phillips Hue skill (even though i have no hue controller), but that still did not do the job. I somehow feel that the UPNP is not getting past the Windows 10 firewall or something like that.
kclubb
n3wb
- Joined
- Aug 28, 2017
- Messages
- 3
- Reaction score
- 4
I just resolved my issue with Amazon Echo. There is a Windows Service named UPnP Device Host on Windows 10 that is disabled by default. This has to be started BEFORE the Blue Iris service is started. So the steps are:
Stop the Blue Iris Service
Set the UPnP Device Host service to Automatic and start it.
Start the Blue Iris service.
Open the Blue Iris client and on Settings | Mobil Devices press Connect to Amazon Echo
Say "Alexa discover devices"
Soon a popup will open saying your Alexa has been connected, and Alexa will appear as a new device in the list.
I also have a Harmony Hub with the same camera name as an Activity and Alexa gets confused an cannot set the camera to a preset because she thinks I am referring to the Harmony device, so I renamed the camera in Blue Iris and re-ran discover.
I hope this helps others. I am forwarding this info to Blue Iris tech support.
Stop the Blue Iris Service
Set the UPnP Device Host service to Automatic and start it.
Start the Blue Iris service.
Open the Blue Iris client and on Settings | Mobil Devices press Connect to Amazon Echo
Say "Alexa discover devices"
Soon a popup will open saying your Alexa has been connected, and Alexa will appear as a new device in the list.
I also have a Harmony Hub with the same camera name as an Activity and Alexa gets confused an cannot set the camera to a preset because she thinks I am referring to the Harmony device, so I renamed the camera in Blue Iris and re-ran discover.
I hope this helps others. I am forwarding this info to Blue Iris tech support.
Unfortunately it is not working for me I have followed directions on the Blue Iris documentation as well as follow through with your suggestions for stopping the universal plug and play service but nothing seems to work BI does not connect to Alexa
Vettester
Getting comfortable
- Joined
- Feb 5, 2017
- Messages
- 743
- Reaction score
- 698
Try logging into your Alexa account through a web browser and then go into Smart Home | Devices and click on forget all. Before using the discover option to rediscover your devices make sure you go back into Blue Iris' mobile devices and enable the Connect to Amazon Echo option.
Sean Motta
n3wb
- Joined
- Dec 29, 2017
- Messages
- 7
- Reaction score
- 3
Yellow-Snow
n3wb
- Joined
- Jan 19, 2018
- Messages
- 12
- Reaction score
- 3
Same issue here on 10. Turned off firewall. Made sure it was a private network. Tried everything
doctorenos
n3wb
- Joined
- Dec 9, 2014
- Messages
- 1
- Reaction score
- 0
I had also tried all the information given previously on this subject, but no success. I found the following document on Alexa development (snip-it):
When developing and testing your Alexa skills in a corporate environment, you might need to
know the TCP/UDP ports that Echo uses so that they could be opened on a corporate firewall,
allowing developers to connect Echo to the network for testing. Please note that Echo is a
consumer device and at the moment does not support enterprise networks directly. Therefore,
you will need to create a personal/consumer Wi-Fi network to be able to use Echo within your
company’s network.
Here is the list of ports you need to open:
* Output TCP: *, 80, 8080, 443, 40317, 67, 68
* Output UDP: *, 53, 123, 40317, 49317, 33434, 1900, 5000, 5353
* Input TCP: 8080, 443, 40317
* Input UDP: 53, 67, 68, 1900, 50000, 5353, 33434, 49317, 40317
I surmised that perhaps the reason my Blue Iris was not being discovered is that it was on a different port that these. So, I changed my port for Blue Iris to 40317(updated the router and port forwarding also), told Alexa to forget all devices, then rediscovered and it worked. This may work for someone else, I am not absolutely sure that this is the only reason, since in the process of trying to get things to work, many things are changed as we go along. Hopefully, this can help someone.
When developing and testing your Alexa skills in a corporate environment, you might need to
know the TCP/UDP ports that Echo uses so that they could be opened on a corporate firewall,
allowing developers to connect Echo to the network for testing. Please note that Echo is a
consumer device and at the moment does not support enterprise networks directly. Therefore,
you will need to create a personal/consumer Wi-Fi network to be able to use Echo within your
company’s network.
Here is the list of ports you need to open:
* Output TCP: *, 80, 8080, 443, 40317, 67, 68
* Output UDP: *, 53, 123, 40317, 49317, 33434, 1900, 5000, 5353
* Input TCP: 8080, 443, 40317
* Input UDP: 53, 67, 68, 1900, 50000, 5353, 33434, 49317, 40317
I surmised that perhaps the reason my Blue Iris was not being discovered is that it was on a different port that these. So, I changed my port for Blue Iris to 40317(updated the router and port forwarding also), told Alexa to forget all devices, then rediscovered and it worked. This may work for someone else, I am not absolutely sure that this is the only reason, since in the process of trying to get things to work, many things are changed as we go along. Hopefully, this can help someone.
looney2ns
IPCT Contributor
Forwarding ports in your router is a huge security risk. Search here for VPN primer for noobs.
Sorry to resurrect this thread, I'm having this issue as well.
Have tried setting the UPnP Service to automatic, starting it then BI, disabling the windows firewall, rebooting, setting the BI service dependant upon UPnP and several other things...
I ran a UPnP sniffer and it sees my router, Plex and several other devices but it does not see Blue Iris while it's in discovery mode.
Have tried setting the UPnP Service to automatic, starting it then BI, disabling the windows firewall, rebooting, setting the BI service dependant upon UPnP and several other things...
I ran a UPnP sniffer and it sees my router, Plex and several other devices but it does not see Blue Iris while it's in discovery mode.
