Help with - EwpeSmart Air Conditioners via MQTT (Gree Smart) Topic is solved

[FireWizard]

This didn't help. However you are now on the latest version.
Have you already tried to contact the developer on Github.
As I do not own the equipment, I'm running out of ideas, what might be wrong.
Perhaps based on the error report the developer can give you an indication where to look.
Sorry that I can't help you any further.

Regards
FireWizard

[Gizmo2000]

Thanx for your help.
It's already on github. At the moment no response to it.

[Gizmo2000]

Problem is now fixed. I had to upgrade node.js to version 8+

now it patially works.


2019-04-10T05:14:35.403Z [info]: "Server is listening on 0.0.0.0:43839"
2019-04-10T05:14:35.507Z [info]: "New device found: xxxxx(xxxxx), binding..."
2019-04-10T05:14:35.513Z [debug]: "Sending request to 192.168.0.185:7000: {\"mac\":\"xxxxxx\",\"t\":\"bind\",\"uid\":0}"
2019-04-10T05:14:35.530Z [info]: "New device bound: 1e516992 (192.168.0.185:7000)"
2019-04-10T05:14:35.534Z [debug]: "MQTT message: ewpe-smart/xxxx"
2019-04-10T05:14:40.541Z [debug]: "Sending request to 192.168.0.185:7000: {\"cols\":[\"Pow\",\"Mod\",\"TemUn\",\"SetTem\",\"TemRec\",\"WdSpd\",\"Air\",\"Blo\",\"Health\",\"SwhSlp\",\"Lig\",\"SwingLfRig\",\"SwUpDn\",\"Quiet\",\"Tur\",\"SvSt\"],\"mac\":\"xxxxxxxx\",\"t\":\"status\"}"
crypto.js:183
var ret = this._handle.final();
^

Error: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
at Decipheriv.final (crypto.js:183:26)
at decrypt (/home/pi/ewpe-smart-mqtt/app/encryptor.js:15:48)
at Socket.messageHandler (/home/pi/ewpe-smart-mqtt/app/connection.js:68:34)
at emitTwo (events.js:131:20)
at Socket.emit (events.js:214:7)
at UDP.onMessage [as onmessage] (dgram.js:659:8)

npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is most likely a problem with the ewpe-smart-mqtt package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node index.js
npm ERR! You can get their info via:
npm ERR! npm owner ls ewpe-smart-mqtt
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 4.14.98-v7+
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "start"
npm ERR! cwd /home/pi/ewpe-smart-mqtt
npm ERR! node -v v8.11.1
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/pi/ewpe-smart-mqtt/npm-debug.log
npm ERR! not ok code 0

[FireWizard]

Hi,

If I look to your debug output, I see that you use now v 8.11.1 of nodejs.
However the latest recommended LTS version is 10.15.3 which includes npm v 6.4.1.
With npm you are still at version 1.4.21
See: https://nodejs.org/en/download and also https://www.npmjs.com/get-npm
Perhaps an idea to upgrade npm as well following the last link.

Regards

[Markokaa]

I have problem when i reboot my system. After reboot ewpe-smart not working. I try to manually start "npm start" comman and get this error:

2019-07-12T05:51:32.798Z [info]: "Server is listening on 0.0.0.0:47828"
2019-07-12T05:51:32.900Z [info]: "New device found: 1e481f22 (f4911e481f22), binding..."
2019-07-12T05:51:32.919Z [info]: "New device bound: 1e481f22 (192.168.1.107:7000)"
2019-07-12T05:51:32.921Z [info]: "MQTT message received: ewpe-smart/f4911e481f22 {\"cid\":\"f4911e481f22\",\"bc\":\"\",\"brand\":\"gree\",\"catalog\":\"gree\",\"mac\":\"f4911e481f22\",\"mid\":\"10001\",\"model\":\"gree\",\"name\":\"1e481f22\",\"series\":\"gree\",\"vender\":\"1\",\"ver\":\"V1.2.1\",\"lock\":0,\"address\":\"192.168.1.107\",\"port\":7000,\"key\":\"5Ef8Hi1Kl4No7Qr0\"}"
2019-07-12T05:51:37.939Z [error]: "Can not decrypt message from f4911e481f22 (192.168.1.107:7000) with key a3K8Bx%2r8Y7#xDh"

I think theres some key error, but where i but new key?

[Markokaa]

I have problem when i reboot my system. After reboot ewpe-smart not working. I try to manually start "npm start" comman and get this error:

2019-07-12T05:51:32.798Z [info]: "Server is listening on 0.0.0.0:47828"
2019-07-12T05:51:32.900Z [info]: "New device found: 1e481f22 (f4911e481f22), binding..."
2019-07-12T05:51:32.919Z [info]: "New device bound: 1e481f22 (192.168.1.107:7000)"
2019-07-12T05:51:32.921Z [info]: "MQTT message received: ewpe-smart/f4911e481f22 {\"cid\":\"f4911e481f22\",\"bc\":\"\",\"brand\":\"gree\",\"catalog\":\"gree\",\"mac\":\"f4911e481f22\",\"mid\":\"10001\",\"model\":\"gree\",\"name\":\"1e481f22\",\"series\":\"gree\",\"vender\":\"1\",\"ver\":\"V1.2.1\",\"lock\":0,\"address\":\"192.168.1.107\",\"port\":7000,\"key\":\"5Ef8Hi1Kl4No7Qr0\"}"
2019-07-12T05:51:37.939Z [error]: "Can not decrypt message from f4911e481f22 (192.168.1.107:7000) with key a3K8Bx%2r8Y7#xDh"

I think theres some key error, but where i but new key?

I reinstall docker image and now it's working fine after reboot.

[BarryT]

Oeps..i did a reply to answer a question but didnt read the whole story!
Its fixed already

[mbulles]

Hi,

I'm trying to get the EWPE MQTT stuff to work as well.

My MQTT is working as I can send info to the virtual switch which works, bu when trying to start npm I receive an error that the package.json file is missing.

gree.jpg (122.86 KiB) Viewed 10431 times

This file is indeed not in the /domoticz/plugins/ewpe-smart-mqtt folder but it is also not on Github source https://github.com/stas-demydiuk/domoti ... qtt-plugin

Any help appreciated.

Thanks

[FireWizard]

Hi,

If you go to: https://github.com/stas-demydiuk/ewpe-smart-mqtt

You will find package.json as the last file

Did you install this?

Regards

[mbulles]

Thanks for your quick reply.

Something is not completely clear to me.

What gets me confused here is the bridge+plugin and where/how they need to be installed.

Does the ewe Domoticz plugin+the ewpe MQTT need to be placed in the same directory?
Because that is what it seems when running both the commands;

ewpe-smart-mqtt bridge creates ewpe-smart-mqtt folder in domoticz/plugins//ewpe-smart-mqtt
git clone https://github.com/stas-demydiuk/ewpe-smart-mqtt

ewpe Domoticz plugin creates files in same folder domoticz/plugins
https://github.com/stas-demydiuk/domoti ... qtt-plugin

npm.jpg (171.99 KiB) Viewed 10420 times

So in my case all the files are in the same folder now ewpe plugin+ewpe MQTT bdrige in /domoticz/plugins
When I run "npm start" I receive the below nmp error;

npm-error.jpg (309.71 KiB) Viewed 10420 times

Domoticz log throws this error;
Which could make sense because npm is not working as expected.

gree-error.jpg (133.38 KiB) Viewed 10420 times

Any thoughts?

Regards,

[FireWizard]

Hi,
@mbulles

You wrote

Something is not completely clear to me.

What gets me confused here is the bridge+plugin and where/how they need to be installed.

Does the ewe Domoticz plugin+the ewpe MQTT need to be placed in the same directory?
Because that is what it seems when running both the commands;

ewpe-smart-mqtt bridge creates ewpe-smart-mqtt folder in domoticz/plugins
git clone https://github.com/stas-demydiuk/ewpe-smart-mqtt

ewpe Domoticz plugin creates files in same folder domoticz/plugins
https://github.com/stas-demydiuk/domoti ... qtt-plugin

This is correct.
If you install them, according to the description with git clone, they are installed in the same directory.

But you have to follow the steps:

1. Clone or download this repository :

Code: Select all

git clone https://github.com/stas-demydiuk/ewpe-smart-mqtt

2. Install dependencies :

Code: Select all

npm install

3. Make initial configuration by setting environmental variables : See https://github.com/stas-demydiuk/ewpe-smart-mqtt
4. Run the bridge :

Code: Select all

npm start

I assume, you don't install it in a Docker container.

To set an environment variable, do as follows:

Code: Select all

export MQTT_SERVER=mqtt://127.0.0.1

(if your Mosquitto broker runs on the same hardware as Domoticz)
Do that for all variables.

