SM100 - no MQTT messages send (sm_data) - 1.8.1b9 #146
Comments
|
definitely a bug somewhere. When you type 'info' do you see 'Solar Module enabled' at the top ? |
|
also do you see the message "Solar Module support enabled." when starting up or after a |
|
Short: yes it appeared Longer: |
|
the MQTT is only updated when the values change, so with the SM module if they are constant nothing will be sent. I did this to save on internet traffic to the MQTT broker. If you think its not needed and we should always publish the values I can remove that check. |
|
Dear @proddy To test if the routine is the reason why nothing appears in mqtt - i can test it with your help - please provide me the necessary steps to do... |
|
I refactored the code a little to separate devices like solar modules from heatpumps. I don't expect it to fix your problem but it'll be easier to trace. The messages come in on the same type so the logic hasn't changed there. Can you test anyway and let me know if you see the SM values in |
|
first impression shows the first 4 values are updated accordingly, the energy values are unknown (once per hour), but i do not get any sm_data topic message via mqtt! All others are send out... Does perhaps the new (for me unknown value) 'Pump working time: 11650 days 20 hours 15 minutes' - the value cannot be true, because the heating was installed less then 5 years ago and it never changes - responsible for the issue? info |
|
update: energy values are updated and again - wrong total energy and no sm_data at all Solar Module stats: |
|
energy total is taken from bytes 11+12 of type 0x28E and divided by 10, so in your example 0x8221 = 33313 = 3331.3 kWH. I think that looks correct? If so it's a rendering problem |
|
as for the pump working time, you should not be even seeing this as its a feature from a Junkers ISM1 solar module. I think the problem is the introduction of the new code for Junkers is confusing the old SM100 implementation that worked in 1.7 (as we wrote in https://github.com/proddy/EMS-ESP/wiki/SM100). Can you leave it running for a while and see if you get any telegrams from type 0x0003 ? Adding @Vuego123 |
|
Regarding #146 (comment) --> issue #147 |
|
i scanned the last 5 minutes - nothing with 0x0003 |
|
After more than 1 hour - no telegram with 0x0003 |
|
ok. I have no idea why you're getting a value for pump working time as your SM100 doesnt support that yet. I'll dig into the code again and run some tests |
|
found the issue and fixed it. can you check again? |
|
Installed: Output after some minutes: |
|
like I said there is no pump working time for SM100. That was left over code for the Junkers that Vuego added. Still no sm_data? ok, let me look into that next |
|
Total energy seems to be correct by now - cool: |
|
mqtt is working for me. Are you sure it says "enabled" in |
|
i entered 'system' then the esp crashed.... Still get mqtt messages from other areas like boiler: The log show mqtt updates send out for: autodetect |
|
entered publish -> seen mqtt topics: but still no sm_data |
|
need to find if the crc checksum is failing. Can you add an extra debug line, in ems-esp.cpp after line #876 so |
|
i doesn't see any debug message up to now; have i to enable something? |
|
I put an additional debug line into the file (line 830) and also nothing - and yes i saved the file and recompiled it! |
|
myDebugLog needs verbose mode. best to use myDebug() instead. but you should see something! |
|
changed and nothing! info shows that the solar modul is enabled but it seems that the routine doesn't run... |
|
interresting: I also see no Thermostat MQTT update - i am not quite sure if that happens often (i have a RC300); info also shows that the thermostat is enabled |
|
i put some debug statements into the code |
|
the publish should run every 2 mins (do a When you do a |
|
Could it be that a "return" in the thermostat routine is responsible that i do not get any update of solar? |
|
Thermostat stats: |
|
in earlier1.8.x that part was solved differently: |
|
Dear @proddy Please adpat the if clause in the code. |
|
OMG! you found the culprit. how silly. I'll fix it right away |
|
Dear @proddy Return temperature: 3276.8 C also tested on Firmware 181b12 |
|
Dear @proddy |
|
Last but not least: Often i have to retry up to four times the upload of a image to the esp via ota. The connection can't be established. I notice that the esp reboot at least one time and also crash dumps... |
|
@proddy |
|
|
to 5.: in both MQTT and telnet |
|
think #5 is resolved now. |
|
Dear @proddy But the mqtt message seems to have wrong values: '''' |
|
Perhaps you should disable them, when no value is present, like you have done for solrr energy... |
|
ok, done in latest build. |
|
Dear @proddy {"wWComfort":"Hot","wWSelTemp":51,"selFlowTemp":5,"selBurnPow":0,"curBurnPow":0,"pumpMod":0,"outdoorTemp":17.6,"wWCurTmp":53.4,"wWCurFlow":0,"curFlowTemp":70.5,"wWActivated":"on","burnGas":"off","heatPmp":"off","fanWork":"off","ignWork":"off","wWCirc":"off","wWHeat":"off","ServiceCode":"0H","ServiceCodeNumber":203} |
|
solved with 1.8.1b14 |
Dear @proddy
dear @Vuego123
i have a problem with the mqtt messages of the SM100 of this version:
I updated from 1.8.1b2 to 1.8.1b9: The SM100 module doesn't send any message to the MQTT broker (test one day!)! You also doesn't see any MQTT message update indications in the log.
I expect SM100 mqtt messages if a value changes like temperature of the collector or bottom temp... I also expect that the hourly updates of the solar eanrnings are send out (like older versions have send out!).
Please check the log below - there is no MQTT update for SM100 visible! At least when the x028E update comes, the new energy values needs to be updated (and yes i expect messages for every change of any sensor of the SM100 too)
(17:53:39.936) SM -> all, type 0x028E telegram: 30 00 FF 00 02 8E 00 00 41 82 00 00 28 36 00 00 82 21 (CRC=6D) #data=12
<--- SM100Energy(0x28E)
Could it be that the routine of the SM100 is a different one from yours @Vuego123 for your configuration? Because i saw other mqtt values in your screentshot than mine in my last issue?
Attachment
The text was updated successfully, but these errors were encountered: