Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Proddy
@proddy
wwonetime is used to send a single charge to boiler to heat up the warm water (DHW). It's a function found on thermostats like the RC35
@grappa24 sending a payload of {"cmd":"flowtemp",data:55} to topic home/ems-esp/boiler_cmddoesn't work?
grappa24
@grappa24
@proddy no doesn't change anything. I suppose because I control my boiler via "heating curve" the flowtemp is the result of some kind of algorithm and can't be affected manual??? Have to look at my junkers set-up ...
Proddy
@proddy
@grappa24 it may behave differently on Junkers. best to open a telnet session, set logging to verbose and manually try the command and see what happens.
grappa24
@grappa24
thanks, will log with telnet tomorrow
grappa24
@grappa24
hab mal via telnet "boiler flowtemp 66" abgesetzt und geloggt:
Setting boiler flow temperature to 66 C
(02:26:56.040) Thermostat -> UBAMaster, type 0x23, telegram: 90 08 23 00 4F 64 00 (CRC=99) #data=3
(02:26:56.370) Sending write of type 0x1A to 0x08, telegram: 8B 08 1A 00 42 (CRC=12)
(02:26:56.438) UBAMaster -> All, type 0x07, telegram: 88 00 07 00 0B 01 00 00 00 00 00 00 00 00 00 00 00 (CRC=51) #data=13
(02:26:56.620) Sending validate of type 0x1A to 0x08, telegram: 8B 88 1A 00 01 (CRC=35)
-> Write failed. Compared set value 0x42 with received value of 0x4F
-> Write didn't work, retrying (1/2)...
(02:26:56.870) Sending write of type 0x1A to 0x08, telegram: 8B 08 1A 00 42 (CRC=12)
(02:26:57.095) Sending validate of type 0x1A to 0x08, telegram: 8B 88 1A 00 01 (CRC=35)
-> Write failed. Compared set value 0x42 with received value of 0x4F
-> Write didn't work, retrying (2/2)...
(02:26:57.370) Sending write of type 0x1A to 0x08, telegram: 8B 08 1A 00 42 (CRC=12)
(02:26:57.600) UBAMaster -> All, type 0x18, telegram: 88 00 18 00 4F 01 8B 64 00 01 03 20 C0 80 00 02 04 80 00 00 00 FF 00 00 00 CA 00 00 00 (CRC=7C) #data=25
Publishing boiler data via MQTT
(02:26:57.795) Sending validate of type 0x1A to 0x08, telegram: 8B 88 1A 00 01 (CRC=35)
-> Write failed. Compared set value 0x42 with received value of 0x4F
-> Write failed. Giving up, removing from queue
Proddy
@proddy
Looks like the write didn't work. Can you try something simple like boiler wwtemp 40 to see if that works? If the Tx is working then the problem is somewhere else.
grappa24
@grappa24
@proddy "boiler wwtemp 40" worked, the wwtemp was set to 40 for some seconds but then the temp automatically went back to 55 which is the value I selected with the control wheel direcly at my boiler (not at thermostat). Seems to be "hardware specific"
Its o.k. for me, learned a lot today with your help, esp. telnet session is very useful :)
Proddy
@proddy
Ok then we need to figure out why the flowtemp didn’t work. What model boiler do you have?
grappa24
@grappa24
@proddy my boiler is a Junkers Cerapur ZSB 24-5 C 23
Proddy
@proddy
@grappa24 can you create a GitHub issue and we can track changes there.
tim-83
@tim-83
Hello, I'm a beginner and I try to configure EMS_ESP with Home Assistant
So far, everything went fine, but I'm not able to receive correctly MQTT states in HA
I run EMS-ESP v1.9.4 and System Status page shows MQTT as connected and sending correctly data
In HA, I imported yaml files and configured mosquitto as explained in the wiki pages
I can see all devices in HA Developer Tools, but the states are all "unknown" and never updated
Could you please help me to find the problem ?
Proddy
@proddy
Sure. The wiki is based on version 1.9.5 which should be released. Try upgrading to that.
tim-83
@tim-83
image.png
Just upgraded to version 1.9.5b25
Still have the issue
States are still "unknown" in HA.
I receive the MQTT messages when listening via the MQTT developer tools tab
tim-83
@tim-83
image.png
I found the issue!
It was because the Base value in the MQTT Settings of the device was not set (the MQTT topic prefix)
I changed it to "home" and now it works
It is confusing as when the value is empty, there is a grey text in the field (cf screenshot), it is not easy to differentiate with the value entered (both "home")
Proddy
@proddy
@tim-83 glad you found the problem. Yes I'll remove the gray'd out home, it is confusing. When installing EMS-ESP for the first time it should set the mqtt_base to 'home' so strange that it didn't with yours. I'll need to look into that.
tim-83
@tim-83
@proddy First setup was done with the default loaded firmware. I do not remember the version but is was for sure previous to 1.9.4.
Proddy
@proddy
ok
grappa24
@grappa24
access to public mqtt server?
Is it possible to let ems gateway publish to a public mqtt server and subscibe to it from another location?
Proddy
@proddy
@grappa24 in theory yes. It just needs an IP of the public server. However keep in mind most public services use TLS and a certificate which isn't implemented yet (there is an open feature request)
Klaasjan te Voortwis
@voortwis
@proddy First i really like the project and am blown away with the easy of installation and quality of the userinterface.
I just upgraded to 1.9.4 and the new version does no longer see my thermostat as a thermostat: RC30/Moduline 400 (Version:03.01 ProductID:78 DeviceID:0x10)
It detects a MM400 Mixer Module. This has the same ID in the ems_devices.h file (with different type). Maybe it has to do with the removal of the 'thermostat scan and autodetect deep functions' ..?
Happy to test a version that might have a fix or provide more info.
Proddy
@proddy
@voortwis hi there. yes, known issue with the Moduline 400, sorry. But fixed in the latest 1.9.5 dev version a while ago. You can upgrade manually from the github releases page or use the web UI and select the beta version. Let me know how you get on.
Klaasjan te Voortwis
@voortwis
@proddy just upgraded to latest EMS-ESP-1_9_5b30-d1_mini-debug version. It installed properly and have seen the Moduline 400 in the dashboard. Sadly after that the UI failed on me in chrome and firefox. As if the device was in a rebootloop. Managed to upload the 1.9.3 firmware after a couple of tries.
Will wait for final version, If you need info about this issue happy to try again, please tell me what info you need. Will be ont earlier than tomorrow.
Proddy
@proddy
oh dear. so there are some stability issues in 1.9.5 which I'm working on fixing. But it shouldn't be this bad. Wait a day or two and try again.
grappa24
@grappa24
could you please provide me the telnet command to activate wWOneTime in 1.9.4 ?
Proddy
@proddy
@grappa24 it's in 1.9.5 -boiler wwonetime <on | off>
grappa24
@grappa24
@proddy but not yet useable via mqtt?
Martin Sezman
@martinSezman_twitter
Hi @proddy, I have question about Boiler temperature value.
for my boiler Buderus GB072 in b29 - Boiler temperature: 17.1 C = Warm Water current temperature: 17.1 C
now in b32 - Boiler temperature: ? C . it was an intended change?
Proddy
@proddy
@martinSezman_twitter yes, I made a change to support Worcester/Bosch boilers where the boiler temp is in a different location. I can fix it. But need an example 0x18 and 0x19 telegrams from you - if possible
Martin Sezman
@martinSezman_twitter
telegrams from my ems bus:
(20:06:19) 08 0B 18 00 15 00 DF 64 00 01 11 20 40 80 00 00 AC 80 00 00 00 FF 30 59 00 CC 00 00 00

