# Ewelink 2.0.0 Auth Failure

**URL:** <https://discourse.nodered.org/t/ewelink-2-0-0-auth-failure/75039>\
**Category:** General\
**Created:** [11 February 2023 14:48 UTC](https://discourse.nodered.org/t/ewelink-2-0-0-auth-failure/75039 "2023-02-11T14:48:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![StrongTown](https://avatars.discourse-cdn.com/v4/letter/s/4bbf92/32.png) [@StrongTown](https://discourse.nodered.org/u/StrongTown)\
**Post date:** [11 February 2023 14:48 UTC](https://discourse.nodered.org/t/ewelink-2-0-0-auth-failure/75039/1 "2023-02-11T14:48:15Z")

</div>

I use Ewelink to control cottage heating, lighting, water heater etc from my home. I've had this running for a couple years now.

![MB_error](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/1/31c3164174910deeba5906349da2dbcfe1c4fdea.gif)

I use a unique account in NR, devices are shared as required. For quite some time now (\> year) I've put up with a periodic (yet often) problem where I get ' **authentication failure**' . (I use my cell phone or iPad more to control these so I've just defaulted to them when it occurs).

In attempts to fix it, I have sometimes I open the "Edit devices node" and 'pretend' to change things with the credentials (actually just click on it with the mouse), re-deploy and it'll connect and work fine, but again, often it doesn't.

Oddly, when the problem occurs, all Ewelink nodes in the NR editor indicate " **connected**".

Any thoughts on this?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [12 April 2023 14:48 UTC](https://discourse.nodered.org/t/ewelink-2-0-0-auth-failure/75039/2 "2023-04-12T14:48:30Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.