Not able to access port 17000 when connected Ezlo Plus beta device to LAN

[trygve]

I have a Ezlo Plus beta device and would like to play around with the API. The documentation I’ve seen refer to a websocket port at 17000 but when my controller is connected to my LAN with the ethernet there is nothing running on 17000. If I open a access point on the controller and connect to that I can access the websocket on port 17000.

I would like to access the websocket locally without having to set up the access point on the controller. Is this possible or am I doing something wrong?

[cw-kid]

I’d start here.

CW's IDIOT GUIDE - To Ezlo platform HTTP API commands aka Luup Requests

Credits to @reneboer @crille @blacey Also see the “Ezlo Linux firmware - HTTP documentation preview” here PART 1 - Running scenes with authentication turned on OK after a lot of trial and error and help from some of you guys on the forum, I now have basic control of devices and scenes working via HTTPS commands. In Vera as you may know we had the Luup Requests API where we could easily send simple one line HTTP commands to Vera to control devices, run scenes and set device variables etc. Th…

[trygve]

@cw-kid

I’d start here.

Thanks. But I’ve been through that guide but I don’t find it clear about not seeing port 17000. If I do a port scan of the controller on LAN the port 17000 is not available. Is it so, that one need to authenticate first to enable the port or turn of authentication?

I’ve not been able to do the authentication in the guide due to the Python script fetching the token not working (highlighted in another post).

[cw-kid]

Which port scanning software are you using?

I haven’t used a port scanner to see if the 17000 port was open, as it was working for me and I could send commands to the API.

[cw-kid]

I just tried this Windows PowerShell command which seems to indicate the port is open on 17000 but not on 17001