And then:

5. Clone repository into your domoticz plugins folder, as follows:

Code: Select all

cd domoticz/plugins
git clone https://github.com/stas-demydiuk/domoticz-ewpe-smart-mqtt-plugin.git ewpe-smart-mqtt

6. Restart domoticz
7. Go to "Hardware" page and add new item with type "EwpeSmart Air Conditioners via MQTT"
8. Set your MQTT server address and port to plugin settings

Regards

[mbulles]

Ok. I will try again first thing tomorrow morning.
One thing I know for sure is the variables have not been set.

Thx for your support so far.

I'll give an update tomorrow.

[mbulles]

Hi

I made 3 out of 4 AC's work in Domoticz!

I think indeed the order of how things were setup I did wrong and that is why the AC's could not be found.

Once I ran npm install again in the domoticz/plugin/ewpe folder everything started to work.

Does npm need to run continuously in the background using "npm start &" command?

I was wondering if there is a limitation in the number of AC's that can be connected as it only finds 3 (3x found/3xbound, but missing nr 4)out of 4 of my AC's. All4 the AC's can be seen and used by the Gree EWPE App.

acs-found.jpg (218.47 KiB) Viewed 10401 times

I have a Gree U-match with 4 AC's connected.

Further I see all the switches but where can I raise or lower the temperature using a switch?

Gree-U-match.jpg (290.59 KiB) Viewed 10401 times

And lastly if I reboot my raspi, do I need to manually restart npm or other services depending on MQTT?

Thanks for being so helpful, much appreciated!

Next I need to see if I can get my Mitsubishi also to work using the MELCloud setup.

[FireWizard]

Hi,
@mbulles

You wrote:

Does npm need to run continuously in the background using "npm start &" command?

"npm start" is the equivalent of running whatever value is specified in the scripts → start attribute of the package.json file.
If you look to your package.json file, you will see that in your case "start": "node index.js" is indicated.

So it will run node index.js

I would create a .service file. You can find the whole procedure e.g. at: https://www.axllent.org/docs/view/nodej ... h-systemd/

I was wondering if there is a limitation in the number of AC's that can be connected as it only finds 3 (3x found/3xbound, but missing nr 4)out of 4 of my AC's. All4 the AC's can be seen and used by the Gree EWPE App.

That would be very strange. However I don't own this hardware, so I cannot test.

Try to communicate with the bridge. See: https://github.com/stas-demydiuk/ewpe-smart-mqtt
Use mqtt_pub ewpe-smart/devices/list

See: https://mosquitto.org/man/mosquitto_pub-1.html and use the -L option.

But I cannot tell, why 1 AC has not been found.

And lastly if I reboot my raspi, do I need to manually restart npm or other services depending on MQTT?

You have to restart your node index.js, but I suggested to run it as a service.
I assume that the MQTT server is also running as a service?

Did you ever run:

Code: Select all

sudo systemctl enable mosquitto.service

?

Regards

[kabaret10]

Hello, anyone tried to setup this with docker?
installed container on my RPi4 -> ewpe-smart-mqtt using command:

Code: Select all

##### MQTT for EWPE SMART https://github.com/stas-demydiuk/ewpe-smart-mqtt
sudo docker run -it \
    --network="host" \
    -e "MQTT_SERVER=mqtt://127.0.0.1" \
    -e "MQTT_BASE_TOPIC=ewpe-smart" \
    -e "NETWORK=192.168.1.255" \
    -e "DEVICE_POLL_INTERVAL=5000" \
    --name ewpe-smart-mqtt \
    -v /mnt/mosquitto:/mosquitto \
    demydiuk/ewpe-smart-mqtt:arm32v6

In logs i can see, that it cant connect to itself?

Code: Select all

> [email protected] start /opt/ewpe-smart-mqtt
> node index.js
2020-07-30T10:08:54.330Z [info]: Trying to connect to MQTT server mqtt://127.0.0.1 ...

Also I did open port on Domoticz container 1883:1883 and like above it can't connect to broker.

Code: Select all

2020-07-30 13:39:57.657 Error: (EwpeSmart Air Conditioners via MQTT) Failed to connect to: 127.0.0.1:1883, Description: Connection refused
2020-07-30 13:39:57.658 Error: (EwpeSmart Air Conditioners via MQTT) Disconnected from MQTT Server: 127.0.0.1:1883

