zhimi.airpurifier.vb2 support

stason325 / node-red-contrib-miio-localdevices

Nodes for controlling MIIO devices via node-mihome lib. List of devices and commands to be extended.

GNU General Public License v3.0

18 stars 7 forks source link

zhimi.airpurifier.vb2 support #9

Closed Atalicsku closed 2 years ago

Atalicsku commented 2 years ago

Thanks for this module

Could you add Mi Air Purifier Pro H as supported device?

Br, Attila

stason325 commented 2 years ago

Thanks for this module

Could you add Mi Air Purifier Pro H as supported device?

Br, Attila

Hi, Attila.

zhimi.airpurifier.vb2 is already supported via my nodes. Please see https://github.com/stason325/node-red-contrib-miio-localdevices/blob/master/DEVICES.md

When configuring and testing usage follow the instructions in readme and don't forget to copy-paste defFile for your purifier (please pay attention on point 3 here: https://github.com/stason325/node-red-contrib-miio-localdevices#send-node)

Regards, Stas

Atalicsku commented 2 years ago

Thank you. That was a problem. Connection appears OK and disappear. I get back the msg. The payload is empty. I am doing something wrong...

stason325 commented 2 years ago

Thank you. That was a problem.

Connection appears OK and disappear.

I get back the msg. The payload is empty.

I am doing something wrong...

Did you copy-paste the defFile to target folder and reboot NR after that?

Atalicsku commented 2 years ago

Thank you. That was a problem. Connection appears OK and disappear. I get back the msg. The payload is empty. I am doing something wrong...

Did you copy-paste the defFile to target folder and reboot NR after that?

yes

Atalicsku commented 2 years ago

Thank you. That was a problem. Connection appears OK and disappear. I get back the msg. The payload is empty. I am doing something wrong...

Did you copy-paste the defFile to target folder and reboot NR after that?

yes

not supported message missed

stason325 commented 2 years ago

not supported message missed

Could you share some pictures of debug messages from get-node and send-nodes after sending some basic commands?

Need to understand what goes wrong...

Atalicsku commented 2 years ago

not supported message missed

Could you share some pictures of debug messages from get-node and send-nodes after sending some basic commands?

Need to understand what goes wrong...

stason325 commented 2 years ago

not supported message missed

Could you share some pictures of debug messages from get-node and send-nodes after sending some basic commands?

Need to understand what goes wrong...

What I see is that device does not respond ... most likely it is because 1 sec auto-polling interval. You overpushed your device with too many messages and device hung, that's why you see "call to device timed out" error message. I strongly recommend not to use less than 15 sec auto-polling interval.

For now you need to increase auto-polling interval up to say 30 secs, reboot the device and reboot NR.

After that I believe everything should go right. Try and come back with the results.

Atalicsku commented 2 years ago

not supported message missed

Could you share some pictures of debug messages from get-node and send-nodes after sending some basic commands?

Need to understand what goes wrong...

What I see is that device does not respond ... most likely it is because 1 sec auto-polling interval. You overpushed your device with too many messages and device hung, that's why you see "call to device timed out" error message. I strongly recommend not to use less than 15 sec auto-polling interval.

For now you need to increase auto-polling interval up to say 30 secs, reboot the device and reboot NR.

After that I believe everything should go right. Try and come back with the results.

Shit. :) Right. That was the problem. It is working. I saw before a normal payload so I do not understand what was the problem. Thank you very well.

stason325 commented 2 years ago

That's ok. It is great that issue was minor and easily solved 👍🏻