Support Mercusys Halo H50G

[3v1n0]

Given that these devices are very close to decos, I tried to login but I'm getting

2023-02-02 00:48:06.143 ERROR (MainThread) [custom_components.tplink_deco] Fetch keys client response error: 401, message='Unauthorized', url=URL('http://192.168.1.25/cgi-bin/luci/;stok=/login?form=keys')
2023-02-02 00:48:06.146 WARNING (MainThread) [custom_components.tplink_deco] Error testing credentials: 401, message='Unauthorized', url=URL('http://192.168.1.25/cgi-bin/luci/;stok=/login?form=keys')

Is this like #130?

Let me know if you want me to to do more inspection with when using the web ui locally.

[amosyuen]

Looks similar, you can confirm by looking for if there is a fetch keys call in network capture when you login

[Juanig]

Given that these devices are very close to decos, I tried to login but I'm getting

2023-02-02 00:48:06.143 ERROR (MainThread) [custom_components.tplink_deco] Fetch keys client response error: 401, message='Unauthorized', url=URL('http://192.168.1.25/cgi-bin/luci/;stok=/login?form=keys')
2023-02-02 00:48:06.146 WARNING (MainThread) [custom_components.tplink_deco] Error testing credentials: 401, message='Unauthorized', url=URL('http://192.168.1.25/cgi-bin/luci/;stok=/login?form=keys')

Is this like #130?

Let me know if you want me to to do more inspection with when using the web ui locally.

did you manage to get it working?

[midadami]

Given that these devices are very close to decos, I tried to login but I'm getting

2023-02-02 00:48:06.143 ERROR (MainThread) [custom_components.tplink_deco] Fetch keys client response error: 401, message='Unauthorized', url=URL('http://192.168.1.25/cgi-bin/luci/;stok=/login?form=keys')
2023-02-02 00:48:06.146 WARNING (MainThread) [custom_components.tplink_deco] Error testing credentials: 401, message='Unauthorized', url=URL('http://192.168.1.25/cgi-bin/luci/;stok=/login?form=keys')

Is this like #130?
Let me know if you want me to to do more inspection with when using the web ui locally.

did you manage to get it working?

Looks like same problem as the other issue. Just not compatible right now.