Closed ZHonry closed 4 years ago
Hi, ZHonry. "Connecting..." usually means that the node can not connect to AC, the things you could check:
I installed nodered in docker, and the Ping result is as shown in the figure. When using another project transferred to mqtt, it was registered successfully and cannot be bound. Is it because the air conditioner is the new model?
Could you try temporarily running NodeRED with the gree-node outside of the docker to see if the problems is not related to docker?
After installing nodered in Debian, it has been confirmed that the air conditioner can be pinged, but it is still the same as installing nodered in docker. The air conditioner currently uses UDP distribution network and is not bound in the app. There is really no coding foundation at all, please forgive me.
I've released a new version 0.1.1 where you can turn on debug messages:
The version will be available in NodeRED palette in a short while. Would be nice to see what you have in the logs of you NodeRED process.
This is the log file greeac.log
Try the version 0.1.2 of this node.
greeacv0.1.2.log Log file for 0.1.2
Try 0.1.3
I've successfully connected. I'll see if I can control it. Thank you very much for your support.
Successfully control AC, and can get status, thanks again.
I use the HomeAssistant-GreeClimateComponent plug-in in ha, which can access my GREE AC normally, but using your node in NR, the connection is always displayed, can you please see what the problem is? (My English is not good, this is translated by Google, please forgive me!)
No other tips.
I look forward to your answer, thank you.