You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
first of all, this is a great piece to query AVM Smart Home devices. It is working great on my local node-red installation when i am inside the same network as my fritzbox.
How can I access the fritz box using a different port using a secured connection. eg. SSL port is set to a value different than default ports?
I am trying to access the FB using a secure gateway client (IBM Bluemix). This creates a gateway host with an endpoint/port that gets forwarded to the client inside my network. The port created by the gateway can not be selected/set to the default ports for the FB.
After having a short look at the sources it looks the node is currently using http only (not sure, i'm new to nodejs).
One last question:
The version of node-red-contrib-fritz pulled with npm install is 0.2.0 while this is 0.3.0. How (frequently) does this get pushed to the npm repo?
Sven
The text was updated successfully, but these errors were encountered:
Hello,
first of all, this is a great piece to query AVM Smart Home devices. It is working great on my local node-red installation when i am inside the same network as my fritzbox.
How can I access the fritz box using a different port using a secured connection. eg. SSL port is set to a value different than default ports?
I am trying to access the FB using a secure gateway client (IBM Bluemix). This creates a gateway host with an endpoint/port that gets forwarded to the client inside my network. The port created by the gateway can not be selected/set to the default ports for the FB.
After having a short look at the sources it looks the node is currently using http only (not sure, i'm new to nodejs).
One last question:
The version of node-red-contrib-fritz pulled with npm install is 0.2.0 while this is 0.3.0. How (frequently) does this get pushed to the npm repo?
Sven
The text was updated successfully, but these errors were encountered: