-
Notifications
You must be signed in to change notification settings - Fork 5
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
Can you add port # as an option? #1
Comments
Thanks for the feedback. Please have a look at version 0.6.0 |
Cool I'll try it out a bit later and let you know how it works. I've got a mix of models so it should be a good test. Thanks! |
This is good:
I've got the node updated with the appropriate port and it worked great. I'll add the others on my network to the mix and report back just to make sure there's not something crazy going on with multiples. |
That seems to work. Thanks! |
Thanks for testing. Do you mind listing the model types, that you used? Would be helpfull to have a list of verified models. |
Here are the models I have:
|
Thx! Added the models to readme. Might be useful for other users. |
One of my receivers uses port
49154
as the port fordesc.xml
Any chance that can become a config option on a per-receiver basis?Also, due to the failed web-request node red completely dies so it probably needs a bit more bullet-proofing in place:
The text was updated successfully, but these errors were encountered: