-
|
Hi, I have Neopool running and working on 14.4.1. Can read data, and issue commands via MQTT, even on web UI everything is visible. Flashing back 14.4.1, everything starts to work again. My chip is: Seeed Studio XIAO ESP32S3 Any idea what went wrong? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 12 replies
-
|
Did you make sure to do a new custom build with the feature, |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I build all firmwares from scratch yesterday. All have: Still 14.4.1 works, and 14.5 and up no. :/ |
Beta Was this translation helpful? Give feedback.
-
|
Maybe you can take the time to find out the commit that is causing the crash. |
Beta Was this translation helpful? Give feedback.
-
From December 24 (release of working 14.4.1) till now, there was no commit to Neopool logic - https://github.com/arendst/Tasmota/commits/master/tasmota/tasmota_xsns_sensor/xsns_83_neopool.ino other commits are really hard to investigate :/ |
Beta Was this translation helpful? Give feedback.
-
|
version 15 same problem. anybody with working neopool on version 15? |
Beta Was this translation helpful? Give feedback.
-
|
First step was to outline compile problems. Next I have build firmware with DEBUG_TASMOTA_SENSOR enabled In log I see: @curzon01 - do you have working Neopool? |
Beta Was this translation helpful? Give feedback.
-
|
I'm currently see no issue with Tasmota >14.1.
|
Beta Was this translation helpful? Give feedback.
-
|
tested 14.5, 14.6, 15.0, 15.0.1 and tasmota master branch custom compile - no version works |
Beta Was this translation helpful? Give feedback.
-
|
yes, tested binary from repo above - not working :/ |
Beta Was this translation helpful? Give feedback.
-
|
14.1 is ok up to 14.4.1 Yes assignments are visible and configured. Everything is working ok on 14.4.1 when upgraded to 14.5 not working, when downgrading to 14.4.1 it is working again. |
Beta Was this translation helpful? Give feedback.
-
|
Pls verify GPIO assignment in Template (if you use it within Module) or Module configuration. Is the GPIO assignment in 14.4.1/14.1 absolutly the same as if you use 14.5? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, both version look like that: Template configured with command: |
Beta Was this translation helpful? Give feedback.
-
This could have something to do with changes regarding chip type, as there were no changes to Neopool between 14.4.1 and 14.5. I can test this next week, but I don't have an ESP32S3 at the moment. |
Beta Was this translation helpful? Give feedback.
-
|
I have just compiled 14.4.1 with DEBUG_TASMOTA_SENSOR if it helps - result 15:18:18.402 MQT: stat/SmartPool/RESULT = {"NAME":"MaxPool","GPIO":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,7008,6976,0,0,0,0],"FLAG":0,"BASE":1} Version 15 - result 10:42:42.733 NEO: NeopoolCheckChanges() false |
Beta Was this translation helpful? Give feedback.
-
|
may be but pls be patient until I have access to a |
Beta Was this translation helpful? Give feedback.
-
|
No problem, 14.4.1 is working fine. |
Beta Was this translation helpful? Give feedback.
-
|
Found the reason: You are using XIAO ESP32S3 GPIO43 (Tx) as RS485-Rx and GPIO44 (Rx) as RS485-Tx. This is no longer possible with the changes in Tasmota Arduino Core 3.1.1.250203 based on IDF 5.3.2.250120, which were committed in 427db230f. To fix the problem, use the XIAO ESP32S3 GPIO43 (Tx) as RS485-Tx and GPIO44 (Rx) as RS485-Rx as designed (see also XIAO ESP32S3 Sense Pin List):
|
Beta Was this translation helpful? Give feedback.
-
|
Sorry to correct myself: After a while this configuration get's data but garbadge so it seems on XIAO ESP32S3 the Rx/Tx port get's unusable since the Core/IDF changes. Good news: It works perfectly on any other port - I'm using currently GPIO5 (D4) as "NeoPool Rx" and GPIO6 (D5) as "NeoPool Tx" without any more issues. |
Beta Was this translation helpful? Give feedback.
-
|
Great! I dont know how you found out in all those changelogs, but this was indeed the root cause. Thanks!!! |
Beta Was this translation helpful? Give feedback.
Sorry to correct myself: After a while this configuration get's data but garbadge so it seems on XIAO ESP32S3 the Rx/Tx port get's unusable since the Core/IDF changes.
Good news: It works perfectly on any other port - I'm using currently GPIO5 (D4) as "NeoPool Rx" and GPIO6 (D5) as "NeoPool Tx" without any more issues.