-
-
Notifications
You must be signed in to change notification settings - Fork 97
receive multiple WW requests 08 0B 33 00 #75
Comments
I've reproduced this, its a bug. I'm looking into it - thanks for reporting |
I had it once, but can't reproduce it anymore. Have you been able too? |
yes, after a boiler and ESP restart still there. I get also some "read retries"...
|
|
if I look at the CRC I don't see any duplicates so those messages coming in are all uniquely different in one way or form. It is however strange that so many messages are sent. |
I downgraded my setup to 1.5.4 and with this version, there are no dupes. .ini
Log:
|
I still can't reproduce. Would you mind testing again with the latest dev build, then |
log r
set test_mode off
|
wow, that's clear as day. I'll have a think of what is happening. Other than adding a delay to the loop nothing much has changed in the UART code. |
hi,
log v
|
I've seen it happen once, but can't reproduce it anymore. I think I'll hook up an Arduino and use bbqkees original code to see if I'm going mad or not. |
edit: since 1.5.4 |
so since 1.5.6 you're seeing double messages? That really helps in narrowing down the root cause. |
i verified it and since V1.5.5 I see the doubled messages. |
ok, so it worked in 1.5.4 but 1.5.5 shows the double messages. I'll compare the sources in a while. Did you compile both from source using the latest Arduino core libraries or take the firmware? I'm trying to rule out any external factors like library changes. |
I compiled all versions new with the latest libs or sdk. There is one exception, because V1.5.4 must be compiled with Arduinojson 5. I also compiled each version with 1.8.0 and 2.5.0 but there was no difference ... I guess :) |
can you test for duplicates with the last dev? I added a line to remove the contents of the last Rx package just in case its overwriting |
wow, seems to be fixed with latest dev version (https://github.com/proddy/EMS-ESP/tree/303e3adc81a1e610c80c7641879caaaf2091ca87).
|
phew, glad that worked! Yes I change verbose logging to also show the milliseconds for more accurate timings. I also made a change to remove the strange 0x00 telegrams. If you have time could you do one last check? Then I think I'll push this version 1.6.0 to the master. |
... last check done and the 0x00 messages are gone! 👍
|
phew! |
Dear proddy,
not sure if it is normal, but I saw a probably untypical behaviour for UBAParameterWW(0x33) and UBATotalUptimeMessage(0x14) message requests.
It seems that I receive four messages for only one WW requests.
Is this normal?
Version 1.6.0_b
update: it seems that can effect almost all messages
The text was updated successfully, but these errors were encountered: