Milo Cesar

And I should have tried this before - removing the space from the SSID fixed the problem. Do you know if there is an option to keep the spaces in...

So when removing the spaces from the SSID, linking works properly. When also changing all buffers in this code (also in the link and wizard libraries) to use `ascii` encoding,...

I don't believe there are any improvements to be made at the moment. At most a warning when an SSID contains spaces but I don't know if that is desired.

I wanted to try and see if I could figure out what the problem was here thus I started capturing some data using Wireshark. I captured the link process once...

When extracting the token and secret from the capture that the Tuya App sent and inputting that into [`smartLinkEncode` ](https://github.com/TuyaAPI/link/blob/master/lib/link.js#L154), the output is fully identical to the captured data.

The default is utf8, these packet are identical Since utf8 allowed me to connect (at least to a SSID without spaces) I did not try ascii.

Please post the result of [the steps under "How to check whether the api this library uses can control your device".](https://github.com/milo526/homebridge-tuya-web#how-to-check-whether-the-api-this-library-uses-can-control-your-device) Without this it is hard for me to help...

No problem, Lately I'm also not the quickest to respond 😉 (Next time please paste the raw text instead of an image, makes it significantly easier for developers to work...

Development is currently slower than I'd hope it would be but everything tagged with the [](https://github.com/milo526/homebridge-tuya-web/labels/active) label has my attention 😄

> Smoke, water and gas sensors also Please follow the steps under [How to check whether the API this library uses can control your device](https://github.com/milo526/homebridge-tuya-web#how-to-check-whether-the-api-this-library-uses-can-control-your-device) to see if this is...