init failed - please power cycle the itho unit - (Warning: I2C timeout)

[MartVisser]

Describe the bug
After some time, usually a day after a power cycle, the connection between the module and the unit drops out with the following error message in the logs 'Warning: I2C timeout'

To Reproduce
After a power cycle, wait a day (sometimes two days)

Expected behaviour
N/A

Screenshots
N/A

Device information

• Firmware version: 2.4.2
• Hardware revision: 2
• Type/model number Itho: CVE-S ECO SP
• CC1101 RF module enabled: yes, but no remote configured
• In case of wifi issues, wifi access point make and model: Ubiquiti APs but no WiFi issues.

Itho device type: CVE-Silent
Itho fw version: 27

Debug logging

Itho I2C connection status: init failed - please power cycle the itho unit -

[...]
2022-10-07 08:58:19 I: Warning: I2C timeout
2022-10-07 08:58:31 I: Warning: I2C timeout
2022-10-07 08:58:42 I: Warning: I2C timeout
2022-10-07 08:58:53 I: Warning: I2C timeout
[...]

Desktop (please complete the following information):
N/A

Smartphone (please complete the following information):
N/A

[patrickvorgers]

I have similar behavior with the CVE-S ECO SP.

Configuration of the Itho unit
Itho device type: CVE-Silent
Itho fw version: 27

2022-10-08 07:50:43 I: HW rev: 2, FW ver.: 2.4.2
2022-10-08 07:45:24 I: I2C init: QueryDevicetype - fw:27 hw:27

Just rebooting the add-on card does not solve the issue. I have to manually remove the power from the CVE-S unit and restart.

[arjenhiemstra]

This is most probably a duplicate of issue #102
It seems that there is a bug (?) in itho firmware version 27 that causes the i2c bus to crash. This is the first issue I will pick up next. (I had to put some time in wifi issues first)

[TD-er]

I2C can get stuck for many reasons.
In ESPEasy I try to detect this and then temporary "swap" the SDA and SCL pins. Then try to send some data and swap them back.
This way you "reset" the bus by letting some device "finish" its communication.

[patrickvorgers]

I2C can get stuck for many reasons. In ESPEasy I try to detect this and then temporary "swap" the SDA and SCL pins. Then try to send some data and swap them back. This way you "reset" the bus by letting some device "finish" its communication.

@arjenhiemstra, would this be an idea when you detect the "I2C timeout" or are you already doing this?

[arjenhiemstra]

It's exactly what @TD-er suggests that I would like to try and see if this can release the I2C bus. I just haven't had time to work on it

[MartVisser]

@arjenhiemstra I installed 2.4.3-beta1, but after a few hours it failed again with the following messages in the log:

2022-10-12 19:15:37 I: I2C bus could not clear: SCL clock line held low
2022-10-12 19:15:48 I: Warning: I2C timeout, trying I2C bus reset...
2022-10-12 19:15:51 I: I2C bus could not clear: SCL clock line held low
2022-10-12 19:16:03 I: Warning: I2C timeout, trying I2C bus reset...
2022-10-12 19:16:05 I: I2C bus could not clear: SCL clock line held low
2022-10-12 19:16:16 I: Warning: I2C timeout, trying I2C bus reset...

[patrickvorgers]

I have downgraded to version 2.3.5 and that version is running stable the past 3 days.

[arjenhiemstra]

Thanks for testing @MartVisser ! That was the worst possible outcome but at least we have that info now. I'll work further on a different approach

[didericko]

I am having the same problems. Just installed the beta firmware and will post results in a few days.

[didericko]

I just checked and the unit stopped responding this morning.

Itho device type: CVE-Silent
Itho fw version: 27
HW rev: 2, FW ver.: 2.4.3-beta1

Debug:
2022-10-15 08:02:56 I: Warning: I2C timeout, trying I2C bus reset...
2022-10-15 08:02:58 I: I2C bus could not clear: SCL clock line held low
2022-10-15 08:02:59 I: I2C init: QueryDevicetype - failed

[patrickvorgers]

@arjenhiemstra, just a quick update
I have been running version 2.3.5 stable for the past week so apparently something has changed in the code between version 2.3.5 and 2.4.2 which is causing this issue. Hopefully it gives you some pointers in what may be causing this.

Itho device type: CVE-Silent
Itho fw version: 27

[didericko]

I downgraded to 2.4.2-beta3 and it has been running stable since Sunday morning.

[didericko]

This morning unit stopped responding. I will try to downgrade to 2.3.5 today

[arjenhiemstra]

Please try https://github.com/arjenhiemstra/ithowifi/releases/tag/Version-2.4.3-beta2

[MartVisser]

Updated to 2.4.3-beta2 two hours ago. So far so good, just some information messages;

2022-10-21 20:08:45 I: Info: I2C bus busy
2022-10-21 20:09:26 I: Info: I2C bus busy
2022-10-21 20:16:07 I: Info: I2C bus busy
2022-10-21 20:28:49 I: Info: I2C bus busy
2022-10-21 20:29:29 I: Info: I2C bus busy

[arjenhiemstra]

Those info messages are good, a sign of proper working code. I will remove it once we get to a stable state.
As long as there are no new "Warning: I2C timeout, trying I2C bus reset..." in the log, I'm satisfied.

[didericko]

Back in 2 weeks, will try then, thx!

[MartVisser]

Sadly, it failed again after 4-5 days on 2.4.3-beta2;

[...]
2022-10-27 07:15:36 I: Info: I2C bus busy
2022-10-27 07:15:46 I: Warning: I2C timeout, trying I2C bus reset...
2022-10-27 07:15:49 I: I2C bus could not clear: SCL clock line held low
2022-10-27 07:15:50 I: Info: I2C bus busy
2022-10-27 07:16:00 I: Warning: I2C timeout, trying I2C bus reset...
2022-10-27 07:16:03 I: I2C bus could not clear: SCL clock line held low
2022-10-27 07:16:04 I: Info: I2C bus busy
2022-10-27 07:16:14 I: Warning: I2C timeout, trying I2C bus reset...
2022-10-27 07:16:17 I: I2C bus could not clear: SCL clock line held low
[...]

[arjenhiemstra]

I just released version 2.4.3 which addresses this further. In some situations the add-on could still access the I2C bus while another master was active. The latest code changes in 2.4.3 should prevent this or at least further lower the change of this happening.

[didericko]

The unit still stops responding after a few days. I will look at the log later today.

[MartVisser]

Yes here it also keeps failing on the latest version. Downgraded to 2.3.5 and has been running stable for 7 days now.

[didericko]

2022-11-10 02:09:34 I: Mem free: 110144, Mem low: 72988, Mem block: 44020
2022-11-10 08:09:34 I: Mem free: 109576, Mem low: 59468, Mem block: 44020
2022-11-10 14:09:35 I: Mem free: 109564, Mem low: 59468, Mem block: 44020
2022-11-10 20:09:35 I: Mem free: 100992, Mem low: 59468, Mem block: 44020
2022-11-11 02:09:35 I: Mem free: 100588, Mem low: 59468, Mem block: 44020
2022-11-11 07:30:00 I: System boot, last reset reason: OWDT_RESET
2022-11-11 07:30:00 I: HW rev: 2, FW ver.: 2.4.3
2022-11-11 07:30:06 I: WiFi: connection successful
2022-11-11 07:30:06 I: WiFi info:
2022-11-11 07:30:06 I: SSID:TROPEN | BSSID[74:AC:B9:49:3D:74]
2022-11-11 07:30:06 I: RSSI:-55dBm
2022-11-11 07:30:06 I: Mode:STA
2022-11-11 07:30:07 I: Status:WL_CONNECTED
2022-11-11 07:30:07 I: IP:192.168.1.189
2022-11-11 07:30:07 I: Setup: Virtual remotes, start ID: 32,D1,B4 - No.: 1
2022-11-11 07:30:07 I: Setup: remotes configfile loaded
2022-11-11 07:30:07 I: Setup: init of CC1101 RF module successful
2022-11-11 07:30:07 I: MQTT: connected, System config: 1
2022-11-11 07:30:08 I: Setup: remotes configfile loaded
2022-11-11 07:30:08 I: Webserver: started
2022-11-11 07:30:08 I: mDNS: started
2022-11-11 07:30:08 I: Hostname: nrg-itho-d1b4
2022-11-11 07:30:09 I: Setup: done
2022-11-11 07:30:14 I: I2C init: QueryDevicetype - failed

[didericko]

System rebooted itself this morning after being inresponsive for several days. During this period, log file showed nothing wrong, just the memory log lines. Last line in the log shows the I2C Init failure.

What is the last really stable version? I only need MQTT for HA and nothing else. Version 2.3.5?

[MartVisser]

@didericko I have had the same experiences with version 2.4.3, unresponsive and nothing in the logs. Downgraded to 2.3.5 last week and have been running "stable" ever since. Sometimes it resets to "Low" mode (or "Start/fallback speed" mode, not sure), but I have it set to my desired value, probably a bug in 2.3.5. I also use it via MQTT in Home Assistant.

[arjenhiemstra]

2.3.5 seems to be stable for users that have i2c issues. A lot of extra logging was removed from 2.4.3 because it seemed to be fixed. I'm working nog on a test version that keeps al log of the i2c transactions, in case of a failure I hope this points to the culprit.

Sometimes it resets to "Low" mode (or "Start/fallback speed" mode, not sure), but I have it set to my desired value, probably a bug in 2.3.5.

As far as I know this is not a known bug in 2.3.5. On MQTT there is a last command topic that might point to the reason for switching to "Low" mode.

[arjenhiemstra]

For testing the I2C issues, please use this version:
https://github.com/arjenhiemstra/ithowifi/releases/tag/Version-2.4.4-beta1

I'm very interested in the i2c log it might produce in case the i2c bus gets stuck

[MartVisser]

Just installed 2.4.4-beta1. I don't have to enable anything right? Just wait for the "crash" and check the debug page for the log.

[arjenhiemstra]

This setting needs to be switched on

[arjenhiemstra]

Doesn’t it work altogether or just after some period?
have you power cycled the unit and have you switched the “i2c safe guard” function to “on” in the latest beta6?

[ezwep]

Doesn’t it work altogether or just after some period? have you power cycled the unit and have you switched the “i2c safe guard” function to “on” in the latest beta6?

I'll try to be a little more specific. ;-)
If I run on firmware 2.4.3, the control will stop working at some point. I have not (yet) saved a specific notification of this. So I tested the hw2-v2.4.4-beta4 and the hw2-v2.4.4-beta6 and these and in both cases I get the message
init failed - please power cycle the itho unit -
I also enabled the i2c safe guard option. But that has no effect.

I am now running on 2.4.3 again. If I have to provide specific logs or something, I am happy to do so. Or if I can test something with the beta versions as well.

[arjenhiemstra]

Ok, please follow the following steps:

1. update to the latest beta release (beta6)
2. switch on the i2c safe guard function.
3. Power cycle the unit and report back what happened

[ezwep]

I followed the steps.
Itho device type: Unknown device type
Itho I2C connection status: init failed - please power cycle the itho unit -
I can operate it, but I no longer see the temperature or humidity in the web interface.

PS.
When I restart the device it goes to maximum. Can you edit this somewhere? I have set the setting to Start/fallback speed 20

Thanks for your quick responses!

[arjenhiemstra]

I can operate it, but I no longer see the temperature or humidity in the web interface.

But you did see the temp/hum info on the web interface before?

Did you take the power of your itho off, waited for a bit and then turned the itho on again?

When I restart the device it goes to maximum. Can you edit this somewhere? I have set the setting to Start/fallback speed 20

What settings did you set around the virtual remote? Can you share all the settings you made?

[ezwep]

I can operate it, but I no longer see the temperature or humidity in the web interface.

But you did see the temp/hum info on the web interface before?
Yes, in 2.4.3 I see these values

