v3.0.0.beta empty devices list.

[panjazzon]

I can't get to work new setup with 3.0beta version. Developer mode is enabled. After filling credentials and PIN, system gets Token and gateway URL. Everything seems to look fine but there is no any device on devices list.

Setup:

• Version of node-red: v1.2.7
• Version of node-red-contrib-tahoma: 3.0.0.beta
• Version of node (node -v): v10.23.2
• Version of npm (npm -v): 6.14.10
• Where is node-red installed Raspberry
• How is node-red installed: npm

[nikkow]

Hello,

Thank you for your feedback. As a workaround, can you please try the following procedure:

1. Repeat the procedure described in the ticket
2. Deploy your flow update (by clicking on "Deploy" button on the top-right corner of node-red)
3. Double-click on your Tahoma/Tahoma-Read node
4. The devices list should appear.

[panjazzon]

Hello. Thank you for quick answer. I've tried this before, it didn't help. Now, I created new config, repeat whole procedure, created new flow, added new node, of course Deployed everything and still get no results.

[nikkow]

ok, thanks for confirming this behavior. I'll try to reproduce on my end :)

one more question though: which beta version are you using (beta.5 was released a few minutes ago, but no similar issues was addressed - though it could be easily explained if you would still be on beta.1).

[panjazzon]

My version is beta4. I'll try luck with beta5. update: I tried with beta.5 with no luck.

@nikkow, can I provide any additional info for you to help you to track this problem? Any diagnostic procedures I can make?

[nandibrenna]

I had also noticed this problem. As a workaround, I changed the Tahoma URL in the configuration node settings to the IP address of the gateway.

https://gateway-xxxx-xxxx-xxxx.local:8443 -> https://192.xxx.xxx.xxx:8443

I have node-red running in docker container and name resolution doesn't seem to work properly.

[Programmierfreund]

Thanks @nandibrenna - this workaround works for me fine as well. I'm also running node-red as docker container.

[panjazzon]

Thank you @nandibrenna, I confirm, this workaround works for me too. Unfortunally, custom rotatin function seems to not working. For example sytnax {"action":"customRotation","orientation":50} gives no results.

[wytsep]

I also have it running in a docker container and for me the request to get the token kept going on forever. So I locally changed the code with an early return with dummy data. Then I filled the correct token which I got by doing the requests manually in postman.