eWeLink API in action with NodeRED

[@chrisg2003]

I have successfully used Sonoff mini using V3.5.0 firmware and control it directly from Node Red in DIY mode. The v2 protocol on v3.5.0 is completely different to previous versions and much easier, you only need eWeLink for the firmware upgrade.

[@notenoughtech]

Darn this switch I used got only 3.4 update

[@soovui]

Great work APi NEW ideas... It is good that we use API to control the devices without flashing it for people who seek for convenient bcoz not many people very handy could have tools and knowledge on soldering stuffs. If eWelink API really good, it really helps a lot and save a lot of time to work with node red. I like the idea working with both mobile and node red, especially if eWeLink able to solve the LAN issues to work as private device.

[@notenoughtech]

I would like to see the consumer grade API like Shelly cloud does it - that would be awesome

[@soovui]

@@notenoughtech exactly

[@rwkemp]

Nice idea. Customers dont like so much change the original firmware because have problems with warranty. Best regards from Brazil

[@notenoughtech]

I will keep bothering them for a consumer grade API - as this would make the eWeLink devices so much better

[@DIYtechie]

Tried this a while ago, but did not support lan mode. This is a dealbreaker for me. The Home Assistant integration now works with LAN mode so you have the speed and privacy without having to flash new firmware to your devices. Only requires one login - after that it works without internet 👌🏻

[@notenoughtech]

It's a bummer about the LAN only mode but eWelink replied that they passed my request for proper REST API so 🤷🏼‍♂️

[@jasong1376]

Be great if you would reduce the screen resolution or zoom in when showing stuff on screen. Is too small to see/read otherwise. Thanks for content.

[@notenoughtech]

In the linked article you will find the exact payloads i mentioned

[@EsotericArctos]

I was watching this on a bigger screen and found the resolution fine. I rewatched it on a mobile phone and on the small screen it was hard to read. Compromise I guess :).

[@notenoughtech]

it's a hard compromise. ... Id love to a better solution for screen recording otherwise it's a lot of post processing, that's why i usually stick additional info in the article as then you can have it open side by side and take it on your own pace - and not have to deal with my accent hahahah

[@jaumevadell5924]

Thank you for your wonderful videos. Since last month the node-red connection with welink has stopped working, giving an authentication error. Have you experienced this problem? do you have a solution for it? thank you

[@notenoughtech]

I'd have to check. It's been a while since I had it in use. Ping me a reply later on this evening so I remember:)

[@jaumevadell5924]

Thank you very much for your interest in my problem.

[@guillaumedeondutoit384]

Hi Mat. How can i use my Aqara P1 motion sensors with eWelink? It seem according to your videos and chanel, you know everything. Show me what to do please.

[@notenoughtech]

If you going zigbee way I urge you to use custom coordinator like sonoff zigbee dongle. Check out my video on that

[@ahcenebelkessa5898]

hello I love your video, I have a question I buyed a EWeLink - caméra (with RTSP protocole ) and I want to connect it to MQTT borker is it possible ?

[@notenoughtech]

As in, you want to use MQTT to control the camera movement? You can't stream over MQTT to my knowledge it's not a protocol that is designed to handle the video stream

[@soovui]

Hi Mat, are you able to teach or share flows sample on how to login and trigger toggle or status or power usage api using purely nodered function node instead of using the node given by node-red-contrib-ewelink?

[@notenoughtech]

I'd have to save some time to do it in other way than shown in the video. Time is the most problematic aspect

[@soovui]

@@notenoughtech 😂 fully understood. Ok I will wait for a smart guy like u to excite everyone.

[@DorsetSaferRoads]

Having an issue. I have sonoff TH origin. It's all working, I can control from Google home and have a flow in node red all working controlling and reading temperatures however I only seem to get an update on the temperature in node red if I open the ewelink app on my phone. All very strange. Any suggestions?

[@notenoughtech]

That's strange, - I remember for some time the API was troubled by the limit of active sessions but I thought this was resolved. have you tried to re-add the device to the eWeLink cloud?

[@DorsetSaferRoads]

@@notenoughtech yes, weird thing, is that it works, but only get a new temperature in node red if i open the app.

[@notenoughtech]

Can you manually get the list of devices in Nodered each time?

[@DorsetSaferRoads]

@@notenoughtech yep and I'm getting regular state of the relay updates just not temperature

[@DorsetSaferRoads]

@@notenoughtech interestingly I decided to go the Samsung smart things route and that seems to be suffering the same issue.

[@ronm6585]

Thanks. Currently use tasmota on what I can.

[@bogorad]

Ha! I spent the better part of yesterday struggling with Sonoff's firmware version 3.5, protocol 2.0. In a nutshell, you can flash any v3.5 device without any wires or soldering!

