Thanks for clarifying this. This is the exact issue I am having at the moment and I don’t have a hub. I hope this gets fixed.
2 Likes
I opened a ticket already, looking forward someone will take it soon, I’ll keep you guys posted here. It would be cool also you open a ticket as well, to put some more pressure
1 Like
I’ll tag @AlejandroPadilla and @Ivan_Luis_Falleau from the Dev Support team as they may be able to grease the wheels a bit by alerting other teams of the issue.
1 Like
Hi all, let me check with the team about this case 
, I can see the same thing in Android (1.8.09.230) apparently, the next option in Android is trying to add the device as a hub-connected device is why the error 34-000.
I have tested it with eWeLink, TP-Link, and Phillis Hue but I don’t see the same behavior. also, I don’t have devices from those brands so I can’t do a complete test sorry.
1 Like
Hi Alejandro, the issues I am seeing are with both Sengled adding wifi bulbs (ZigBee worked just fine) and Ewelink ( I did a workaround with EWlink by adding another type of device and that option took me to the website and I could link the accounts finally). So far no workaround with Sengled trying to link both accounts have worked, please advise and thanks for your help …
Team, any new news on this matter??? Support is taking to long in provide any feedback at all, thanks
@Silvio_Macias We have created a report on this problem and the team is working on it, unfortunately, we do not have an expected date for the solution.
2 Likes
I have the exact same issue. I’m using the latest version of the Smartthings app on my Android 13 smartphone.
1 Like
Hello everyone, some updates from my side
- The fix will be implemented on the new Android version
- The new Android version was released this week (note that the upgrade may not be reflected until a few days later)
If after the update you still experiencing the issue please let me know
2 Likes