Do I need to install something else? I think somenthing is going on with broker container.
@EDIT I've got it. Replaced mqtt server and started to work.

[mVik85]

Hi Guys,

Well, it cost me a couple of nights, but finally I managed to set this up form my 2 Gree Fairy/Comfort X (GWH09ACC & GWH12ACC) ACs.
I was really happy with the success considering that was is my first home automation project, and also the first with RPI or Linux (apart from Domoticz and Ubuntu installation)
So I thought to summarize and share how I did it, the issues I ran into, since the available tutorials were not enough form my experience level.

First of all, ewpe-smart-mqtt and EwpeSmart - Domoticz Python Plugin shall be installed in two different directories!

1. Followed th steps from here: https://github.com/stas-demydiuk/ewpe-smart-mqtt
My install folder is the same level where the domoticz folder is: /home/pi

Here you also have to install npm & nodejs.
ARMv6 (Pi Zero) is not listen on nodejs.org currently, you have to google for the link (node js armv6), e.g.:

Code: Select all

wget https://nodejs.org/dist/v10.16.3/node-v10.16.3-linux-armv6l.tar.xz

Extract tar.xz

Code: Select all

tar -xf node-v10.16.3-linux-armv6l.tar.xz

Install is just copy:

Code: Select all

cd node-v6.11.1-linux-armv6l/
sudo cp -R * /usr/local/

--> in 3. Environmental variables which differs from the default in your case can be set temporarily (example):

Code: Select all

export MQTT_SERVER=mqtt://localhost - your server IP
export NETWORK=192.168.0.255 - IP range of your ACs

BUT you better add permanently by editing ewpe-smart-mqtt/index.js, otherwise it is lost after restart:

Code: Select all

const networkAddress = process.env.NETWORK || '192.168.0.255';
const mqttServerAddress = process.env.MQTT_SERVER || 'mqtt://localhost';
const mqttBaseTopic = process.env.MQTT_BASE_TOPIC || 'ewpe-smart';
const pollInterval = process.env.DEVICE_POLL_INTERVAL || 5000;
const mqttServerUsername = process.env.MQTT_USERNAME || '';
const mqttServerpassword = process.env.MQTT_PASSWORD || '';
const mqttServerport = process.env.MQTT_PORT || 1883;

2. Installed the plugin in domoticz/plugins: https://github.com/stas-demydiuk/domoti ... qtt-plugin
--> I got several problems at this point, check your Domoticz log if the python scripts are running well, if not:

make scripts executable in domoticz/plugins/ewpe-smart-mqtt:

Code: Select all

chmod +x *.py

install libpython:

Code: Select all

sudo apt-get install libpython3.4

install python3-dev:

Code: Select all

sudo apt-get install python3-dev

After a full restart the switches became available in Domoticz (under Devices), and I could switch the ACs.
Note, at this point, after every restart you have to start manually the ewpe-smart-mqtt:

Code: Select all

/ewpe-smart-mqtt $ npm start

To fix this you have to run it as a service, for this I followed the instructions linked by @FireWizard :
https://www.axllent.org/docs/nodejs-ser ... qus_thread

This is the specific code for my ewpe-smart-mqtt.service with npm:

Code: Select all

[Unit]
Description=Node.js ewpe-smart-mqtt
#Requires=After=mysql.service       # Requires the mysql service to run first

[Service]
ExecStart=/usr/local/bin/npm start
# Required on some systems
WorkingDirectory=/home/pi/ewpe-smart-mqtt
Restart=always
# Restart service after 10 seconds if node service crashes
RestartSec=10
# Output to syslog
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=nodejs-example
#User=<alternate user>
#Group=<alternate group>
Environment=NODE_ENV=production PORT=1337

[Install]
WantedBy=multi-user.target

Last thing I needed was to add a startup delay to Domoticz, to wait for other processes to start, otherwise I got an error message on boot:

Code: Select all

sudo nano /etc/init.d/domoticz.sh

add ARGS to define delay, 5 seconds in my case:

Code: Select all

DAEMON_ARGS="$DAEMON_ARGS -startupdelay 20"

ToDo:
As I've experienced it does not reconnect in case of network error (router restart), but this could be managed with the Domoticz script I guess, but suggestions are welcomed

Thank you guys for making this, and the support to all the sources I've worked from.

[philips]

Hi Guys,