Did you take the power of your itho off, waited for a bit and then turned the itho on again?
Yes, I wait for a minute or so

When I restart the device it goes to maximum. Can you edit this somewhere? I have set the setting to Start/fallback speed 20

What settings did you set around the virtual remote? Can you share all the settings you made?
I have 1 virtual remote: remtype: RRT CVE
I did some testing and it seems to be due to my MQTT settings, I will look into this further. But after I turn off MQTT it works fine after a reboot that the value is at 20.

[arjenhiemstra]

for those with a CVE and humidity sensor, please try 2.4.4-beta4 and enable i2c safe guard function if available on your add-on hardware revision. It seems to run smoothly on my devices but I'm more than interested how it runs on those devices that have issues.

I have a CVE with built in humidity and CO2 sensor (CVE-S OPTIMA IN, I2C init: QueryDevicetype - fw:27 hw:27). I've had I2C stability problems before, but with firmware 2.4.4-beta6 and "I2C init: Safe guard enabled" I have been running without an I2C failure for 7 days now (and counting). It's never been without a hang for that long before, so it definitely seems your changes help to at least reduce the occurrence of this issue.
Thanks!

Thanks for the feedback and I'm glad to hear this! Hopefully it stays like this! I would appreciate if you could check in again after lets say a week or so to see if it is still working a ok.

Still going strong, 15 days uptime, without a single I2C failure (or other failure), most stable firmware so far for me!

Very nice! Thanks again! I'm working on some last details, after that I'll release it as the next stable version.

[ezwep]

I can operate it, but I no longer see the temperature or humidity in the web interface.

But you did see the temp/hum info on the web interface before?
Yes, in 2.4.3 I see these values

Did you take the power of your itho off, waited for a bit and then turned the itho on again?
Yes, I wait for a minute or so

When I restart the device it goes to maximum. Can you edit this somewhere? I have set the setting to Start/fallback speed 20

What settings did you set around the virtual remote? Can you share all the settings you made?
I have 1 virtual remote: remtype: RRT CVE
I did some testing and it seems to be due to my MQTT settings, I will look into this further. But after I turn off MQTT it works fine after a reboot that the value is at 20.

Hi Arjen,

I was wondering if you can still help me with the problems I'm having? With firmware 2.4.3 I have problems (state hangs at 49, and the unit no longer responds to commands) and 2.4.4-beta6 does not work for me at all.

[arjenhiemstra]

I can operate it, but I no longer see the temperature or humidity in the web interface.

But you did see the temp/hum info on the web interface before?
Yes, in 2.4.3 I see these values

Did you take the power of your itho off, waited for a bit and then turned the itho on again?
Yes, I wait for a minute or so

When I restart the device it goes to maximum. Can you edit this somewhere? I have set the setting to Start/fallback speed 20

What settings did you set around the virtual remote? Can you share all the settings you made?
I have 1 virtual remote: remtype: RRT CVE
I did some testing and it seems to be due to my MQTT settings, I will look into this further. But after I turn off MQTT it works fine after a reboot that the value is at 20.

Hi Arjen,

I was wondering if you can still help me with the problems I'm having? With firmware 2.4.3 I have problems (state hangs at 49, and the unit no longer responds to commands) and 2.4.4-beta6 does not work for me at all.

As I think this is not related to this described issue, could you create a separate issue for this?
And also, please provide the details request of this earlier question:
"Can you share all the settings you made?"

This can be as screenshot or config file which can be downloaded through the file editor on the debug page

[patrickvorgers]

@arjenhiemstra I have been running the latest beta for two weeks now and it has been stable sofar. In the previous releases it would fail within 1 or 2 days.

[ezwep]

I can operate it, but I no longer see the temperature or humidity in the web interface.

But you did see the temp/hum info on the web interface before?
Yes, in 2.4.3 I see these values

Did you take the power of your itho off, waited for a bit and then turned the itho on again?
Yes, I wait for a minute or so

When I restart the device it goes to maximum. Can you edit this somewhere? I have set the setting to Start/fallback speed 20

