-
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
if nodered runs inside a docker container, ip-address is wrong #4
Comments
https://git.restis.ch/nicolas/node-red-contrib-mystrom/ i created a fix that works with the GUI, but breaks backwards compatibility for the offset field.. unfortunately I could not create a new branch on this repo here to create a pull request.. if anyone wants to use it: |
Any news on this? There is more or less a solution free to merge. |
Hi all, This repo is no longer actively maintained (as far as I know). |
Funny. Why is then this repo actively linked on the MyStrom Website and here on NPM is a big banner with MyStrom <3 NodeRed? 😏 |
the problem
if you run nodered inside a docker container and want to configure a mystrom button,
the internal (docker) nodered ip-address will be sent to the button instead of the real one (the one of the device running docker).
The button then thinks it has to call the docker-internal ip address instead of the ip-address of the device. Of course the request will never reach nodered.
possible longterm solution
it would be nice to define the 'real' ip-address in a field in a way like the field 'offset' (that already exists)
quick fix
tech-savy persons can just define the request to nodered themself by using the mystrom-button api. (via POST
/api/v1/device/5CCF7FXXXXXX
)The text was updated successfully, but these errors were encountered: