Login Error . Appid is not unauthorized
Closed this issue · 94 comments
Since this morning the Ewelink plugin is not connecting. The cloud is online and the credentials are correct.
Yesterday everything was working, and no changes were made to the configs.
here is a screenshot of the logs,
Looks like Ewelink is no longer authorising the app key HB is using.
Hi @lmartu
Yes not long woken up to this 🤯
Same thing for home assistant sonoff plugin
AlexxIT/SonoffLAN#887
Will look into this as soon as I can
Please try beta version 9.0.2-beta.4
Please try beta version 9.0.2-beta.4
beta version 9.0.2-beta.4 is working.
Amazing... such a quick support. Love it!
THANK YOU SO MUCH
Bitte versuchen Sie die Beta-Version 9.0.2-beta.4
Thanks beta works
Thanks, unfortuntely, I had uninstalled and reinstalled the plugin and …. Lost all my homekit automations… I’m going to have to re code them all…
Danke, leider hatte ich das Plugin deinstalliert und neu installiert und …. Ich habe alle meine Homekit-Automatisierungen verloren ... Ich muss sie alle neu codieren ...
Have you no Backups?
Nope… don’t think you can backup apple automations
Danke, leider hatte ich das Plugin deinstalliert und neu installiert und …. Ich habe alle meine Homekit-Automatisierungen verloren ... Ich muss sie alle neu codieren ...
Have you no Backups?
If you set up the plugins as a subbridge, the devices are not immediately gone in the Homekit app. Then simply restore a backup from the Homebridge. By the way, Homebridge automatically makes a backup every night
Danke, leider hatte ich das Plugin deinstalliert und neu installiert und …. Ich habe alle meine Homekit-Automatisierungen verloren ... Ich muss sie alle neu codieren ...
Have you no Backups?
If you set up the plugins as a subbridge, the devices are not immediately gone in the Homekit app. Then simply restore a backup from the Homebridge. By the way, Homebridge automatically makes a backup every night
I wish I had known… a bit late now… I’ll keep it in mind for the future
I thought i was the only one, lucky i look for the issue here
The issue is that eWeLink seem to have revoked the app id and app secret the plug-in uses to connect to their servers.
The fix has been to use a different app id and secret that I happened to find.
Lets hope they don’t revoke the new one!
I’m sure this is going to happen again in the future, they must be seeing thousands of devices connecting with the same ID, and rightly be suspicious. how did you “happen” to find a new key and secret may I ask? :) any way of generating a per user ID in the future?
The beta works for me too. Thanks for a quick fix.
Hi.
Installed the beta, issue is resolved but one device the "KingArt KING-M4 dimmer switch is not discovered.
Thanks for the assistance so far
I have the same problem with the KingArt KING-M4 dimmer switch
Hopefully Ben can resolve it.
This time it is something totally out of my control.
The old APPID and APPSECRET seemed to work for all device types like some master key.
The new APPID and SECRET only seems to work for some device types. This is something I cannot control.
The only thing I can do is get in contact with ewelink to see if they’d be willing to continue to help projects like this exist fully. I will do this 👍🏻
@coolkit-tony anything we can do here?
I think I will try installing HAA firmware.. though that will only work for esp devices… window sensors are not flashable AFAIK
This time it is something totally out of my control. The old APPID and APPSECRET seemed to work for all device types like some master key.
The new APPID and SECRET only seems to work for some device types. This is something I cannot control.
The only thing I can do is get in contact with ewelink to see if they’d be willing to continue to help projects like this exist fully. I will do this 👍🏻
Good Idea…. I hope they do…. but I doubt they will…. Fingers crossed
Thanks for great effort on this project, i 've upgraded to version v9.0.2-beta.4, the login is sucessful, but seems cannot discover my cloud device at all.
Thanks for great effort on this project, i 've upgraded to version v9.0.2-beta.4, the login is sucessful, but seems cannot discover my cloud device at all.
which device model?
Thanks for great effort on this project, i 've upgraded to version v9.0.2-beta.4, the login is sucessful, but seems cannot discover my cloud device at all.
which device model?
i am not sure the model , but it is a 4g-lte (it connect to internet via the 4g network) switch for controller my garage gate.
But i am been using with your homebridge plugin solid stable so far. (over 1 year)
the product page:
https://ewelink.eachen.cc/product/eachen-4g-lte-switch-dry-contact-relay-1ch-ewelink-app/
It can connect and login , but cannot fetich the device at all .
[7/7/2022, 1:22:40 AM] [eWeLink] Fetching devices from eWeLink home/id [My Home] [60edXXXXXXXXXXb3].
[7/7/2022, 1:22:40 AM] [eWeLink] Web socket host received [as-pconnect2.coolkit.cc].
[7/7/2022, 1:22:41 AM] [eWeLink] Sending WS login request.
[7/7/2022, 1:22:41 AM] [eWeLink] LAN discovery starting.
[7/7/2022, 1:22:41 AM] [eWeLink] WS login successful.
[7/7/2022, 1:22:44 AM] [eWeLink] LAN discovery complete.
[7/7/2022, 1:22:44 AM] [eWeLink] LAN monitoring started.
[7/7/2022, 1:22:46 AM] [eWeLink] ✓ Setup complete. Interested in sponsoring this plugin? https://github.com/sponsors/bwp91
It can connect and login , but cannot fetich the device at all .
[7/7/2022, 1:22:40 AM] [eWeLink] Fetching devices from eWeLink home/id [My Home] [60edXXXXXXXXXXb3]. [7/7/2022, 1:22:40 AM] [eWeLink] Web socket host received [as-pconnect2.coolkit.cc]. [7/7/2022, 1:22:41 AM] [eWeLink] Sending WS login request. [7/7/2022, 1:22:41 AM] [eWeLink] LAN discovery starting. [7/7/2022, 1:22:41 AM] [eWeLink] WS login successful. [7/7/2022, 1:22:44 AM] [eWeLink] LAN discovery complete. [7/7/2022, 1:22:44 AM] [eWeLink] LAN monitoring started. [7/7/2022, 1:22:46 AM] [eWeLink] ✓ Setup complete. Interested in sponsoring this plugin? https://github.com/sponsors/bwp91
This is most likely due to this comment above:
#385 (comment)
It can connect and login , but cannot fetich the device at all .
[7/7/2022, 1:22:40 AM] [eWeLink] Fetching devices from eWeLink home/id [My Home] [60edXXXXXXXXXXb3]. [7/7/2022, 1:22:40 AM] [eWeLink] Web socket host received [as-pconnect2.coolkit.cc]. [7/7/2022, 1:22:41 AM] [eWeLink] Sending WS login request. [7/7/2022, 1:22:41 AM] [eWeLink] LAN discovery starting. [7/7/2022, 1:22:41 AM] [eWeLink] WS login successful. [7/7/2022, 1:22:44 AM] [eWeLink] LAN discovery complete. [7/7/2022, 1:22:44 AM] [eWeLink] LAN monitoring started. [7/7/2022, 1:22:46 AM] [eWeLink] ✓ Setup complete. Interested in sponsoring this plugin? https://github.com/sponsors/bwp91This is most likely due to this comment above: #385 (comment)
Thanks, thanks anyway, Hope can solve this issue soon.
The Burnett BN-SZ01 Ceiling Light is also not being discovered since the issue. Curently running the 9.0.2-beta4.
It pains me to hear that devices have stopped working 🙁
This ewelink plugin is my pride and joy and i’ve tried to make it work so well, so for something out of my control to diminish the functionality is really irritating me
Thanks Ben. The beta version is now working for me. If anything we can do like signing a petition or something, let us know.
Tried the beta. TH16R2 (switch with temp probe) Still won’t work. On the other hand, my iFan04 worked through it all. Odd. If there’s any debugging I can do from my end to shed light on this, let me know.
Tried the beta. TH16R2 (switch with temp probe) Still won’t work. On the other hand, my iFan04 worked through it all. Odd. If there’s any debugging I can do from my end to shed light on this, let me know.
Never mind. Restarted HomeBridge and it’s all working now. I think I might have forgotten to restart after installing the beta version. Thanks for the effort! Cool plug-in.
It pains me to hear that devices have stopped working 🙁
This ewelink plugin is my pride and joy and i’ve tried to make it work so well, so for something out of my control to diminish the functionality is really irritating me
Thank you a lot bwp91
i am the same side my inching devices dosent add to my devices dosent detected , erase the plug in reinstall , restart all do it
I have 4 of them EACHEN 1-GANG DIY 5V SELF-LOCKING/INCHING SWITCH ST-UDC1 (EWelink APP)
thank you for your help !!
The others works son off , mini son off and the 4 channels son off work ,only the eachen 1 gang dosent work
Does anybody know if ITA-GZ1-GL still works?
Is a Sonoff device.
4 Channel DM-585 not working here, can't see any mention of it in logs either.
Is there another 5v input multi channel switch that works?
4 Channel DM-585 not working here, can't see any mention of it in logs either.
Is there another 5v input multi channel switch that works?
can you try new beta 9.1.1-beta.0?
Hmm doesn't seem to change. But can see an error now:
[7/7/2022, 7:47:56 AM] [eWeLink] An error occurred during http getHomes().
[7/7/2022, 7:47:56 AM] [eWeLink] ***** Disabling plugin. *****
[7/7/2022, 7:47:56 AM] [eWeLink] ***** {
"error": 407,
"msg": "the path of request is not allowed with appid:4s1FXKC9FaGfoqXhmXSJneb3qcm1gOak",
"data": {}
} "error": 407,. *****
Bizarrely, updating to previous version also reset about 36 lights associated with the hue plugin. Maybe I should run homebridge in bridged mode to avoid plugins interfering with each other, not seen that before.
Sonff mini is working.
All working expect for the EACHEN 1-GANG DIY 5V SELF-LOCKING/INCHING SWITCH ST-UDC1 (EWelink APP)
it dosent recognize , and with new beta 9.1.1 An error occurred during http getHomes().
[7/7/2022, 2:47:56 AM] [eWeLink] ***** Disabling plugin. *****
Hi, thanks for fixing this. I did have only one of my R3s not connecting after the update. I rejoined it to the wifi (since I set this up I created a seprate SSID which is only on 2.5g) and now its discoverable. All the R3s are on the latest firmware. So its odd to say the least.
my switch is not working
Thank you for work! I hope this helps.
ewelink v9.1.0
Working:
- POWR2 -> [Manufacturer: Sonoff, FW Name: PSC-B67-GL]
- TH16R2 -> [Manufacturer: Sonoff, FW Name: PSA-BHA-GL]
- BASICR2 ->[Manufacturer: Sonoff, FW Name: PSF-B01-GL]
Not Working (Not added):
- ZJSB9-80 J (Manufacturer: WDYK, FW Name: PSF-B67-GL)
ewelink v9.1.1-beta.0
Nothing works and shows the following error.
Newest beta should work with all device types again.
The drawback is, it will log you out the ewelink app.
My suggestion (not ideal) is to create another ewelink account and share your devices to this account.
Most importantly, use your MAIN ewelink account for this plugin and your shared account with the ewelink app
@bwp91 I just tested v 9.1.1-beta.1 and the devices that previously dissappeared were added to Homebridge again. Seems like the problem is resolved. Thanks!
Same problem - KingArt04 stopped working - I use Hoobs 4.2 and can install only 9.0.1.
Can not install 9.0.2 beta 4 or 9.1. Those are not on the list for installation.
Any solution ? Maybe by shell ?
Die neueste Beta sollte wieder mit allen Gerätetypen funktionieren.
Der Nachteil ist, dass Sie dadurch von der ewelink-App abgemeldet werden.
Mein Vorschlag (nicht ideal) ist, ein weiteres ewelink-Konto zu erstellen und Ihre Geräte für dieses Konto freizugeben.
Am wichtigsten ist, dass Sie Ihr HAUPT-ewelink-Konto für dieses Plugin und Ihr gemeinsames Konto mit der ewelink-App verwenden
So I am not logged out in the app with the beta, I had problems before and could only log in the plugin or in the app, otherwise there were problems. With the beta everything is back to normal.
My switch still doesn't work. I have been using the G1 switch as my account for over 2 years. When I see other people getting fixed, I feel very bad. The G1 switch is compatible with the ewelink app and I've been using it for over 2 years and it doesn't work now. Will G1 switches not be supported in the future?
Both the lastest version and the beta version do not work.
Trying with a shared account doesn't work. I am very sad Can you help?
Same problem - KingArt04 stopped working - I use Hoobs 4.2 and can install only 9.0.1.
Can not install 9.0.2 beta 4 or 9.1. Those are not on the list for installation.
Any solution ? Maybe by shell ?
For hoobs please see
https://github.com/bwp91/homebridge-ewelink/wiki/Beta-Version#hoobs-4
- The version number will not be correct but this will still download the latest beta version
Trying with a shared account doesn't work. I am very sad Can you help?
Did you use your main ewelink account in the plugin?
Trying with a shared account doesn't work. I am very sad Can you help?
Did you use your main ewelink account in the plugin?
Tried with main account but it doesn't work
Tried with a shared account but it doesn't work
Trying with a shared account doesn't work. I am very sad Can you help?
Did you use your main ewelink account in the plugin?
Tried with main account but it doesn't work Tried with a shared account but it doesn't work
Using the latest beta version and your main ewelink account, can you show me all logs of the plugin initialising?
Can confirm DM-585 working now on v9.1.1-beta.1 👍
Bwp91 thank you a lot for your work
The beta works all the people need to delate the plug-in restart Homebridge , and later install the beta put your account all work single switch really g1 all mini th all of them thank you a lot you can close now!!
People erase the plug in , restart Homebridge , add the beta directly put your account and restart !! Go ahead !! Thank a lot Bwp91
Trying with a shared account doesn't work. I am very sad Can you help?
Did you use your main ewelink account in the plugin?
Tried with main account but it doesn't work Tried with a shared account but it doesn't work
Using the latest beta version and your main ewelink account, can you show me all logs of the plugin initialising?
hey this is working now!!!!!
after delete plugin and reinsatall plugin is worki g very well thanks
How long before v9.1.1-beta.1 will be available in HOOBS please?
How long before v9.1.1-beta.1 will be available in HOOBS please?
will be available already using the usual process as described for hoobs in the wiki.
ignore the version that shows in hoobs, it will install the latest beta
plugin should not need to be deleted, just update and restart
How long before v9.1.1-beta.1 will be available in HOOBS please?
will be available already using the usual process as described for hoobs in the wiki.
ignore the version that shows in hoobs, it will install the latest beta
Great thanks, that has fixed it!
Out of interest, has anyone tried using the same ewelink account for plugin and ewelink app?
At least for me (on newest beta) when i start the plugin it logs me out of ewelink app. and if i then log into ewelink app it shows errors in homebridge log
Out of interest, has anyone tried using the same ewelink account for plugin and ewelink app?
At least for me (on newest beta) when i start the plugin it logs me out of ewelink app. and if i then log into ewelink app it shows errors in homebridge log
It logged me out of the app too.
good to know it’s not just me!
The plugin is designed so that when you control a device it waits for a successful (or not) response from ewelink.
If the plugin is trying to control a shared device it doesn’t get this “response”. Only the main account gets the notification.
This is why the plugin does not work well with shared devices and why I suggest that the main account is used with the plugin and the shared account is used with the ewelink app.
Before I make a release I would just like someone else to confirm that 9.1.1-beta.2 is still working?
Before I make a release I would just like someone else to confirm that 9.1.1-beta.2 is still working?
Installed briefly tested and Working!
👍
Before I make a release I would just like someone else to confirm that 9.1.1-beta.2 is still working?
Working here too but I’m getting an error when I try to open the settings page of the plugin
Before I make a release I would just like someone else to confirm that 9.1.1-beta.2 is still working?
Working here too but I’m getting an error when I try to open the settings page of the plugin
😯
Me too.
oops newest beta?
oops newest beta?
Yes. Might have been an issue in previous beta too. Not sure if I’ve tested that yesterday
oops newest beta?
homebridge-ewelink v9.1.1-beta.3
And reboot.
Devices good ✔️
Settings available ✔️
@bwp91 The situation for me is similar. If Homebridge log in to the Ewelink account, it log out of the Ewelink application. If he log in into the Ewelink application again, an error appears in the logs in Homebridge. Despite this error, I can still control all my devices in the Home Application, despite the fact that I am logged in to the Ewelink application. Check Ben to see if you have the same. Maybe this will help you. Thanks for the plug.
The plugin version I am using is 10.0.0
Problem solved by new plugin version. Hoobs showing 9.0.1 on plugin page but log show:
eWeLinkundefined v10.0.0 | System linux | Node v16.14.0 | HB v1.4.0 | HAPNodeJS v0.10.0...
version 10.0.0 so far working well.
Thank you! Good Job!
hoobs sometimes a bit behind with version numbers but glad it’s working for you 👍🏻
plugin seemed to work so well before i’m not happy about the new “criteria”
for those still using version homebridge-ewelink@8.15: patch
did you try v10 of the plugin?
for those still using version homebridge-ewelink@8.15: patch
did you try v10 of the plugin?
Yes I did. Sadly, I have certain environment that cannot run over node version 12.
Therefore, have to use 8.xx of your plugin.
Maybe I have better fork yours and keep up major commits🤔
How long before v10 will be available in HOOBS please? I don't want to reconfigure my home setup.
i'm using v9.0.2-beta.4 and all my devices are working just fine. Moreover, it doesn't log me out from either the plugin or the app when I log in the other. Do I still need to update to v10?
How long before v10 will be available in HOOBS please? I don't want to reconfigure my home setup.
HOOBS users can follow the instructions for installing the beta but in the version list just click the icon for “latest” instead of “beta”.
Even though the version number is wrong, this will still install v10 of the plugin
Oui mais cela ne sera pas une mise à jour, mais une réinstallation du plugin et donc supprimer toute la configuration ainsi que les automatisations créé sur HomeKit.
Yes, but this will not be an update, but a reinstallation of the plugin and thus remove all the configuration as well as the automations created on HomeKit.
did this happen when you installed the beta?
Je ne sais pas car je n'ai pas installer la version beta. Je suis en panne depuis et j'attend que HOOBS veuille bien lancer la mise a jour V10.
I don't know because I didn't install the beta version. I have been down since and I am waiting for HOOBS to launch the V10 update.
I see.
Using the instructions like the beta will not reset all your homekit data, it’s the same as updating the plugin
HOOBS propose la mise a jour du plugin EweLink afin ainsi que d'autre plugin !
HOOBS is proposing the update of the EweLink plugin and other plugin!
Nice Job, as always, despite our friends EWELink making it tricky!
Hi
I have the same problem
Too bad I didn't find this thread first
So I have reinstalled homebridge-ewelink v10.0.0
Everything about Sonoff works fine
But I have another product 丙申 Electric curtains
Systems that also use ewelink
When my mobile phone is logged into the ewelink system, these electric curtains of Homebridge will be logged out and cannot be used.
When I restart Homebridge, the ewelink account on the phone will be logged out.
thank you for your effort
When my mobile phone is logged into the ewelink system, these electric curtains of Homebridge will be logged out and cannot be used.
When I restart Homebridge, the ewelink account on the phone will be logged out.
Please see the release notes for v10 for a workaround for this!
This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
So I have a question. I have this self inching relay: https://a.co/d/fT51OJN
It has LAN control enabled. Can I not just connect to it directly instead of having to go through the ewlink cloud? Is that possible? Or am I also affected by this API change up?
Hi,
Closing this just as been a little overwhelmed with issues recently.
If this is still an issue or a feature you would like implemented then please do re-open this ticket!
Thanks for your understanding!