Hi All,
It has been a long time since I was last active here. In the early stages of homey I created some apps for z-wave devices. But along the way, I got other priorities.
Now I am biting into a new thing.
I have a Haier AC. There is no Haier app available yet.
The wifi module is connected through USB and therefor easily replaced. The Haier ac’s consist of 2 types:
- Based on hOn
- Based on SmartAir
There is a piece of software called “ESPhome” that can be installed on a Wemos D1 mini.
And can than be controlled by Home Assistent. But i don’t have that, i have a Homey ofcourse
Someone created a piece of ESPhome software which should connect the Haier hOn AC to Home assistent: https://github.com/paveldn/haier-esphome
But I dont want to control my AC with Home assistent (for I don’t have that), I want to control my AC with my Homey.
Fortunately, someone has started developping a Homey app for ESPhome devices.
(which is than applied to the appstore by someone else without asking the developer!)
https://github.com/Inversion-NL/Homey-ESPhome
So now my plan is to add the ESPhome device for Haier AC into that app.
https://github.com/priknr1/Homey-ESPhome
But, my programming skills for homey are quite rusty. I added a new device, and the app is compiling.
I can fill in the IP and port for the ESPhome device, and it starts to communicate.
But then I get the following error 7 times before a timout occurs:
2023-04-14 18:11:38 [ManagerDrivers] [Driver:esphome-haier_ac] Error on device 192.168.1.119: TypeError: Cannot read property ‘deserializeBinary’ of undefined
at deserialize (/node_modules/esphome-native-api/lib/utils/messages.js:90:52)
at Socket. (/node_modules/esphome-native-api/lib/connection.js:26:34)
at Socket.emit (events.js:311:20)
at addChunk (_stream_readable.js:294:12)
at readableAddChunk (_stream_readable.js:275:11)
at Socket.Readable.push (_stream_readable.js:209:10)
at TCP.onStreamRead (internal/stream_base_commons.js:186:23)
Is this 7 times the same error on a retry, or 7 different errors?
What could cause this error?
Does it maybe have to do with unknown capibily names?