Well, it cost me a couple of nights, but finally I managed to set this up form my 2 Gree Fairy/Comfort X (GWH09ACC & GWH12ACC) ACs.
I was really happy with the success considering that was is my first home automation project, and also the first with RPI or Linux (apart from Domoticz and Ubuntu installation)
(...)

mVik85, your post is very helpfull, without it I wouldn't make it work. The problem with this plugin is the lack of good documentation.
To make things work I'll try also to clear things - my small Q&A :

How to connect Air Conditioner with the MQTT so they talk to each other ?
You don't do anything. The Air Conditioner will itself start talking to MQTT. Just magic.

In Domoticz how to add buttons controling the Air conditioner ?
In Domoticz available futures and switches of the Air Conditioner will appear themself, you do not add them yourself .

What if the switches don't appear ?
If the switches don't appear this means there is no connection between Air Conditioner <--> Mqqt or Mqqt<--> Domoticz plugin.
Check if your MQTT is working, if the username and password of mosquitto is correct.

The buttons appeared but I can't controll anything, they just don't work. What now ?
You need to make the .py files in executable, see mVik85 post above to solve this isssue. Remember to reboot you server (server, not Domoticz) after making them exectuable.

Making the NPM start does not work, what now ?
The NPM should be started from the folder /home/pi/ewpe-smart-mqtt (not from /home/pi/domoticz/plugins/ewpe-smart-mqtt !)
After starting "npm start" you should see something like this:

screen 11.JPG (115.66 KiB) Viewed 10012 times

You can see that the Air Conditioner has been discovered under 192.168.10.70:7000 and all the parameters (temperature etc) are there.
Check if you have the additional elements installed like libpython3.4 and python3-dev

NPM started and the Air conditioner was discovered but in Domoticz nothing happened, what now ?
Turn on debug in the Domoticz plugin:

screen 3.JPG (61.71 KiB) Viewed 10012 times

Check the logs in Domoticz. At the begining there should be also an information about connecting to MQTT and later there should be also something like this:

screen 2.JPG (96.16 KiB) Viewed 10012 times

I don't understand how the system works, I'm lost with what connects to what and what plugins to install.
Yes, this is confusing. This link might help: https://blog.szygmon.pl/domoticz/sterow ... -domoticza
So it works this way: Air Conditioner --> EWPE Bridge --> MQTT Sever --> EWPE Domoticz plugin
To make it work:
1. Install and run Mosquito
2. Install the bridge in "/home/pi/". It is called "ewpe-smart-mqtt" bridge, from here: https://github.com/stas-demydiuk/ewpe-smart-mqtt
Note: Install the normal version of the bridge OR the docker version, not both (!) as it kind'a suggested in the description in the link.
4. Edit the /home/pi/ewpe-smart-mqtt/index.js file with nano and adjust the settings to meet you mqtt server (IP, username and password, port)
3. Install NPM:

Code: Select all

sudo apt-get install npm

4. Again install NPM but inside the /home/pi/ewpe-smart-mqtt/ :

Code: Select all

 cd /home/pi/ewpe-smart-mqtt
 npm install

and run NPM

Code: Select all

npm start

5. Make the bridge still work after rebooting your system by creating a file called "ewpe-smart-mqtt.service" (see above post)
6. Reboot your system

Code: Select all

sudo reboot

6. Finally install the Domoticz plugin: https://github.com/stas-demydiuk/domoti ... qtt-plugin in the Domoticz plugin folder
7. Restart Domoticz
8. In Domoticz add new hardware with EWPE plugin with settings meeting your mqtt settings (IP, username nad password)
9. Wait until your Airconditioner switches will appear in Domoticz automaticly.

[imek100]

Please help. I'm stuck at the point shown in the logs. My air conditioner is Gree.

2021-07-25T10:14:46.930Z [info]: Trying to connect to MQTT server mqtt://127.0.0.1 ...
2021-07-25T10:14:47.069Z [info]: Successfully connected to MQTT server
2021-07-25T10:14:47.100Z [info]: Socket server is listening on 0.0.0.0:56538
2021-07-25T10:14:47.102Z [info]: Scanning network 192.168.1.255 for available devices...
2021-07-25T10:14:47.376Z [info]: New device found: c6537cc2 (), binding...

and nothing else happens.

[jannl]

I got the same problem, for some reason it looks like the mac-address is not found (should be between the empty() ), as far as I can read the java code in de the app subdir.

Any clues?
May be node.js too new? Function deprecated somehwere?

[jannl]

No one with a hint?
Issue at github does not help as well untill now