Getting a please Enable Skill when the skill is already enabled

[Vicore]

Everything was working yesterday without issue. But in an attempt to troubleshoot I disabled the skill and made an attempt to re-enable it. It fails to re-enable. I have tried a pixel 6 pro a pixel 7 pro with both Chrome and Edge with the same results. I have again tried both those phone with Verizon, Fi, and my Wi-Fi connection. On a whim I created another account new and tried to connect that and received the same “Login Failed Please try again or contact Monocle support for assistance” while attempting to link the Alexa app. On a whim, I attempted to use an amazon tablet (silk browser) on Wi-Fi to link the account and I get the same error.

I am open to suggestions. I do not have immediate access to an iPhone.

[mjd]

@Vicore I’m having the same issue. I can log into the monoclecam web portal, but I cannot log in through Alexa. Disabled the skill, but now I can re-enable.

[bocci]

Same. Unable to login inside Alexa skill, was working fine the same as the others posted here.

[pathfinder]

I just started encountering the same error. It was shortly after upgrading to protect to 2.11.21 but I think the timing might have been coincidental because the monocle logs have repeats of this line, amongst the [monocle connecting] and [monocle disconnected] lines:

2024-01-29T16:51:32.113Z [ERROR] [Monocle Error] connect ECONNREFUSED 54.160.127.226:443
[ ‘[Monocle Error]’, ‘connect ECONNREFUSED 54.160.127.226:443’ ]

Best guess is aws resource is unavailable/unresponsive.

[ricardobj]

Estou tendo o mesmo problema. Posso entrar no portal da web monoclecam, mas não consigo fazer login através da Alexa.

[Rich]

Same issue here. Alexa told me to log back into the skill, so i logged out, but now cannot log back in “Login Failed Please try again or contact Monocle support for assistance.”. I can login via the website using the same credentials, but for some reason not via the Alexa skill. @Monocle, could this have anything to do with the reCaptcha?

[flynmoose]

Same situation - here. Can log into dashboard and see cameras via web browser. But cannot enable skill. (same as others, I disabled skill to troubleshoot and cannot re-enable.)

[mjd]

@Monocle, would you be able to to provide any help?

[twicklund]

Problem still remains…

Hopefully we can get a resolution soon.

[bouboun59]

same issue here

Monocle you are alwars active ?

[Vicore]

@Vicore I can test or try anything @admin just let me know. If this is a resource issue please let us in the chain that is has been resulted. I am a long time user, and I would had to see Monocle stop working.

[VolkerM]

I have the same issue and cannot reactivate the alexa skill with my login data from the dashboard of the Monocle portal.

But what I noticed is:

The login site of the monocle webpage has the url:
portal.monoclecam.com

But the linking page of the alexa skill has another url:
auth.monoclecam.com

Could this be the reason why we cannot login again? Is this the bug?

Regards,
Volker

[chewmaster2k]

Same problem here, please give some attention to solving this issue.

[vmsman]

Same thing here. I disabled the skill and cannot reenable it. It always says my password is wrong and yet the website where the cameras is defined is working. It appears to me to be an expired authentication token preventing the skill from connecting to Alexa. I’ve messaged Robert and not heard anything. The wife approval factor has plummeted. The workaround in the interim would be to run Tinycam Pro on your Fire TV Sticks. Sadly no workaround for Echo Shows.

[hrisan]

I hope it will get fixed as it was nice working app.

The certificated expired on the 29th and that’s when the monocle skill stopped working. I am not sure what else expired but from the skill URL I can conclude that the login for auth.monocle.com works fine and it is not auth problem as if you paste the url - https://auth.monoclecam.com/login?client_id=monocle-alexa-smart-home-skill&response_type=code&scope=discover+view you can login but it needs two more attributes:
redirect_uri=https%3A%2F%2Falexa.amazon.co.jp%2Fapi%2Fskill%2Flink%2FM1WSNB1R57M76P with the skill ID I guess the skill was registered in Amazon Japan and also the state= token.

One or both are not valid and I guess the skill is not registering.

Alexa skills are very obscure and it is all designed to work with their hosting platform :(

[chzetzl]

Here´s the same problem. Alexa doesn´t show my cams :-(

[johnquilico]

Can’t authenticate the Monocle-cam skill either.
Changed passwords on the Monocle portal. I can log into the portal but can not authenticate the Skill on Apple ios.
Please let me know what I can do to get it working again.

[vmsman]

I am actually surprised that more folks have not replied to this forum. The popularity of Monocle is through the roof. I am thinking that this app may be being retired. Usually when I contact Robert at ShadeBlue I hear back from him in hours and I have heard nothing. It may be that Amazon is not wanting a blanket 3rd party camera app. I’ve been pushing Amazon for H.265, 4k camera support with no luck. Towards this goal I started using a Chromecast 4k Ultra to display my Reolink 4k cameras which I cover in my video

.

[vmsman]

I really meant this video

[Monocle]

@ALL.

Sorry, about the delay in getting this issue resolved. I was away from my office all last week and unable to access the necessary details and resources to work on this problem.

PLEASE TRY AGAIN NOW. (You may need to restart your Monocle Gateway instances.)

The issue started when I replaced all the SSL certificates at the end of January. Even though we have a pre-paid and valid 5 year certificate, the SSL rules require that it gets replaced annually now. So after updating all the certificates and restarting all the services that allow Monocle to function, it all appeared to be working from my local testing. However somewhere in the changes … the Monocle/Alexa authentication service failed to re-connect to the Monocle backend database properly. Perhaps it was holding onto (cached) the previous SSL for its secure connection which then expired. I’ll have to dig a bit deeper to better understand why it continued to fail to connect over the course of several days, but I believe this was the underlying issue causing failed account re-linking, failure to refresh Alexa tokens and failure for Monocle Gateway to reconnect and throw 401 errors.

Please let me know if any of you have further issues getting Monocle working again.

Thanks, Robert