(20:07:18) 08 0B 19 00 00 0A 80 00 80 00 00 00 00 00 00 06 21 02 11 29 00 00 00 02 0F C0 00 05 E6 00 DD

(20:08:01) 08 00 19 00 00 0A 80 00 80 00 00 00 00 00 00 06 21 02 11 29 00 00 00 02 0F C0 00 05 E6 00 DB

Proddy
@proddy
Thanks
Martin Sezman
@martinSezman_twitter
(20:09:22) 08 00 18 00 05 00 E6 00 00 00 10 00 40 80 00 00 AC 80 00 00 00 FF 30 48 00 CB 00 00 00
(20:09:23) 08 00 18 00 05 00 E4 00 00 00 10 00 40 80 00 00 AB 80 00 00 00 FF 30 48 00 CB 00 00 00
(20:09:26) 08 00 18 00 05 00 E6 00 00 00 10 00 40 80 00 00 AC 80 00 00 00 FF 30 48 00 CB 00 00 00
no problem. let me if you need anything more
Proddy
@proddy
boiler temp around 17.2 degrees C ?
Martin Sezman
@martinSezman_twitter
yes.
Proddy
@proddy
Ok. Made a new build
Martin Sezman
@martinSezman_twitter
I see. Boiler temperature works again. Thanks.
John Melati
@jcmelati
Hey there! It seems that my device is recognizing "RC10/Moduline 100" thermostat as "Junkers M100" mixer
doesnt seem right... any idea how to fix this? thanks
I tried to setup my system again and also the thermostat data seems gone.. I saw it was removed but I didnt understand why or how to make it work again.. it used to work on a previous version but I avoid downgrading things
John Melati
@jcmelati
I "kinda" solved deleting the Junkers entry from the code, compiling it and uploading
it fixed for me but I guess other people might face the same issue
both are code 79
Proddy
@proddy
Ah, this problem again where product ids are not unique. I’ll look into it. Thanks for reporting.