[@notenoughtech]

I know about DIY mode flash do you know something I don't? :)

[@bogorad]

@@notenoughtech if sonoff firmware v3.5 and protocol 2.0 don't ring a bell, Google it right now and enjoy.

[@notenoughtech]

SonOTA didnt work for my device - this is how I came across the API

[@bogorad]

@@notenoughtech forget sonota! github.com/itead/Sonoff_Devices_DIY_Tools/blob/master/SONOFF%20DIY%20MODE%20Protocol%20Doc%20v2.0%20Doc.pdf

[@notenoughtech]

That;s the DIY mode I talked about some time ago. Since the DIY needs the hardware switch - won't work or anything that was compatible up until Sonoff R3 which is a bummer

[@Lazniak]

Thank you for your video :)

[@notenoughtech]

Pleasure is mine

[@soovui]

Hi Mat, sorry to disturb you. Like to check with you, do you manage to get the ewelink power usage because I failed to fetch and dont know what happen and here is the error debug msg shown "No power usage data found". Do you have any idea?

[@notenoughtech]

I will check this afternoon.

[@notenoughtech]

Sorry Stu, I haven't got around to this yet. Time goes through my fingers like sand.

[@ph-jq1jb]

I have the node red ewelink nodes working (intermittently with some problems) with my Ewelink sonoff devices. One of my devices that gives a big problem is a Sonoff ZigBee hub with sub device temperature sensors. How can I extract the temperature information for use in node red? The device id of the sensors (according to Ewelink App) does not appear to work when used in nodered red Ewelink nodes. I should add that the Devices node finds all attached devices, ( inc the sub- devices) and I can read the information giving the detail of the sensor inc temperature. second question - is it possible to delete the Ewelink credentials stored in Nodered - every time I I reconfigure a node I seem to have to enter the logon details and end up with multiple credentials?

[@notenoughtech]

I will try to check this over the weekend. sorry I had been swamped with things recently

[@ph-jq1jb]

@@notenoughtech Thankyou - whilst I can control and monitor simple switches fairly reliably I have no success in using the EventListener node - either leaving id blank or using a working id.

[@ph-jq1jb]

I have now succeeded in getting Temp and humidity readings from Sub Devices Sensors (aka child Devices) by using the Devices node and then using Change and Switch Nodes to filter the returned message. Messy but a temp solution. It would be good to know if anybody else has succeeded with the EventListener Node.

[@user-od3rl5mc]

Will this work for taking temp readings on TH16 for example?

[@notenoughtech]

I don't have th16 but the nodes are there so I'm pretty confident it will

[@muhammadfarhan5823]

Does this mean it’s going thru local mode?

[@notenoughtech]

It uses eWeLink cloud so you need to be online. No LAN this way

[@demokedes1]

Dear NoetEnoughTech, I am already using ewelink with NodeRed, but I am missing one thing. maybe you know the answer. i am missing the information who forced particular action. Let me give you some background: I have several devices, that I share with other users. In the app, I can see in the history for the recent event who triggered them, but in the nodered debug windows I don't see that information, I see only, whether it is triggered through the device od the 'app'. Any idea how to get information which user triggered it?

[@notenoughtech]

I would have to experiment with the shared account but if the information isn't available in the payload, then unfortunately not much we could do about it. Use event listener perhaps it will give you different info for each user?

[@unlock-er]

Definitely flashed everything I have. Just like Travis from digiblur said, and I quote "Take your S1%t out of the cloud"

[@notenoughtech]

If I was taking this advice verbatim... There would be no not enough tech

[@unlock-er]

@@notenoughtech well you did ask for it by asking the question..

[@notenoughtech]

touche :)

[@TheBettyswetty]

Hello, what if i have a SONOFF 4ch? I repeated the sequence 4 times replacing the chanel (1, 2, 3, 4). Every time i deploy it, some channels work, some don’t. Every time is different but they never work all of them simultaneously..

[@notenoughtech]

Do you have interlocking enabled by any chance?

[@TheBettyswetty]

I don’t think so... i don’t even know how to activate it. But from the eWelink i can turn on/off the chanells independently, also works the same with the remote. And sometimes from node-red i can control even two or three (with luck) channels.

[@notenoughtech]

ewelink controls work fine? Is it just the remote that gives you issues or more?

[@TheBettyswetty]

@@notenoughtech the ewelink app works just fine. The remote also, works fine. I am having issues just with the node red because i can t controll all the 4 channels. When i hit the “deploy” button sometimes is working the channel 1, sometimes channel2, 3 or 4. Even 2 chanells works. Every time it s different.

[@TheBettyswetty]

When i inject “on/off”, in the debug section for those chanells that doesn’t work i am receiving the error: 406 “authentication failed”. But it s weird because if i deploy it again, a channel that didn t work, maybe it s working...

[@krzysztofhandzlik9273]

It seems like this Node Red module is not working any more... Look at project github

[@notenoughtech]

i will take a look. since api is available I would assume the library needs to be updated that's all

[@amita1974]

Interesting. I do not wish to flush Tasmota or any other FW from the following reasons: 1. On the Sonoff POW R2 device, I understand that overwriting the official FW it will cause to lose all the calibration parameters that comes with it. Does any one have an idea on how to keep them before flushing the POW R2, in order to be able to get back to official FW if I will ever want to do that? 2. Flushing Tasmota will cause me to lose access to the use of google home assistant control. Bypassing this would require use a free service that is limitted with the number of the connected devices. 3. From my expirience, using Tasmota and Domoticz as hub does not work well when the WiFi connection is not stable and it is not so clear on how to set the system (Tasmota / Domoticz) to work with: 1. persistent messages 2. QOS 1 or 2 3. Set "Will of death" message to be transmitted when the broker understand that the connection was lost, and use it, after it will be set. Does anyone have information to share regarding the aspects that I mentioned above?

[@notenoughtech]

ad 1. Tested against known meters shown good accuracy on my flashed Sonoff . Flashing guide by me has backup option - just remember backups are linked to individual units, so mark sonoff and backup files ad 2 - take a look at NORA ad 3 consider MQTT with delivery protocols, unlike HTTP MQTT assures delivery . If wifi is spotty, both services will struggle but MQTT will deliver the message These are set in MQTT broker (mosquitto ie) and you can pick the options in the config. Links: notenoughtech.com/home-automation/flashing-tasmota-on-sonoff-pow-2/ notenoughtech.com/featured/sonoff-tasmota/ notenoughtech.com/home-automation/nora-google-assistant-in-nodered/

[@EsotericArctos]

A person named 'Alexxit" (github.com/AlexxIT/SonoffLAN (make sure it has two x's)) on GitHub made a Home Assistant add-on that allows you to add the ewelink devices to HA for local control. They add to the app the first time you add a device, but after the first connection they don't talk to the server. I believe it's available in HACS as well. DrZzs did a video on it. If you do a google search for "SonOff HACS ewelink " it seems to find it. The add-on uses the API to grab the data to control the device locally without flashing.

[@notenoughtech]

I came across this but I was looking for something for NodeRED - I believe he was monitoring the eWeLink device with wireshark for contact - so it was still connected to the outside network. I locked the WAN simulating internet failure - and it woldn't work.

[@EsotericArctos]

@@notenoughtech Apparently each ewelink device has a local "device id" that can be used for local control even if the internet is disconnected. I haven't played with it a lot myself, but I wonder if this is worth exploring more.

[@notenoughtech]

I will see if I can put it on a subnet we I was blocking packets going out

[@EsotericArctos]

@@notenoughtech It would definitely be interesting to see if default firmware really can have total local control. It would make those new non-sonoff devices more interesting.

[@notenoughtech]

I will email eWelink see what they are up to :)

[@thatnoone]

so we can use this on Tasker?

[@notenoughtech]

You would have to figure out the individual API calls but in theory yes

[@thatnoone]

@@notenoughtech cool thanks

[@luciangpl]

Hi, is this still working? I'm trying now and I have this error " "RequestError: Error: certificate has expired""

[@notenoughtech]

It should be. Error says you need to authenticate again - you can be onlu log in on one device

[@luciangpl]

@@notenoughtech I don't know what you mean, can you please explain?

[@notenoughtech]

Go to config node and enter your credentials again to log in. If you log in later on in the android app, it will log you out from NodeRED

[@luciangpl]

@@notenoughtech Thanks for your answer, I did that, still not working. I also made a new account and share some Sonoff devices to that account and still the same. This account is not used on any android phone

[@thatnoone]

how about zigbee?

[@notenoughtech]

Any ewelink devices can be controlled. You will end a ZigBee bridge of course

[@faisalachmad8958]

Node red not working with sonoff anymore

[@notenoughtech]

So I heard I'll try to get some info from sonoff about it

[@kilof8]

@@notenoughtech Did you get some info?

[@CosmicToy]

Did you get some info?

[@kmchmk]

This doesn't look like it came from eWeLink. This is a third party project I think.

[@notenoughtech]

It's not an eWeLink node, but it uses eWeLink api for developpers

[@squalazzo]

all my devices are tasmotized, if no esp inside, i'll just sell them...

[@notenoughtech]

I keep it all as I often go back to compare products etc