What settings did you set around the virtual remote? Can you share all the settings you made?
I have 1 virtual remote: remtype: RRT CVE
I did some testing and it seems to be due to my MQTT settings, I will look into this further. But after I turn off MQTT it works fine after a reboot that the value is at 20.

Hi Arjen,
I was wondering if you can still help me with the problems I'm having? With firmware 2.4.3 I have problems (state hangs at 49, and the unit no longer responds to commands) and 2.4.4-beta6 does not work for me at all.

As I think this is not related to this described issue, could you create a separate issue for this? And also, please provide the details request of this earlier question: "Can you share all the settings you made?"

This can be as screenshot or config file which can be downloaded through the file editor on the debug page

Ok, here I made a new request: #150

Thanks

[GelsemaP]

Just wanted to let you know that I experience the same error. After a couple of days I cannot control the itho fan anymore and I2C is disconnected. Powering on and off the fan completely fixes it. I've now updated the firmware to latest beta and enabled safeguard mode and restarted the whole device. Let's see if this also fixes my issue.

some details of my setup:
16103 I: I2C init: Safe guard enabled
15761 I: I2C init: QueryStatus
15452 I: I2C init: QueryStatusFormat - items:12
15280 I: I2C init: QueryDevicetype - fw:27 hw:27
12359 I: Hostname: nrg-itho-741c
11944 I: mDNS: started
11730 I: Webserver: started
11527 I: MQTT: connected, System config: 1
11341 I: Setup: init of CC1101 RF module successful
10604 I: WiFi: connection successful
2757 E: Unable to set wifi disconnect
1652 I: I2C sniffer capable hardware: yes
1498 I: HW rev: 2, FW ver.: 2.4.4-beta6
1257 I: System boot, last reset reason: POWERON_RESET

I have a Itho CVE-S ECO SE connected to Home Assistant.

[mvaneijken]

Same issue here, running version 2.4.4-beta6: Itho I2C connection status: init failed - please power cycle the itho unit -

The issue occurred the first time on version 2.4.3, and did not work on any update since. Power cycles are not helping in this case.

