Greetings!
I have the same problem as @Andremain. Please can you help me?
Saudações!
Eu tenho o mesmo problema que @Andremain. Por favor, você poderia me ajudar?
Hi, @Gilvandro_Souza!
So, you cannot enroll your Edge-compatible Hub in the SmartThings Beta Channel, correct?
Do you have access to a PC where you can install the SmartThings CLI?
Yes @nayelyz,
I installed the CLI on the PC, but I can’t install the driver through it either.
Even accepting the invitation:
.\smartthings edge:channels:invites:accept 6b68563b-1905-4654-8d2b-e677a2997424
Invitation 6b68563b-1905-4654-8d2b-e677a2997424 accepted.
The same does not appear in the command:
.\smartthings edge:channels:enroll
The error seems to be the same as discussed in the link:
Sim @nayelyz,
Instalei a CLI no PC, mas também não consigo instalar o driver por ela.
Mesmo aceitando o convite:
.\smartthings edge:channels:invites:accept 6b68563b-1905-4654-8d2b-e677a2997424
Convite 6b68563b-1905-4654-8d2b-e677a2997424 aceito.
O mesmo não aparece no comando:
.\smartthings edge:channels:enroll
O erro parece ser o mesmo discutido no link:
I’m seeing this same issue with installing Drivers from another channel. Something hosed with Driver installs in general today?
Can you share that link, please? Just to check if we see the same.
Hi, @Gilvandro_Souza
I am Andres, a member of the Developer Support team.
Can you please confirm if this same error happens for this channel? We are trying to find out if this is a one time thing or a more generic error
Check my browser for the following error messages when trying to access the channel:
Hope it helps with the analysis.
Hi, @Gilvandro_Souza
Yes it does help, thanks for sharing those captures. I already reported the issue to the Engineering team. We will keep you updated.
Great!
Here is more information about my attempts to access the channel:
2022-09-08T23:38:05.330Z Error: Request failed with status code 403: {“requestId”:“1B4AD807-02E8-4F5B-BC9D-BCDF9ABE9957”,“error”:{“message”:“unsuccessful-http-call status=403”,“details”:}}
2022-09-08T23:38:05.330Z at createError (C:/snapshot/smartthings-cli/node_modules/axios/lib/core/createError.js:16:15)
2022-09-08T23:38:05.330Z at settle (C:/snapshot/smartthings-cli/node_modules/axios/lib/core/settle.js:17:12)
2022-09-08T23:38:05.330Z at IncomingMessage.handleStreamEnd (C:/snapshot/smartthings-cli/node_modules/axios/lib/adapters/http.js:269:11)
2022-09-08T23:38:05.330Z at IncomingMessage.emit (node:events:539:35)
2022-09-08T23:38:05.330Z at IncomingMessage.emit (node:domain:475:12)
I cant enroll either, any updates on this? thanks
Wow, I certainly hope there is a better solution than this haha… thanks for your reply and solution!
I cannot enroll in the channel name “light790” that was provided by Third Reality for the Multifunction Night Light. Here is the channel link: Samsung account
When clicking on the “Enroll” button it just spins (circle of death) until it times out. I tried to enroll repeatedly with no success. Here is the device information from installing the driver Zigbee Light Multifunction Test:
The “Zigbee Switch” from the SmartThings Beta channel provides some functionality for the RGBW light but does not provide access to the illuminance and motion detection settings.
I am looking for suggestions on how to enroll in the channel. Perhaps there is an existing driver out there for a Multi Sensor light that has motion and illuminance sensing capabilities that I could install. Perhaps the devices fingerprints could be added to an existing driver?
Thank you in advance for any and all assistance.
Note: Here is the article I published on the Third Reality Night Light. I was successful in installing the driver channel and the “Zigbee Switch” driver when I first installed the device. I then deleted the driver channel for testing purposes and I now cannot enroll in the driver channel.
The invitation link seems to be suggesting it is a temporary channel that gets created automatically when a Pull Request is created yet he PR seems to suggest the channel has since been deleted. Not sure what is going on there but I guess things don’t get tidied up as much as they should be.
Is there any specific direction I must provide to Third Reality about steps that need to be taken to fix the issue?
It looks to me like they submitted a PR that modifies the Zigbee Switch driver to support a WWST certification request for the Night Light. That results in a temporary channel being created to provide access to the modified driver. For some reason that only Third Reality and ST are party too the PR has been closed and that deletes the channel, though it rather seems it doesn’t completely clean up after itself as I could still access the invitation URL and you could still access the subscription URL.
I would have thought that if they want to provide access to a driver independently they should be publishing it to their own channel and creating an invitation for it, just like any other community provided driver.
Thanks for the detailed explanation Graham . I will pass this information to the Third Reality support team.
I reached out to ThirdReality, and they responded with this updated link for their edge drivers: https://bestow-regional.api.smartthings.com/invite/adMKr50EXzj9 .
I used the “Zigbee Switch” driver from that Third Reality channel and it worked fine with their Multifunction Night Light, providing control for the night light color, motion sensor status, and luminance light lux sensor status.
1 Like
Thank you ankitprasad! Yes, I used the link that you specified and I was able to download the “Zigbee Switch” driver and it is working splendidly! Thanks again for this solution!