search

absalom-muc / MHI-AC-Ctrl

Reads and writes data (e.g. power, mode, fan status etc.) from/to a Mitsubishi Heavy Industries (MHI) air conditioner (AC) via SPI controlled by MQTT
MIT License
279 stars 62 forks source link

Update from 2.02 to 2.8 doesn't work #177

Closed coyote1 closed 10 months ago

coyote1 commented 10 months ago

Hi, have been using your project since 2020 without any problems with currently SW version 2.02. Now I wanted to upgrade the software version to the latest version 2.8. So I flashed a new Wemos D1 Mini and put it on the PCB. Unfortunately it doesn't work and I don't know why. Is the SW V2.8 compatible with the "old" PCB?

According to the log, it looks to me like the ESP keeps rebooting, doesn't it? I have flashed the Wemos with 80MHz and also with 160MHz, but nothing has changed. Maybe you can help me, otherwise I'll just stick with the "old" version, it works without any problems :-)

Name of my AC: SRK50-ZM-S Used MHI-AC-Ctrl HW: PCB from Dec 2019 (no HW Version Number on PCB) Used MHI-AC-Ctrl SW: 2.02

Log:

17:31:57.024 -> Starting MHI-AC-Ctrl v2.8
17:31:57.024 -> CPU frequency[Hz]=160000000
17:31:57.024 -> ESP.getCoreVersion()=3.1.2
17:31:57.024 -> ESP.getSdkVersion()=2.2.2-dev(38a443e)
17:31:57.316 -> ESP.checkFlashCRC()=1
17:31:57.625 -> Measure frequency for SCK, MOSI and MISO pin
17:31:58.630 -> SCK frequency=4299Hz (expected: >3000Hz) o.k.
17:31:58.630 -> MOSI frequency=590Hz (expected: <SCK frequency) o.k.
17:31:58.630 -> MISO frequency=0Hz (expected: ~0Hz) o.k.
17:31:58.630 -> OTA Ready
17:31:58.630 -> setupWiFi: Start async scanNetworks
17:31:58.630 -> WIFI_CONNECT_SCANNING
17:31:58.697 -> mhi_ac_ctrl_core.loop error: -2
17:31:58.768 -> mhi_ac_ctrl_core.loop error: -2
17:31:58.844 -> mhi_ac_ctrl_core.loop error: -2
17:31:58.915 -> mhi_ac_ctrl_core.loop error: -2
17:31:58.992 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.062 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.134 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.207 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.277 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.380 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.454 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.525 -> mhi_ac_ctrl_core.loop error: -4
17:31:59.600 -> mhi_ac_ctrl_core.loop error: -4
17:31:59.671 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.744 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.819 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.930 -> mhi_ac_ctrl_core.loop error: -2
17:31:59.967 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.075 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.148 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.194 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.304 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.373 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.449 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.517 -> mhi_ac_ctrl_core.loop error: -4
17:32:00.593 -> mhi_ac_ctrl_core.loop error: -4
17:32:00.668 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.741 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.816 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.883 -> mhi_ac_ctrl_core.loop error: -2
17:32:00.988 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.062 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.138 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.209 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.281 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.349 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.422 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.496 -> mhi_ac_ctrl_core.loop error: -2
17:32:01.567 -> mhi_ac_ctrl_core.loop error: -4
17:32:01.675 -> mhi_ac_ctrl_core.loop error: -4
17:32:01.744 -> mhandleWiFiScanResult(): 10 access points available
17:32:01.744 ->  1              TP-Link_84FE  1 -93dBm 98:DA:C4:68:3E:31 secured 08
17:32:01.744 ->  2                CoyoteGast  1 -81dBm 1E:E8:29:A7:77:0D secured 04
17:32:01.744 ->  3                 CoyoteIoT  1 -82dBm 22:E8:29:A7:77:0D secured 04
17:32:01.744 ->  4                CoyoteGast  1 -95dBm 7E:8A:20:2D:D9:4C secured 04
17:32:01.782 ->  5                 CoyoteIoT  1 -90dBm 82:8A:20:2D:D9:4C secured 04
17:32:01.782 ->  6                 CoyoteIoT  6 -83dBm 86:8A:20:27:54:75 secured 04
17:32:01.782 ->  7                CoyoteGast  6 -93dBm 4A:D9:E7:FA:DB:16 secured 04
17:32:01.782 ->  8                 CoyoteIoT  6 -91dBm 4E:D9:E7:FA:DB:16 secured 04
17:32:01.782 ->  9             Vodafone-87A0 11 -91dBm 2C:3A:FD:6B:84:01 secured 04
17:32:01.782 -> 10                    Coyote  1 -80dBm 18:E8:29:A7:77:0D secured 04
17:32:01.782 -> current BSSID: FF:FF:FF:FF:FF:FF, strongest BSSID: 22:E8:29:A7:77:0D
17:32:01.819 -> Connecting from bssid:FF:FF:FF:FF:FF:FF to bssid:22:E8:29:A7:77:0D, channel:1
17:32:01.819 -> WIFI_CONNECT_ONGOING
17:32:01.819 -> hi_ac_ctrl_core.loop error: -2
17:32:01.890 -> mhi_ac_ctrl_core.loop error: -2
17:32:02.870 -> mhi_ac_ctrl_core.loop error: -2
17:32:02.923 -> mhi_ac_ctrl_core.loop error: -2
17:32:02.993 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.061 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.140 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.207 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.277 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.352 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.424 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.495 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.574 -> mhi_ac_ctrl_core.loop error: -4
17:32:03.677 -> mhi_ac_ctrl_core.loop error: -4
17:32:03.750 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.826 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.907 -> mhi_ac_ctrl_core.loop error: -2
17:32:03.976 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.044 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.122 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.192 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.272 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.340 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.412 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.488 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.564 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.640 -> mhi_ac_ctrl_core.loop error: -4
17:32:04.750 -> mhi_ac_ctrl_core.loop error: -4
17:32:04.817 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.893 -> mhi_ac_ctrl_core.loop error: -2
17:32:04.962 -> mhi_ac_ctrl_core.loop error: -2
17:32:05.031 -> mhi_ac_ctrl_core.loop error: -2
17:32:05.104 -> mhi_ac_ctrl_core.loop error: -2
17:32:05.142 ->  connected to CoyoteIoT, IP address: 192.168.59.110 (-83dBm)
17:32:05.142 -> WIFI_CONNECT_OK
17:32:05.214 -> mhi_ac_ctrl_core.loop error: -2
17:32:05.214 -> MQTTreconnect(): Attempting MQTT connection (MQTTclient.state=-1), WiFi.status()=3 ...
17:32:05.214 ->  connected
17:32:05.214 -> MQTTclient.connected=1
17:32:05.214 -> status=64 topic=connected payload=1
17:32:05.214 -> 
17:32:05.214 -> --------------- CUT HERE FOR EXCEPTION DECODER ---------------
17:32:05.249 -> 
17:32:05.249 -> Exception (3):
17:32:05.249 -> epc1=0x40219716 epc2=0x00000000 epc3=0x00000000 excvaddr=0x4024a3ec depc=0x00000000
17:32:05.249 -> 
17:32:05.249 -> >>>stack>>>
17:32:05.249 -> 
17:32:05.249 -> ctx: cont
17:32:05.249 -> sp: 3ffffd30 end: 3fffffd0 offset: 0150
17:32:05.249 -> 3ffffe80:  4024a3ec 65696c63 632e746e 00000000  
17:32:05.249 -> 3ffffe90:  4024a3f0 4024a3ec 00000040 40203050  
17:32:05.249 -> 3ffffea0:  5f49484d 746e6957 61677265 6e657472  
17:32:05.249 -> 3ffffeb0:  6f632f32 63656e6e 00646574 00000000  
17:32:05.249 -> 3ffffec0:  00000000 00000000 00000000 00000000  
17:32:05.284 -> 3ffffed0:  00000000 00000000 00000000 00000000  
17:32:05.284 -> 3ffffee0:  00000000 00000000 00000000 00000000  
17:32:05.284 -> 3ffffef0:  00000000 00000000 00000000 00000000  
17:32:05.284 -> 3fffff00:  00000000 3ffeea70 3ffeec34 00000000  
17:32:05.284 -> 3fffff10:  3ffeeadc 3ffeea70 3ffeec34 402031c9  
17:32:05.284 -> 3fffff20:  00000001 3ffe893c 5f6c7274 65726f63  
17:32:05.284 -> 3fffff30:  6f6f6c2e 72652070 3a726f72 0a322d20  
17:32:05.284 -> 3fffff40:  00000000 0000208e a4dd2f1a 0025a4ee  
17:32:05.284 -> 3fffff50:  3ffeec34 00000000 0000000c 40100664  
17:32:05.327 -> 3fffff60:  3fffffa0 3fffff70 00000008 402012b1  
17:32:05.327 -> 3fffff70:  402456c6 3ffeea00 3ffeea08 00000001  
17:32:05.327 -> 3fffff80:  ffffffff 0000208f e4dd2f1a 0025a660  
17:32:05.327 -> 3fffff90:  3ffef81c 402039b4 3fffffa0 3ffeee10 <
17:32:05.327 -> 3fffffa0:  3ffe85f0 3ffeea08 3ffeea18 40202850  
17:32:05.327 -> 3fffffb0:  3fffdad0 00000000 3ffeede4 4020e398  
17:32:05.327 -> 3fffffc0:  feefeffe feefeffe 3fffdab0 40101261  
17:32:05.327 -> <<<stack<<<
17:32:05.327 -> 
17:32:05.327 -> --------------- CUT HERE FOR EXCEPTION DECODER ---------------
17:32:05.360 -> 
17:32:05.360 ->  ets Jan  8 2013,rst cause:2, boot mode:(3,6)
17:32:05.360 -> 
17:32:05.360 -> load 0x4010f000, len 3424, room 16 
17:32:05.360 -> tail 0
17:32:05.360 -> chksum 0x2e
17:32:05.360 -> load 0x3fff20b8, len 40, room 8 
17:32:05.360 -> tail 0
17:32:05.360 -> chksum 0x2b
17:32:05.360 -> csum 0x2b
17:32:05.360 -> v00052b50
17:32:05.360 -> ~ld
17:32:05.428 -> ⸮⸮n⸮r⸮⸮n|⸮l⸮l`bbrl⸮nb⸮nl`⸮rl⸮l⸮⸮
17:32:05.537 -> Starting MHI-AC-Ctrl v2.8
17:32:05.537 -> CPU frequency[Hz]=160000000
17:32:05.537 -> ESP.getCoreVersion()=3.1.2
17:32:05.537 -> ESP.getSdkVersion()=2.2.2-dev(38a443e)
17:32:05.824 -> ESP.checkFlashCRC()=1
17:32:06.147 -> Measure frequency for SCK, MOSI and MISO pin
17:32:07.127 -> SCK frequency=4280Hz (expected: >3000Hz) o.k.
17:32:07.127 -> MOSI frequency=587Hz (expected: <SCK frequency) o.k.
17:32:07.127 -> MISO frequency=0Hz (expected: ~0Hz) o.k.
17:32:07.127 -> OTA Ready
17:32:07.127 -> setupWiFi: Start async scanNetworks
17:32:07.160 -> WIFI_CONNECT_SCANNING
17:32:07.194 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.268 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.340 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.416 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.487 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.561 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.633 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.743 -> mhi_ac_ctrl_core.loop error: -4
17:32:07.817 -> mhi_ac_ctrl_core.loop error: -4
17:32:07.889 -> mhi_ac_ctrl_core.loop error: -2
17:32:07.964 -> mhi_ac_ctrl_core.loop error: -2
Henk50V commented 10 months ago