2023-02-08 19:35:46 E: I2C init: QueryDevicetype - failed
2023-02-08 19:35:42 I: SHT3x sensor reset: executed
2023-02-08 11:29:52 E: Error: I2C bus could not be cleared!
2023-02-08 11:29:50 W: Warning: I2C timeout, trying I2C bus reset...
2023-02-04 16:52:06 E: I2C init: QueryDevicetype - failed
2023-02-04 16:52:05 I: SHT3x sensor reset: executed
15213 E: I2C init: QueryDevicetype - failed
9960 I: Hostname: nrg-itho-6804
9789 I: mDNS: started
9630 I: Webserver: started
9419 I: MQTT: connected, System config: 1
8266 I: WiFi: connection successful
2773 E: Unable to set wifi disconnect
1858 I: I2C sniffer capable hardware: no
1634 I: HW rev: 2, FW ver.: 2.4.4-beta6
1333 I: System boot, last reset reason: TG0WDT_SYS_RESET
2023-01-29 19:55:29 E: I2C init: QueryDevicetype - failed
2023-01-29 19:55:27 E: Error: I2C bus could not be cleared!
2023-01-29 19:55:24 W: Warning: I2C timeout, trying I2C bus reset...
2023-01-29 19:55:24 I: Hostname: nrg-itho-6804
2023-01-29 19:55:24 I: mDNS: started
2023-01-29 19:55:23 I: Webserver: started
2023-01-29 19:55:23 I: MQTT: connected, System config: 1
2023-01-29 19:55:22 I: WiFi: connection successful
2023-01-29 19:55:17 E: Unable to set wifi disconnect
2023-01-29 19:55:16 I: I2C sniffer capable hardware: no
2023-01-29 19:55:15 I: HW rev: NON-CVE 2, FW ver.: 2.4.4-beta6
2023-01-29 19:55:15 I: System boot, last reset reason: SDIO_RESET
2023-01-29 21:12:53 I: Reboot requested
2023-01-19 08:14:30 E: Error: I2C bus could not be cleared!
2023-01-19 08:14:27 W: Warning: I2C timeout, trying I2C bus reset...
15204 E: I2C init: QueryDevicetype - failed
10180 I: Hostname: nrg-itho-6804
9772 I: mDNS: started
9553 I: Webserver: started
9347 I: MQTT: connected, System config: 1
8580 I: WiFi: connection successful
2770 E: Unable to set wifi disconnect
1695 I: I2C sniffer capable hardware: no
1507 I: HW rev: 2, FW ver.: 2.4.4-beta6
1272 I: System boot, last reset reason: TG0WDT_SYS_RESET
2023-01-13 19:17:48 E: I2C init: QueryDevicetype - failed
2023-01-13 19:17:44 I: SHT3x sensor reset: executed
2023-01-13 20:22:30 E: I2C init: QueryDevicetype - failed
2023-01-13 20:22:25 I: Hostname: nrg-itho-6804
2023-01-13 20:22:25 I: mDNS: started
2023-01-13 20:22:24 I: Webserver: started
2023-01-13 20:22:24 I: MQTT: connected, System config: 1
2023-01-13 20:22:23 I: WiFi: connection successful
2023-01-13 20:22:18 E: Unable to set wifi disconnect
2023-01-13 20:22:17 I: I2C sniffer capable hardware: no
2023-01-13 20:22:17 I: HW rev: 2, FW ver.: 2.4.4-beta6
2023-01-13 20:22:16 I: System boot, last reset reason: SDIO_RESET
2023-01-13 19:16:10 I: Reboot requested
2023-01-13 17:52:10 E: I2C init: QueryDevicetype - failed
2023-01-13 17:52:04 I: Hostname: nrg-itho-6804
2023-01-13 17:52:04 I: mDNS: started
2023-01-13 17:52:04 I: Webserver: started
2023-01-13 17:52:04 I: MQTT: connected, System config: 1
2023-01-13 17:52:03 I: WiFi: connection successful
2023-01-13 17:51:57 E: Unable to set wifi disconnect
2023-01-13 17:51:56 I: I2C sniffer capable hardware: no
2023-01-13 17:51:56 I: HW rev: 2, FW ver.: 2.4.4-beta6
2023-01-13 17:51:56 I: System boot, last reset reason: SDIO_RESET
2023-01-05 13:25:28 E: I2C init: QueryDevicetype - failed
2023-01-05 13:25:26 I: SHT3x sensor reset: executed
15248 E: I2C init: QueryDevicetype - failed
9871 I: Hostname: nrg-itho-6804
9681 I: mDNS: started
9487 I: Webserver: started
9309 I: MQTT: connected, System config: 1
8358 I: WiFi: connection successful
2859 E: Unable to set wifi disconnect
2067 I: I2C sniffer capable hardware: no
1855 I: HW rev: 2, FW ver.: 2.4.4-beta3
1341 I: System boot, last reset reason: TG0WDT_SYS_RESET
2023-01-05 10:23:14 E: I2C init: QueryDevicetype - failed
2023-01-05 10:23:12 I: SHT3x sensor reset: executed
15162 E: I2C init: QueryDevicetype - failed
9826 I: Hostname: nrg-itho-6804
9467 I: mDNS: started
9241 I: Webserver: started
9031 I: MQTT: connected, System config: 1
8244 I: WiFi: connection successful
3024 E: Unable to set wifi disconnect
1702 I: I2C sniffer capable hardware: no
1510 I: HW rev: 2, FW ver.: 2.4.4-beta3
1259 I: System boot, last reset reason: TG0WDT_SYS_RESET
15206 E: I2C init: QueryDevicetype - failed
9856 I: Hostname: nrg-itho-6804
9505 I: mDNS: started
9279 I: Webserver: started
9073 I: MQTT: connected, System config: 1
8294 I: WiFi: connection successful
3027 E: Unable to set wifi disconnect
1720 I: I2C sniffer capable hardware: no
1530 I: HW rev: 2, FW ver.: 2.4.4-beta3
1279 I: System boot, last reset reason: TG0WDT_SYS_RESET
2023-01-05 11:48:35 E: I2C init: QueryDevicetype - failed
2023-01-05 11:48:33 E: Error: I2C bus could not be cleared!
2023-01-05 11:48:31 W: Warning: I2C timeout, trying I2C bus reset...
2023-01-05 11:48:30 I: Hostname: nrg-itho-6804
2023-01-05 11:48:30 I: mDNS: started
2023-01-05 11:48:30 I: Webserver: started
2023-01-05 11:48:29 I: MQTT: connected, System config: 1
2023-01-05 11:48:29 I: WiFi: connection successful
2023-01-05 11:48:23 E: Unable to set wifi disconnect
2023-01-05 11:48:22 I: I2C sniffer capable hardware: no
2023-01-05 11:48:21 I: HW rev: NON-CVE 2, FW ver.: 2.4.4-beta3
2023-01-05 11:48:21 I: System boot, last reset reason: SDIO_RESET
2023-01-05 10:08:39 I: Reboot requested
2023-01-05 10:08:23 I: Firmware update: nrgitho-hw2-v2.4.4-beta3.bin
2023-01-05 08:21:24 I: I2C init: QueryDevicetype - failed
2023-01-05 08:21:19 I: Setup: done
2023-01-05 08:21:18 I: Hostname: nrg-itho-6804
2023-01-05 08:21:18 I: mDNS: started
2023-01-05 08:21:18 I: Webserver: started
2023-01-05 08:21:18 I: MQTT: connected, System config: 1
2023-01-05 08:21:18 I: Setup: remotes configfile loaded
2023-01-05 08:21:17 I: Setup: Virtual remotes, start ID: 1A,68,04 - No.: 2
2023-01-05 08:21:17 I: IP:[redacted]
2023-01-05 08:21:17 I: Status:WL_CONNECTED
2023-01-05 08:21:17 I: Mode:STA
2023-01-05 08:21:17 I: RSSI:-36dBm
2023-01-05 08:21:16 I: SSID:[redacted]
2023-01-05 08:21:16 I: WiFi info:
2023-01-05 08:21:16 I: WiFi: connection successful
2023-01-05 08:21:10 I: HW rev: 2, FW ver.: 2.4.3
2023-01-05 08:21:10 I: System boot, last reset reason: SDIO_RESET
2023-01-05 09:59:30 I: Reboot requested
2023-01-05 09:18:32 I: Mem free: 111436, Mem low: 83124, Mem block: 44020
2023-01-05 03:18:31 I: Mem free: 112036, Mem low: 83124, Mem block: 44020
2023-01-04 21:18:31 I: Mem free: 111436, Mem low: 83124, Mem block: 44020
2023-01-04 15:18:30 I: Mem free: 112044, Mem low: 83124, Mem block: 44020
2023-01-04 09:18:30 I: Mem free: 112048, Mem low: 83124, Mem block: 44020
2023-01-04 03:18:29 I: Mem free: 112056, Mem low: 83124, Mem block: 44020
2023-01-03 21:18:29 I: Mem free: 112056, Mem low: 83124, Mem block: 44020
2023-01-03 19:43:20 I: HA DISCOVERY: Start publishing MQTT Home Assistant Discovery...
2023-01-03 19:43:17 I: Reconnect WiFi successful
2023-01-03 19:43:10 I: Attempt to reconnect WiFi
2023-01-03 15:21:06 I: HA DISCOVERY: Start publishing MQTT Home Assistant Discovery...

From the I2C debug menu:

origin	start	duration	error	final
QUERY_DEVICE_TYPE	345200832	4528	I2C_ERROR_SDA_LOW	I2C_NOK
QUERY_DEVICE_TYPE	345195829	3	I2C_ERROR_CLEARED_OK	I2C_NOK
QUERY_DEVICE_TYPE	345190826	2		I2C_OK
QUERY_DEVICE_TYPE	345185823	2		I2C_OK
QUERY_DEVICE_TYPE	345180820	2		I2C_OK
QUERY_DEVICE_TYPE	345175817	2		I2C_OK
QUERY_DEVICE_TYPE	345170939	2		I2C_OK
QUERY_DEVICE_TYPE	345170811	2		I2C_OK
QUERY_DEVICE_TYPE	345165807	2		I2C_OK
QUERY_DEVICE_TYPE	345160804	2		I2C_OK
QUERY_DEVICE_TYPE	345155801	2		I2C_OK
QUERY_DEVICE_TYPE	345150779	2		I2C_OK
QUERY_DEVICE_TYPE	345145776	2		I2C_OK
QUERY_DEVICE_TYPE	345140773	2		I2C_OK
QUERY_DEVICE_TYPE	345135770	2		I2C_OK

[arjenhiemstra]

@mvaneijken

