is this app EOL ? since a update 2 months ago it has been very bad connecting to my airco. keeps saying device not reachable while it is. up until a (couple) of days ago i could fix it by restarting the app, that does not work anymore now.
Wut?
I think @Ziglar means: End of Life, a term in manufacturing and technology indicating that a product has reached the end of its functional, supported, or marketable existence. When a product reaches EOL, the manufacturer stops producing, selling, or providing updates (like security patches) for it.
1 Like
I did not know the term Wut? 
Unfortunately, Iām unable to connect the air conditioners to the app. Adding them to Homey goes smoothly and the air conditioners have been assigned a fixed IP address. However, after connecting, Homey reports that the device is unreachable.
The support documentation mentions that the Smart M-Air app must not be logged in. However, Iām not sure how to log out of it. I have already removed the app from my phone, but that did not seem to make any difference.
I sincerely hope you can help me resolve this issue.
1 Like
@Jesse_de_Vroet I think your problem is the same as mine. Read back a bit and youāll see that the newer versions of the Modules have this issue. You can add the devices, but they donāt connect and show ādevice unreachableā in Homey.
I also donāt really see an answer from @evdpol about whether we could solve this with software. No idea where the problem lies and Iām happy to test, but it doesnāt seem to be taken seriously. Of course, as has already been mentioned, itās a community app and everything is voluntary, but it would be nice to get an answer if he thinks it is possible.
Maybe the App could also indicate that it only works with the older 52010 version and not with the newer 52025 (BL3372-P_1V1) versions as @pvdven has mentioned to be the difference.
1 Like
I do think we can solve it with the software, but as I do not own a device with the newer software, itās hard to know where to begin at this point. I am keeping my eyes on the HA integration also. Does the HA integration work with the newer software that anyone knows?
I donāt know, I personnally donāt know anybody that has this version and uses HA. Maybe I can send you a diagnostics report so you can view what the error is?
Yeah, could you send me a report right after youāve added the device to Homey, and it becomes unavailable?
Done, just added the two Aircoās again and right after they become unavailable Iāve created an diagnostics report for you. Let me know if I can try anything else.
If necessary, I can also share a report with you.
And I also do not use HA.
Wat zie je voor output, wanneer je op de command line van je computer het volgende uitvoert?
Vervang <IP> met het IP adres van je airco.
MacOS:
curl -L http://<IP>:51443/beaver/command
PowerShell (Windows - untested):
$response = Invoke-RestMethod 'http://<IP>:51443/beaver/command' -Method 'POST' -Headers $headers -Body ""
$response | ConvertTo-Json
En als je daar eventueel een foutmelding krijgt, vervang dan eventueel http met https:
https://<IP>:51443/beaver/command
Kunnen jullie de resultaten hier posten? Als het goed, krijg je een melding zoals:
Not supported this command
Ik get these responses with http and https on Windows 11:
And this response on my MacBook:
Patricks-MacBook-Pro:~ Patrick$ curl -L http://192.168.192.136:51443/beaver/command
curl: (56) Recv failure: Connection reset by peer
Patricks-MacBook-Pro:~ Patrick$ curl -L https://192.168.192.136:51443/beaver/command
curl: (35) Send failure: Broken pipe
Patricks-MacBook-Pro:~ Patrick$
That explains why Homey cannot control your units. Iām not sure what the difference is between firmware 52010 and 52025 (BL3372-P_1V1), but it looks like the API (endpoints) are also not the sameā¦ 
*On my Macbook
Via HTTP no reply:*
curl -L http://192.168.1.206:51443/beaver/command
curl: (52) Empty reply from server
Via HTTPS my MacBook doesnāt trust the certificate:
curl -L https://192.168.1.206:51443/beaver/command
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: curl - SSL CA Certificates
Over HTTPS with certificate check skipping option:
curl -L https://192.168.1.206:51443/beaver/command -k
Page Not Found
/beaver/command**%**
This is the same as when I use a browser to go to the /beaver/command path on HTTPS.
Page Not Found
/beaver/command
This is rather interesting. I see that the HA integration uses a certificate when possible, which is probably (by reading this pull request and this issue) required to connect to the newer units.
@KingSize32 Could you create a certificate like in the PR, and use it with cURL and see if that works, and post the reply here?
1 Like
Following this thread for a while. Looking forward to getting my 2 new MHI units working in Homey 
I have HA running and can confirm that the new MHI models work properly with the HA plugin (HACS)
Are you willing to test the app after I try to implement a secure connection?
Yes of course!
1 Like
