# iHost 2.5.0. What a mess!

**URL:** <https://forum.ewelink.cc/t/ihost-2-5-0-what-a-mess/157246>\
**Category:** eWeLink CUBE\
**Created:** [March 30, 2025, 10:35pm UTC](https://forum.ewelink.cc/t/ihost-2-5-0-what-a-mess/157246 "2025-03-30T22:35:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![p.2msousa](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@p.2msousa](https://forum.ewelink.cc/u/p.2msousa)\
**Post date:** [March 30, 2025, 10:35pm UTC](https://forum.ewelink.cc/t/ihost-2-5-0-what-a-mess/157246/1 "2025-03-30T22:35:28Z")

</div>

Hi all!

The ihost problems are not new and at every new “improvement” it only gets worse.

I’m still running 2.5.0. Last time i checked, everything was working “just” fine.

Curently, I’m facing an issue where the SD Card is detected but all the info inside is not accessible and iHost keeps “suggesting” to format it in order to install Add-ons.

The interesting part is that I’ve been using the SD since the moment I bought the ihost, have docker with stuff installed (including eWeLink and HA) and now everything appears to be gone!  
This is not the first time that the SD card is “ignored” but after some power cycles, the thing comes back to life.

Today, I’ve already power cycle 5times and nothing!

Off topic: I always know when iHost is having a crisis and it is when my HA instance does not load.  
IHost CPU 100%, super laggy or non responsive, etc.. the usual drill..  
Now they lauched the 2.5.1 with native HAss.. I’m afraid of such new feature.

Back to the topic: any solution to make iHost remeber my SD and its info?  
I really dont feel like starting from scratch..

Thanks!

---

<div class="post-metadata">

**Author:** ![SuiKa](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/suika/32/8656_2.png) [@SuiKa](https://forum.ewelink.cc/u/SuiKa)\
**Post date:** [March 31, 2025, 1:58am UTC](https://forum.ewelink.cc/t/ihost-2-5-0-what-a-mess/157246/2 "2025-03-31T01:58:49Z")

</div>

Can you provide us your system log and see if we can find out the problem?

---

<div class="post-metadata">

**Author:** ![p.2msousa](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@p.2msousa](https://forum.ewelink.cc/u/p.2msousa)\
**Post date:** [March 31, 2025, 5:45pm UTC](https://forum.ewelink.cc/t/ihost-2-5-0-what-a-mess/157246/3 "2025-03-31T17:45:50Z")

</div>

My full log is 34Mb. Cant only upload max 8Mb file.  
Any specific part you have more interest?

---

<div class="post-metadata">

**Author:** ![SuiKa](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/suika/32/8656_2.png) [@SuiKa](https://forum.ewelink.cc/u/SuiKa)\
**Post date:** [April 1, 2025, 2:00am UTC](https://forum.ewelink.cc/t/ihost-2-5-0-what-a-mess/157246/4 "2025-04-01T02:00:47Z")

</div>

Can you upload it via google drive or one dirve?

> [@p.2msousa](#):
>
> Any specific part you have more interest?

The full log would give a better aspect of the situation.

---

<div class="post-metadata">

**Author:** ![renatoyamane](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@renatoyamane](https://forum.ewelink.cc/u/renatoyamane)\
**Post date:** [April 1, 2025, 7:40pm UTC](https://forum.ewelink.cc/t/ihost-2-5-0-what-a-mess/157246/5 "2025-04-01T19:40:07Z")

</div>

> [@p.2msousa](#):
>
> My full log is 34Mb. Cant only upload max 8Mb file.

Their tar.gz file is created without compression. That is weird.

Zip them by yourself and the size will be reduced to less than 5Mb

---

<div class="post-metadata">

**Author:** ![p.2msousa](https://avatars.discourse-cdn.com/v4/letter/p/d07c76/32.png) [@p.2msousa](https://forum.ewelink.cc/u/p.2msousa)\
**Post date:** [April 1, 2025, 10:19pm UTC](https://forum.ewelink.cc/t/ihost-2-5-0-what-a-mess/157246/6 "2025-04-01T22:19:14Z")

</div>

Hi there,

I’ll share as soon as possible.  
Nevertheless, I already started all over again.  
Formated TF.