-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSL "Fix"" Breaks MIM-H02 #52
Comments
I agree with you, but v4.1 is working. v4.2 breaks it again. |
so for now whoever using MIM-H02 like me and you should stay on v4.1 until they fix v4.2 to be compatible with MIM-H02 |
Thanks for the clarification. I didn’t manage to go onto 4.1 as it moved me from 4.0 straight to 4.2. Hopefully it’ll be fixed soon. |
Mine stopped working after upgrade to 2022.11.5 i think. No versions is working |
same here, no version works |
Yeah mines stopped working now on any version, seems to have dropped off in recent updates of HA |
so what are you guys (with MIM-H02- samsung_2878.yaml) are using? |
I stayed on 4.0 / 4.1 and never choose to update in Home Assistant HACS since. Those are the versions I know works with MIM H02. |
Yep same here, seems to work on those versions. |
that is what I did too until yesterday. But the new 2023.6 beta broken it this morning. I can roll back to regular release for now but it may still broken when they release it next week. |
Really? Damn. That’s no good ! |
does anyone know if MIM-H03 or MIM-H04 work reliably? Happy to throw couple of hundreds at this problem to go away instead of mucking around it for each update. Thanks for your inputs. |
tried that. no dice :( |
Originally I got MIM-H02 to work. Then one of the climate_ip release broke MIM-H02. I threw in the towel, and bought a MIM-H03, which was still compatible with my AC. I reverted back to MIM-H02 after one of the climate_ip release got it working again. |
weird thing is I have reverted to HA 2023.5 and climate_ip 4.1 still getting the same error. I have restored from last night's backup still same error. just to make sure, I restarted my whole aircon system (including the MIM-H02) and vola.. its working. atleast with 4.1 for now. |
So are you back on 2023.5 now with 4.1 ? |
Yes
…On Thu, 1 Jun 2023 at 17:09, lawrencelnm ***@***.***> wrote:
weird thing is I have reverted to HA 2023.5 and climate_ip 4.1 still
getting the same error. I have restored from last night's backup still same
error. just to make sure, I restarted my whole aircon system (including the
MIM-H02) and vola.. its working. atleast with 4.1 for now.
So are you back on 2023.5 now with 4.1 ?
—
Reply to this email directly, view it on GitHub
<#52 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAWDYAGCR5SBQ7JVRBL3TDXJBBMXANCNFSM55DC6JMA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi all. I saw Release 5.2 was out, but there wasn't much detailed in the release note other than another 'SSL' fix. I decided to bite the bullet and test this out. I am happy to report that I have successfully upgraded from Release 4.1 to release 5.2 without breaking MIM-H02. For those who have been stuck (in the past release), we are now able to move forwards. |
The latest release 4.2 / 4.1 which targets SSL fix broke the integration with MIM-H02 (Using 'samsung_2878.yaml')
As soon as I roll back to 4.0, the air con shows up again in Home Assistant.
The text was updated successfully, but these errors were encountered: