Support for WT32-ETH01 board

[bgcngm]

Successfully tested on WT32-ETH01 board connected to a ROTEX HPSU compact unit.

[swalsh11]

Might be helpful to show people how to connect & Flash the WT32

[swalsh11]

Could pin 33 (RS485) control the relay?

[bgcngm]

I don't think so, but IO2, IO4, IO12, IO14 and IO15 for sure. Note that IO35, IO36 and IO39 can only be used as inputs.

[swalsh11]

Modified the Drawing to use IO2,

[swalsh11]

I do not appear to be able to get OTA updates to Work, , It could be Worthwhile Removing the OTA lines in PlatformIO.ini Until that is resolved.

 ; Uncomment this line to allow for remote upgrade. If name resolution does not work for you, replace with the IP of ESPAltherma
; upload_port = ESPAltherma.local
; Uncomment this line if you want to define the protocol. Autodetected otherwise.
; upload_protocol = espota

[bgcngm]

Why is that? I have my WT32-ETH01 already in production and OTA updates work flawlessly. I suppose you're referring to the ESPOE32 board?

[Alibloke]

OTA updates worked for me after I allowed access between vlans, perhaps that could be your issue?

[bgcngm]

Yes, make sure that the computer where you upload the new OTA is in the same VLAN as the device or allow the traffic to flow back to the computer IP address (assuming you have VLANs and you already allow it from the normal VLAN to IoT VLAN).

[swalsh11]

I have both the poesp32 and wt32, I bought both trying to figure out an ethernet solution, they replace a m5sickc, The issue could be vlan related, due to software on my laptop needed for work, which runs zscaler vlan, I will try the OTA updates with a different laptop, with no vlan.

…

On Thu 22 Feb 2024, 16:27 Bruno Martins, ***@***.***> wrote: Yes, make sure that the computer where you upload the new OTA is in the same VLAN as the device or allow the traffi to flow back to the computer IP address. — Reply to this email directly, view it on GitHub <#399 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP6FYJMOFIH5Y7RMOCBNP4TYU5WW7AVCNFSM6AAAAABDP44QTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJZHAYTAOBYHE> . You are receiving this because you commented.Message ID: ***@***.***>

[swalsh11]

My 10 year old Laptop with no VLAN uploaded the code with no problem, Thanks for the Tip

[ce3a]

@bgcngm thanks a lot for your pull request, works like a charm with my WT32-ETH01.

However, I am don't receive logs via MQTT. I think we need to adopt MQTTSerial::write(). Maybe something like that;

     M5.Lcd.print((const char*) buffer);
 #endif
 #ifndef DISABLE_LOG_MESSAGES
-    if (WiFi.status() == WL_CONNECTED && _client!=nullptr &&_client->connected()){
-        _client->publish(_topic,buffer,size);
+#ifdef WT32_ETH01
+    if (ETH.linkUp()) {
+#else
+    if (WiFi.status() == WL_CONNECTED) {
+#endif
+        if (_client!=nullptr &&_client->connected()){
+            _client->publish(_topic,buffer,size);
+        }
     }
     Serial.write(buffer,size);
 #endif