Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WeMo Emulation Port assignment/visiblity #7738

Closed
hyukishi opened this issue Feb 14, 2020 · 7 comments
Closed

WeMo Emulation Port assignment/visiblity #7738

hyukishi opened this issue Feb 14, 2020 · 7 comments
Labels
awaiting feedback Action - Waiting for response or more information troubleshooting Type - Troubleshooting

Comments

@hyukishi
Copy link

Have you looked for this feature in other issues and in the docs?
Yes
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
Somewhat, the issue is that my WeMo emulated devices are not easily found even when using the static configuration because the port is required. So finding the port is the problem.
Describe the solution you'd like
A clear and concise description of what you want to happen.
The solution would be to add the ability to assign a port to the WeMo emulated device or at least making the port visible on the same configuration page that the enable WeMo emulation feature is on.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I've tried using nmap, however since the WeMo emulation uses UDP ports, they are not caught in the scan of the target device.
Additional context
Add any other context or screenshots about the feature request here.

(Please, remember to close the issue when the problem has been addressed)

@ascillato
Copy link
Contributor

If you change the port of the Emulation, the rest of standard softwares won't be able to find your device. Seems not to be a good option to change that.

As in older issues, seems that your issue is that multicast is not enabled in your router or it is using an old version of igmp. Try changing your router configuration.

@ascillato2 ascillato2 added awaiting feedback Action - Waiting for response or more information troubleshooting Type - Troubleshooting labels Feb 15, 2020
@hyukishi
Copy link
Author

Made sure multicast is enabled on my router. Still unable to add the WeMo emulated device to my home assistant installation. I'm trying to get away from mqtt whenever its not absolutely necessary for my use case.

@Jason2866
Copy link
Collaborator

How have you checked that the udp traffic is reaching the endpoint(s)?

@hyukishi
Copy link
Author

To elaborate on the issue, WeMo emulated devices show up in Alexa just fine. The issue comes with trying to discover them in home assistant. So yes, UDP traffic is reaching the endpoints for certain.

In Home Assistant it is strongly recommended to define the port used by the emulated WeMo device that you are trying to discover in it. Does anyone know of a default port that is assigned for WeMo emulation in Tasmota?

@Jason2866
Copy link
Collaborator

Jason2866 commented Feb 15, 2020

Do you have a Alexa device (hardware)? Without it will NOT work.
WeMo and HueEmulation from Tasmota is designed and tested only to work with Alexa (hardware).
Using the emulations with other systems is not tested and probably will not work.
See #6086 (comment)

@hyukishi
Copy link
Author

Yes, I have it discovered with my echo dots... Discovery with Alexa is NOT the issue. Discovery in home assistant is the issue and reason for suggesting display of the wemo emulation port in the information section.

@Jason2866
Copy link
Collaborator

Jason2866 commented Feb 15, 2020

As said before you can NOT discover or use with home assistant. ONLY with Alexa.
If you knew the port it will still NOT work.
You can try. The port will be probably 50000
Just enable debug level 4 and you will see if you use Alexa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting feedback Action - Waiting for response or more information troubleshooting Type - Troubleshooting
Projects
None yet
Development

No branches or pull requests

4 participants