Authenticating in Ubuntu vm failing

[cheme75]

Finally got DWB running in Ubuntu vm, finally got the web ui to prompt for the wyze login, but now keep getting error message - api ID is expecting 36 characters. I’ve checked several times and it is indeed 36. A few are dash - characters, exactly as provided by wyze with no spaces and which works as is in the previous Win DWB, as well as homebridge and scrypted. Although right now no RTSP stream for scrypted.

So is it the dashes that aren't recognized? Got no idea how to fix this. Do I substitute underscores_, spaces , or somehow use escape codes/ characters (if so, how?)

Appreciate any help. If I can get past this, maybe the darn thing will work again.

[beamo11]

I am having the same issue with both the API key and the API id. Unsure what the issue is at this point.

[cheme75]

Further tries with underscores and spaces failed. Tried single quotes, didn't work. Returned to using the dash characters and it finally accepted them as far as attempting to login, but credentials are not accepted. Says something like need to login with your wyze credentials. Checked my wyze login and it's correct, double checked with my homebridge wyze plugin and exactly the same credentials so really frustrated now. No reason I can see for rejecting the login.

It's no longer a need, more like a challenge to learn something new. I can certainly live with the db cam just working in the wyze app. But I would like to learn what may be wrong with this setup. Is it the vm? Is it docker in the vm? Hard to believe no has any suggestions!

[cheme75]

I am having the same issue with both the API key and the API id. Unsure what the issue is at this point.

I had a similar issue with the wyze plugin for homebridge several months ago. I did an update on wyze site for new key and ID which worked. Returned to this bridge to update key and ID and it was all good. Everything was working. But then homebridge HD crashed. So I replaced drive, setup all again, and all worked fine. No new credentials, it worked as normal. Now this wyze glitch - so back to starting over, finally got the vm working and now can't get bridge to login!

[cheme75]

Gave up on VM, most likely lack of resources on a gen 2/i5 win10 laptop. Went back to a somewhat older laptop running lubuntu 22.04 - lacks ram but otherwise runs homebridge ok. Loaded up DWB using idispisable fork - basically appears to just set net mode=host and comments out the port mapping. I just edited my existing yaml and bingo, works like a charm. Only got a v1 db cam but it at least is functional in scrypted again setting it up as a RTSP cam. So far old laptop is handling hb for wyze plugs and bulbs, DWB for the db cam and scrypted for the RTSP cam/hksv feed plus added blink plugin for 2 battery cams. Suspect old laptop make choke on all of it eventually. But I got one more old laptop I can deploy if necessary.

[RyanHope]

When copying/pasting from the wyze website into the setup UI, make sure to copy/paste plain text only. You are pasting hidden characters that the UI is complaining about.