Have you seen this in the readme? I had the same issue ⚠️[MQTT client library] ..... don't use v2.8.0, use v2.7.0

coyote1 commented 10 months ago

Sure. I know that, because I use this Project since 2020. But I will check the PubSub client version and flash it again.

glsf91 commented 10 months ago

Indeed you esp is crashing a few times. A lot have changed in between :-) If it is not PubSub client version you can also try:

Also check if you also have a lot "mhi_ac_ctrl_core.loop error: -2" in your previous used version

Henk50V commented 10 months ago

I see in your log it is near wifi connection, in my case, after months of stable working, without network changes, connected goes nearly all the time to 0. Didn't connect to serial to debug. But you can give it a try to change parameter:

define WiFI_SEARCHStrongestAP false

For me, this solved the problem.

coyote1 commented 10 months ago

No luck. I tried all options: Without frame size, StrongestAP false, both frequencies. MQTT connection is there, I can set Power ON, but it doesn't work.

I also tried ESPHome Version, all Datapoints are there, but I can't control MHI. Here are serial log and pictures from ioBroker. Maybe hardware layout is different?!

17:26:33.987 -> Starting MHI-AC-Ctrl v2.8
17:26:33.987 -> CPU frequency[Hz]=80000000
17:26:33.987 -> ESP.getCoreVersion()=3.1.2
17:26:33.987 -> ESP.getSdkVersion()=2.2.2-dev(38a443e)
17:26:34.527 -> ESP.checkFlashCRC()=1
17:26:34.820 -> Measure frequency for SCK, MOSI and MISO pin
17:26:35.824 -> SCK frequency=4320Hz (expected: >3000Hz) o.k.
17:26:35.824 -> MOSI frequency=577Hz (expected: <SCK frequency) o.k.
17:26:35.824 -> MISO frequency=0Hz (expected: ~0Hz) o.k.
17:26:35.861 -> OTA Ready
17:26:35.861 -> setupWiFi: Start async scanNetworks
17:26:35.861 -> WIFI_CONNECT_SCANNING
17:26:35.899 -> mhi_ac_ctrl_core.loop error: -2
17:26:35.969 -> mhi_ac_ctrl_core.loop error: -2
17:26:36.040 -> mhi_ac_ctrl_core.loop error: -2
17:26:46.112 -> mhi_ac_ctrl_core.loop error: -2
17:26:46.183 -> mhi_ac_ctrl_core.loop error: -2
17:26:46.259 -> mhi_ac_ctrl_core.loop error: -2
17:26:46.333 -> mhi_ac_ctrl_core.loop error: -2
17:26:46.333 ->  connected to CoyoteIoT, IP address: 192.168.59.110 (-84dBm)
17:26:46.333 -> WIFI_CONNECT_OK
17:26:46.406 -> mhi_ac_ctrl_core.loop error: -2
17:26:46.406 -> MQTTreconnect(): Attempting MQTT connection (MQTTclient.state=-1), WiFi.status()=3 ...
17:26:47.590 ->  connected
17:26:47.590 -> MQTTclient.connected=1
17:26:47.590 -> status=64 topic=connected payload=1
17:26:47.590 -> status=64 topic=Version payload=2.8
17:26:47.624 -> status=64 topic=RSSI payload=-84
17:26:47.624 -> status=64 topic=WIFI_LOST payload=0
17:26:47.624 -> status=64 topic=MQTT_LOST payload=0
17:26:47.624 -> status=64 topic=WIFI_BSSID payload=4E:D9:E7:FA:DB:16
17:26:47.624 -> MQTTreconnect(): 10 access points available
17:26:47.624 -> status=64 topic=fSCK payload=4320
17:26:47.624 -> status=64 topic=fMOSI payload=577
17:26:47.624 -> status=64 topic=fMISO payload=0
17:26:47.700 -> mhi_ac_ctrl_core.loop error: -2
17:26:47.773 -> mhi_ac_ctrl_core.loop error: -2
17:26:47.848 -> mhi_ac_ctrl_core.loop error: -2
17:26:47.925 -> mhi_ac_ctrl_core.loop error: -2
17:26:48.001 -> mhi_ac_ctrl_core.loop error: -4
17:29:18.030 -> mhi_ac_ctrl_core.loop error: -2
17:29:18.105 -> mhi_ac_ctrl_core.loop error: -2
17:29:18.105 -> MQTT_subscribe_callback, topic=MHI_Wintergarten2/set/Power payload=On payload_length=2
17:29:18.105 -> status=64 topic=cmd_received payload=o.k.
17:29:18.177 -> mhi_ac_ctrl_core.loop error: -2
17:29:18.283 -> mhi_ac_ctrl_core.loop error: -4
17:29:18.353 -> mhi_ac_ctrl_core.loop error: -4
17:29:18.428 -> mhi_ac_ctrl_core.loop error: -2
17:31:24.095 -> mhi_ac_ctrl_core.loop error: -2
17:31:24.170 -> mhi_ac_ctrl_core.loop error: -2
17:31:24.242 -> mhi_ac_ctrl_core.loop error: -2
17:31:24.242 -> MQTT_subscribe_callback, topic=MHI_Wintergarten2/set/Power payload=Off payload_length=3
17:31:24.242 -> status=64 topic=cmd_received payload=o.k.
17:31:24.314 -> mhi_ac_ctrl_core.loop error: -2
17:31:24.388 -> mhi_ac_ctrl_core.loop error: -2
17:31:24.463 -> mhi_ac_ctrl_core.loop error: -2
17:31:24.534 -> mhi_ac_ctrl_core.loop error: -2

SCR-20240111-olr

glsf91 commented 10 months ago

It is not crashing anymore :-) Looks like there is no good communication with the AC because after startup it should publish almost all topics in about 20-40 sec. Or did you remove some of the logging? Give version 2.6 a try because between 2.6 and 2.8 communication with AC was also changed a little bit. And put freq on 160Mhz.

coyote1 commented 10 months ago

Yes, I have removed some loop errors in the log so that it is shorter. I will test the 2.6, maybe it will work. It's no problem, the 2.02 works without any problems. Just thought I'd upgrade to the latest version. It's strange that the ESPHome version doesn't work either. I can also send commands via iobroker and it says command ok

glsf91 commented 10 months ago

It's strange that the ESPHome version doesn't work either.

That is not strange because it uses the same core files (which are doing the communication with the AC).

coyote1 commented 10 months ago

@glsf91 v2.6 works fine

glsf91 commented 10 months ago

@glsf91 v2.6 works fine That is nice. Do you still have a lot of mhi_ac_ctrl_core.loop errors with v2.6 ?

coyote1 commented 10 months ago

I would say it is limited :-)

23:06:04.249 -> setupWiFi2:12 access points available
23:06:04.249 -> current BSSID: 22:E8:29:A7:77:0D, strongest BSSID: 4E:D9:E7:FA:DB:16
23:06:06.911 -> status=135 topic=THI-R1 payload=15
23:06:08.788 -> mhi_ac_ctrl_core.loop error: -2
23:06:42.821 -> mhi_ac_ctrl_core.loop error: -2
23:07:05.947 -> mhi_ac_ctrl_core.loop error: -2
23:07:06.607 -> mhi_ac_ctrl_core.loop error: -2
23:07:09.203 -> status=135 topic=THI-R1 payload=14
23:07:33.816 -> mhi_ac_ctrl_core.loop error: -2
23:07:40.148 -> status=135 topic=THI-R1 payload=15
23:07:51.015 -> mhi_ac_ctrl_core.loop error: -2
23:07:51.840 -> mhi_ac_ctrl_core.loop error: -2
23:07:54.890 -> mhi_ac_ctrl_core.loop error: -2
23:08:11.312 -> status=135 topic=THI-R1 payload=14

So I will probably stick with v2.6. Let's see if I can get the ESPHome version to work with the v2.6 core files.

glsf91 commented 10 months ago

I think the communication with you AC is a little bit critical for some reason. I have almost never a mhi_ac_ctrl_core.loop error. I also think the change in v2.7R3 (change sending MISO with faster refresh of data every 20s) will be the cause of the problem for you.

If you want you can first try v2.7R2 (https://github.com/absalom-muc/MHI-AC-Ctrl/tree/7814a9d9942fcb288c5473e5fe2ec8b4d8efc8da) which should also work. And I expect if you try v2.7R3 (https://github.com/absalom-muc/MHI-AC-Ctrl/tree/e9bccf4e47f0a615186739b23c69d6fbadbe3cea) it won't work anymore.

If this is the case we can also try v2.8 again with a very little change to see if this solves the problem. If you want of course.

coyote1 commented 10 months ago

Don't ask me why, but now it's suddenly working.

2.7R2 flashed -> works 2.7R3 flashed -> works 2.8 flashed, works now too

The only thing that was different now was that I restarted the laptop and flashed the ESP when it was plugged directly onto the board and connected to the air conditioning.

Perhaps I will now test the ESPHome version.

Log:

14:22:43.752 -> status=137 topic=THI-R3 payload=14
14:22:44.662 -> status=134 topic=IU-FANSPEED payload=0
14:22:45.573 -> status=139 topic=TOTAL-IU-RUN payload=200
14:22:46.508 -> status=132 topic=OUTDOOR payload=6.00
14:22:47.433 -> status=133 topic=THO-R1 payload=-4
14:22:48.352 -> status=141 topic=COMP payload=0.00
14:22:49.300 -> status=143 topic=TD payload=<=30
14:22:50.215 -> status=142 topic=CT payload=0.00
14:22:50.994 -> WIFI_CONNECT_TIMEOUT
14:22:51.098 -> setupWiFi: Start async scanNetworks
14:22:51.098 -> WIFI_CONNECT_SCANNING
14:22:52.836 -> status=144 topic=TDSH payload=1
14:22:53.826 -> handleWiFiScanResult(): 10 access points available
14:22:53.826 ->  1              TP-Link_84FE  1 -89dBm 98:DA:C4:68:3E:31 secured 08
14:22:53.826 ->  2                    Coyote  1 -77dBm 18:E8:29:A7:77:0D secured 04
14:22:53.826 ->  3                CoyoteGast  1 -74dBm 1E:E8:29:A7:77:0D secured 04
14:22:53.826 ->  4                 CoyoteIoT  1 -75dBm 22:E8:29:A7:77:0D secured 04
14:22:53.826 ->  5                CoyoteGast  1 -89dBm 7E:8A:20:2D:D9:4C secured 04
14:22:53.826 ->  6                 CoyoteIoT  1 -93dBm 82:8A:20:2D:D9:4C secured 04
14:22:53.994 ->  7                    Coyote  6 -83dBm 78:8A:20:27:54:75 secured 04
14:22:53.994 ->  8                 CoyoteIoT  6 -83dBm 86:8A:20:27:54:75 secured 04
14:22:53.994 ->  9                CoyoteGast  6 -83dBm 82:8A:20:27:54:75 secured 04
14:22:53.994 -> 10             Vodafone-87A0 11 -93dBm 2C:3A:FD:6B:84:01 secured 04
14:22:53.994 -> current BSSID: 22:E8:29:A7:77:0D, strongest BSSID: 22:E8:29:A7:77:0D
14:22:53.994 -> Connecting from bssid:22:E8:29:A7:77:0D to bssid:22:E8:29:A7:77:0D, channel:1
14:22:53.994 -> WIFI_CONNECT_ONGOING
14:22:53.994 -> status=145 topic=PROTECTION-NO payload=0
14:22:56.957 -> status=140 topic=TOTAL-COMP-RUN payload=300
14:22:58.002 -> status=147 topic=OU-EEV1 payload=250
14:23:01.139 ->  connected to CoyoteIoT, IP address: 192.168.59.110 (-81dBm)
14:23:01.139 -> WIFI_CONNECT_OK
14:23:01.290 -> MQTTreconnect(): Attempting MQTT connection (MQTTclient.state=-1), WiFi.status()=3 ...
14:23:01.290 ->  connected
14:23:01.290 -> MQTTclient.connected=1
14:23:01.290 -> status=64 topic=connected payload=1
14:23:01.290 -> status=64 topic=Version payload=2.8
14:23:01.290 -> status=64 topic=RSSI payload=-81
14:23:01.290 -> status=64 topic=WIFI_LOST payload=0
14:23:01.290 -> status=64 topic=MQTT_LOST payload=0
14:23:01.290 -> status=64 topic=WIFI_BSSID payload=22:E8:29:A7:77:0D
14:23:01.290 -> MQTTreconnect(): 10 access points available
14:23:01.290 -> status=64 topic=fSCK payload=4231
14:23:01.290 -> status=64 topic=fMOSI payload=552
14:23:01.290 -> status=64 topic=fMISO payload=0
14:23:01.392 -> status=65 topic=Mode payload=Cool
14:23:01.392 -> power_status: off; received status_power: 0
14:23:01.392 -> status=64 topic=Power payload=Off
14:23:01.392 -> status=66 topic=Fan payload=Auto
14:23:01.392 -> status=67 topic=Vanes payload=?
14:23:01.392 -> status=71 topic=Tsetpoint payload=22.0
14:23:01.392 -> status=72 topic=Errorcode payload=0
14:23:01.450 -> status=135 topic=THI-R1 payload=15
14:23:02.292 -> status=136 topic=THI-R2 payload=39
14:23:03.194 -> status=137 topic=THI-R3 payload=14
14:23:04.133 -> status=134 topic=IU-FANSPEED payload=0
14:23:05.067 -> status=139 topic=TOTAL-IU-RUN payload=200
14:23:06.027 -> status=132 topic=OUTDOOR payload=6.25
14:23:06.899 -> status=133 topic=THO-R1 payload=-4
14:23:07.841 -> status=141 topic=COMP payload=0.00
14:23:08.749 -> status=143 topic=TD payload=<=30
14:23:09.689 -> status=142 topic=CT payload=0.00
14:23:12.221 -> status=144 topic=TDSH payload=1
14:23:13.220 -> status=145 topic=PROTECTION-NO payload=0
14:23:14.256 -> status=138 topic=OU-FANSPEED payload=0
14:23:15.321 -> status=146 topic=DEFROST payload=Off
14:23:16.337 -> status=147 topic=OU-EEV1 payload=250
14:23:17.063 -> status=128 topic=Mode payload=Cool
14:23:17.354 -> status=140 topic=TOTAL-COMP-RUN payload=300
14:23:17.981 -> status=130 topic=Tsetpoint payload=22.0
14:23:18.895 -> status=131 topic=RETURN-AIR payload=18.25
14:23:24.467 -> status=132 topic=OUTDOOR payload=6.00
14:23:25.399 -> status=133 topic=THO-R1 payload=-4
14:23:34.664 -> MQTT_subscribe_callback, topic=MHI_Wintergarten4/set/Power payload=On payload_length=2
14:23:34.664 -> status=64 topic=cmd_received payload=o.k.
14:23:34.865 -> power_status: off; received status_power: 1
14:23:34.865 -> status=64 topic=Power payload=On
14:23:36.764 -> status=148 topic=unknown payload=4306
14:23:36.764 -> Unknown operating data, MOSI_frame[DB9]=210 MOSI_frame[D10]=16
14:23:37.783 -> status=147 topic=OU-EEV1 payload=0
14:23:38.683 -> status=135 topic=THI-R1 payload=15
14:23:38.818 -> status=148 topic=unknown payload=4306
14:23:38.818 -> Unknown operating data, MOSI_frame[DB9]=210 MOSI_frame[D10]=16
14:23:40.701 -> status=137 topic=THI-R3 payload=14
14:23:41.597 -> MQTT_subscribe_callback, topic=MHI_Wintergarten4/set/Power payload=Off payload_length=3
14:23:41.655 -> status=64 topic=cmd_received payload=o.k.
14:23:41.770 -> power_status: on; received status_power: 0
14:23:41.770 -> status=64 topic=Power payload=Off
14:23:41.863 -> status=148 topic=unknown payload=4306
14:23:41.863 -> Unknown operating data, MOSI_frame[DB9]=210 MOSI_frame[D10]=16
14:23:44.500 -> status=133 topic=THO-R1 payload=-4
14:23:52.023 -> status=148 topic=unknown payload=4306
14:23:52.023 -> Unknown operating data, MOSI_frame[DB9]=210 MOSI_frame[D10]=16
14:23:54.067 -> status=147 topic=OU-EEV1 payload=470
14:23:57.544 -> status=135 topic=THI-R1 payload=15
14:23:58.271 -> status=138 topic=OU-FANSPEED payload=4
14:23:59.394 -> status=137 topic=THI-R3 payload=14
14:24:02.292 -> status=144 topic=TDSH payload=0
14:24:05.893 -> status=142 topic=CT payload=0.27
14:24:07.291 -> status=148 topic=unknown payload=4306
14:24:07.291 -> Unknown operating data, MOSI_frame[DB9]=210 MOSI_frame[D10]=16
14:24:08.312 -> status=144 topic=TDSH payload=1
14:24:09.099 -> mhi_ac_ctrl_core.loop error: -1
14:24:21.622 -> status=133 topic=THO-R1 payload=-4
14:24:45.028 -> status=144 topic=TDSH payload=1
14:24:53.154 -> status=138 topic=OU-FANSPEED payload=0
14:25:12.510 -> status=136 topic=THI-R2 payload=38
14:25:13.517 -> status=144 topic=TDSH payload=0
14:25:17.121 -> status=133 topic=THO-R1 payload=-4
14:25:41.035 -> status=144 topic=TDSH payload=0
glsf91 commented 10 months ago

That is looking very good. Almost no mhi_ac_ctrl_core.loop errors. Sometimes reflashing will help indeed. Sometimes I also flash first a zeroed bin file to clear the complete flash memory when I have strange behaviour.

You even can try the extended framesize if you want to get 3dauto and L/R vanes.

coyote1 commented 10 months ago

Yes, I had tried that. I had flashed the ESP several times, but always had the same problem. I also always selected "flash all contents".

Another thing I saw was that I didn't comment out the extended frame size, I just set it to false. Maybe that was my problem! I will test further tomorrow and report back.

glsf91 commented 10 months ago

@coyote1 Any update or can we close this one ?

coyote1 commented 10 months ago

Yes, we can close it. All three Aircons updated to 2.8 👍