Binding Software controller to Tp-Link Cloud
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I recently migrated from OC200 to the software controller, but i, like @MarkusL having problems with connecting to the cloud, this thread still seemed unsolved, so I figured to revive it.
This is from my server.log
10-27-2024 10:27:44.147 ERROR [https-jsse-nio-443-exec-13] [] c.t.e.c.h.ApiHttpClient(): Device information from deviceMgmt is illegal.
10-27-2024 10:27:44.333 WARN [https-jsse-nio-443-exec-13] [] c.t.e.c.h.ApiHttpClient(): Failed to validate device.
10-27-2024 10:27:44.333 WARN [https-jsse-nio-443-exec-13] [] c.t.s.o.i.a.b.b.a(): Unexpected error when binding owner.
10-27-2024 10:27:44.333 WARN [https-jsse-nio-443-exec-13] [] c.t.s.o.c.p.b.d(): Request: checkDeviceBindStatus, cloud errorCode: -20104, msg: Parameter doesn't exist
10-27-2024 10:27:44.333 WARN [https-jsse-nio-443-exec-13] [] c.t.s.o.c.a.b.a(): Unexpected cloud error: -20104
These 5 lines, comes everytime i try to enable and bind to omada cloud.
I on the latest beta - 5.15.6.4
/Stephen
Here is a screenshot.
This is with the url localhost, i have also tried with it's actual ip with same result.
Here is the error, i am trying to login with my tp-link account, the same account i am using on Omada Cloud Management Platform
/Stephen