if nodered runs inside a docker container, ip-address is wrong

[auckenox]

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)

[NicJak]

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: simple go into your /node_modules/ and use "git clone https://git.restis.ch:/git/nicolas/node-red-contrib-mystrom.git" after this you will be able to enter the url of your docker-container into the gui for a button

[matthiasbaldi]

Any news on this? There is more or less a solution free to merge.

[Hadjimina]

Hi all,

This repo is no longer actively maintained (as far as I know).
If you open a pull request I can merge it. The only PR I see (by @NicJak ) right now wants to merge something into the development branch which does not seem correct. Let me know If you manage to create PR into the master branch. Then, I'll have a look at it and merge it.

[matthiasbaldi]

Funny. Why is then this repo actively linked on the MyStrom Website and here on NPM is a big banner with MyStrom <3 NodeRed? 😏 Then may someone should deprecate that thing. Should we use the HTTP Input Node then?