Also for you, please follow the instruction posted here earlier:

1. update to the latest beta release (beta6)
2. switch on the i2c safe guard function.
3. Power cycle the unit and monitor what happens

[mvaneijken]

I'm already on beta6 and i2c safe guard is on, but that does not help (also after a reboot).

[arjenhiemstra]

I'm already on beta6 and i2c safe guard is on, but that does not help (also after a reboot).

Sorry, it took me a while to see it but you have the add-on in use already for some time? For the I2C safe guard function to work I needed to implement a I2C sniffer. This only works on add-on from HW rev. 2.5 and up :(

It might be that I will be able to fix these issues without I2C sniffer functionality but how long that will take is unsure.
You can go back to an earlier firmware version (I would advise 2.3.5) is you don;t need any of the new features from later firmware versions. I you need the newer features or you have also issues with 2.3.5 I'm also want to offer the option to replace to add-on for a newer revision.

[mvaneijken]

I'm already on beta6 and i2c safe guard is on, but that does not help (also after a reboot).

Sorry, it took me a while to see it but you have the add-on in use already for some time? For the I2C safe guard function to work I needed to implement a I2C sniffer. This only works on add-on from HW rev. 2.5 and up :(

It might be that I will be able to fix these issues without I2C sniffer functionality but how long that will take is unsure. You can go back to an earlier firmware version (I would advise 2.3.5) is you don;t need any of the new features from later firmware versions. I you need the newer features or you have also issues with 2.3.5 I'm also want to offer the option to replace to add-on for a newer revision.

I was in the understanding that I was having a hw2.5 version. Although I see in the firmware that I'm on ref 2, that is not the same? Nevertheless, I was able to revert back to 2.3.5 successfully, only I'm missing the virtual remotes now.

[arjenhiemstra]

If you need the more recent functionality, I can (instruct or do it for) you how to change the hardware using two wires and add support for the sniffer functionality.

[mvaneijken]

That would be great! I'm able to solder, so if you can give the instructions I can do it myself.

[arjenhiemstra]

This is version 2.4, the i2c pins are encircled in red:

This is version 2.5, the i2c pins are encircled in red, notice that there are 2 times 2 extra pins on the i2c bus. That is all that is different.

Soldered it could look something like this:

The firmware detects the connection of these pins. After soldering you should have i2c sniffer functionality available

[arjenhiemstra]

2.5.0 has been released as new stable release, including fixes for the described issue.

https://github.com/arjenhiemstra/ithowifi/releases/tag/2.5.0

[MartVisser]

Great work! Been running on beta6 for a while without any problems. Just updated to 2.5.0.

[mvaneijken]

This is version 2.4, the i2c pins are encircled in red:

This is version 2.5, the i2c pins are encircled in red, notice that there are 2 times 2 extra pins on the i2c bus. That is all that is different.

Soldered it could look something like this:

The firmware detects the connection of these pins. After soldering you should have i2c sniffer functionality available

I added the mod today and now the addon is working again on v2.5.0. Thanks!

[arjenhiemstra]

2.5.0 has been released as new stable release, including fixes for the described issue.

https://github.com/arjenhiemstra/ithowifi/releases/tag/2.5.0

I've found a serious issue with the fail save firmware update, please do not install 2.5.0 and if you have already, wait with further updates until 2.5.1 comes out.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.