This repository has been archived by the owner on Oct 4, 2021. It is now read-only.
hc3 data measured in ems-esp, not displayed in Home Assistant #715
Labels
question
Further information is requested
Comments
|
It looks like the MQTT does not contain all the heating circuits. Can you check which version you are? Also try and go the telnet console and type For MQTT you'll need to sniff what is being sent. A good tool for that is MQTTExplorer. See https://emsesp.github.io/docs/#/MQTT?id=monitoring-the-queue |
|
I may have to add that the single RC300 controls four circuits
Regarding MQTT, number for publish fails have been zero. Here we go ... and Lastly, how HA sees the connection ...
|
|
I have no experience with ESP devices. One thing I noticed: the device is sluggish at best. Accessing the web interface doesn't work 6/10 times. After connecting, I have to refresh the devices list often with varying results. Putty connects instantly but gives me "network error: software caused connection abort" after a short time. I've read about power issues in another post (with the GB192i) - could this be a problem? |
|
You have a lot of devices and heating-circuits. I think the esp8266 ran out of memory to handle all the values. The low memory causes the connection issues with web and telnet. You can try to set mqtt sending intervall to different values for thermostat/boiler/mixer/solar (maybe 25/26/27/28 sec) to ensure that a message is send out before another device allocates sending memory. The service jack delivers enough power and is safe, power issues are mainly on buspower. |
|
Hi Michael, thanks for the feedback. Will try out the MQTT sequence. From my perspective (as a layman) the mem usage looks ok ... but the uptime doesn't. I connected the device a couple of days ago. That's not the uptime of the current telnet session, is it? |
|
The uptime counts from last processor reset. Reset reason is exception 29 (access to invalide address), which is a result from not enough memory. |
|
Ok, changed to
will check during the day, how the system performs. Good to know that its either web or telnet but not both :-/ |
|
Well, HA still complains ... |
|
@swa72 those HA errors are not caused by the MQTT. It looks like the HA config is wrong. Can you use MQTTExplorer and removed all the entries from /ems-esp and /homeassistant, restart EMS-ESP and watch them load with MQTTExplorer active? |
|
Before going into MQTTExplorer, I checked the following: Removed Mosquitto from HA, removed MQTT integration from HA, rebootet. Added Mosquitto again. Upon adding the integration, one thermostat device is added and it has numerous entities that also refer to hc2 and hc3. I assume https://bbqkees-electronics.nl/wiki/gateway/home-assistant-configuration-heating-circuits.html is only relevant if I have another thermostat, right? If I check the thermostat device and click on "MQTT INFO", I get a list of all entities that receive messages and I think all hc1, hc2 and hc3 are there.
If I then select e.g. "'Thermostat hc3 Control mode' (sensor.thermostat_hc3_control_mode" and show the last ten received messages, I see something like and there is very little hc3 info in there. So I reckon, its the sender ;-) Will try MQTTExplorer tonight ... |
|
I think the json size is to small for 3 heating circuits. |
|
I think that is indeed the issue. The payload is getting cut. And as it doesn't have the |
|
Ok, that info is a bit over my head ;-) Are you saying that each MQTT message cannot handle more than 1k of data and all the stuff that is sent exceeds that 1k? From "errorcode" to "comforttemp: 19" in the above example there are 855 characters (including blanks). So there is a tiny bit more room ;-)
another try at Did I mention that the device takes friggin ages to respond :-/ I'm surprised that I'm the first user with three circuits. Why not split the thermostat message into n pieces (for n circuits)? Anyway, I got MQTTExplorer up and connected to
If I click on I guess it wouldn't make much of a difference upgrading to an ESP32 instead of an ESP8266 (which means sending the stuff back to bbqkees), uh? I don't really care if I pay a couple of EUR more, I just want a reliable system. And I haven't been to the point where I can actually optimize my heating (which is the whole purpose of this exercise). I'm still confused that anytime I telnet into the system, it gives me uptime of less than a day, and now its an 28 and not a 29. Thanks for any help or hints in advance |
|
I'd like to test your setup, will simulate it with the test code to see what is really happening. Could you grab some example telegrams from your thermostat? Go to console and do a Then I can experiment if we can increase the MQTT json buffer sizes or indeed need to split into separate MQTT topics. The stability issues you're facing is because EMS-ESP has many EMS devices loaded, in your case the Mixers. Each device eats memory and the ESP8266 doesn't have a lot. |
|
|
|
|
I hope that helps ... |
|
oops, you have an RC300. Wrong telegrams. Can you do |
|
Ok, here we go ... and and |
|
@MichaelDvP I see three possible fixes for this: The first would be to up the value of The second is to advise using MQTT format 'Single' so each hc is published on its own MQTT topic. Then modify the Home Assistant discovery code to handle this variant. It'll be some extra work since the same will need to be done for the Mixer and the Dallas Sensor, and a new option for HA Discovery like in v3. I'd rather not do this! The third, and easiest, is to spend 5 euros on replacing the ESP8266 with a ESP32 and switching over to v3 ! |
|
Thanks for the analysis. That’s a tough decision;-) I will ask bbqkees to exchange the device and pay the difference/handling fee. Everything else seems like way to much futzing around. |
|
great, moving to ESP32 greatly simplifies things. You can pick up a ESP32 for a few euros and replace the ESP8266 on your gateway yourself. See https://bbqkees-electronics.nl/wiki/gateway/upgrade-the-gateway-to-an-esp32.html |
|
Yupp, I've read that. But I'm not into soldering stuff ;-) Kees offered me a return so I'll rather take the easy route :-) So I think, we can close this issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Question
hc3 data measured in ems-esp, not displayed in Home Assistant
Screenshots
I also get load of errors in the log file of HA. Here are some examples ...
or
or
Device information
Copy-paste here the information as it is outputted by the device. You can get this information from http://ems-esp.local/api?device=system&cmd=info
Running that command I get ...
I run a device from bbqkees that I received a couple of days ago, hooked up directly to the service jack (not external power source) ...
The text was updated successfully, but these errors were encountered: