ems-esp adapter is requesting data for "unknown device"

[harvey637]

Hi, after updateing to ems-esp v3.7.0-dev0 (2023-10-09 around 16:00) this error is logged in ems-esp:

the times correspond to the times of the ems-esp adapter in my iobroker installation, e.g when stopping no errors, restarting errors start again at the times of the polling od data. No error with initial data (/thermostat, /boiler, /system)

I dont see the wrong api call, please help me with settings to log the error (ems-esp or ems-esp-iobroker adapter)

[harvey637]

it looks to me,, that the adapter is requesting 7 api calls per polling cycle of which 1 fails :-(

thermostats, boiler ... receive updated datapoint, e.g boiler/ubauptime or thermostat/date.

in adapter config only emsp-esp gateway with poling 120 active, no km200, statistics or heatdemand ...

[tp1de]

3.7.0 is not supported yet. Haven't tested. But have you restarted the iobroker adapter?

[harvey637]

Hi, thank you for the quick answer. YES Adapter was restarted. All the relevant Infos (Boiler, thermostat, ... ) look like they are received, so no big problem.

10.09.2023 17:47:43 Thomas @.***>:

3.7.0 is not supported yet. Haven't tested. But have you restarted the iobroker adapter?

— Reply to this email directly, view it on GitHub[https://github.com/tp1de/ioBroker.ems-esp/issues/34#issuecomment-1712847377], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ACNPTCQY2QPCXNDBREYBIW3XZXOJ5ANCNFSM6AAAAAA4SHZ4DQ]. You are receiving this because you authored the thread.[Verfolgungsbild][https://github.com/notifications/beacon/ACNPTCTHHJTQOFXTF2UJWADXZXOJ5A5CNFSM6AAAAAA4SHZ4DSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTGC75BC.gif]

[tp1de]

Do you have 2 thermostats? Please post http://ems-esp/api/system

[harvey637]

Yes, in a way. The system ist a Bosch heatpump, where the rc300 ist build inside. A room Thermostat rc100h ist external. This second Thermostat supplies temp and humidity for dewpoint calculation, as the Bosch can also be a cooling system. Will send API/System soon.--Diese Nachricht wurde von meinem Android Mobiltelefon mit WEB.DE Mail gesendet.Am 10.09.23, 18:31 schrieb Thomas @.***>:

Do you have 2 thermostats? Please post http://ems-esp/api/system —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[harvey637]

`

  |   -- | -- System Info |   version | "3.7.0-dev.0" platform | "ESP32" uptime | "000+01:56:45.473" uptime (seconds) | 7005 free mem | 119 max alloc | 47 free app | 440 reset reason | "Software reset CPU / Software reset CPU" Network Info |   network | "WiFi" hostname | "ems-esp" RSSI | -36 IPv4 address | "192.168.23.95/255.255.255.0" IPv4 gateway | "192.168.23.1" IPv4 nameserver | "253.0.0.0" static ip config | false enable IPv6 | false low bandwidth | false disable sleep | false enable MDNS | true enable CORS | false AP provision mode | "disconnected" AP security | "wpa2" AP ssid | "ems-esp" NTP Info |   NTP status | "connected" enabled | true server | "192.168.23.1" tz label | "Europe/Amsterdam" OTA Info |   enabled | true port | 8266 MQTT Info |   MQTT status | "disconnected" enabled | false client id | "ems-esp" keep alive | 60 clean session | false entity format | 0 base | "ems-esp" discovery prefix | "homeassistant" discovery type | 0 nested format | 1 ha enabled | false mqtt qos | 0 mqtt retain | false publish time heartbeat | 60 publish time boiler | 30 publish time thermostat | 10 publish time solar | 60 publish time mixer | 60 publish time other | 60 publish time sensor | 30 publish single | false publish2command | false send response | false Syslog Info |   enabled | false Sensor Info | {} API Info |   API calls | 781 API fails | 55 Bus Info |   bus status | "connected" bus protocol | "HT3" bus telegrams received (rx) | 23852 bus reads (tx) | 4589 bus writes (tx) | 0 bus incomplete telegrams | 3 bus reads failed | 26 bus writes failed | 0 bus rx line quality | 100 bus tx line quality | 100 Settings |   board profile | "CUSTOM" locale | "de" tx mode | 2 ems bus id | 11 shower timer | false shower alert | false phy type | 0 rx gpio | 4 tx gpio | 2 dallas gpio | 0 pbutton gpio | 0 led gpio | 0 hide led | false notoken api | false readonly mode | false fahrenheit | false dallas parasite | false bool format | 4 bool dashboard | 1 enum format | 2 analog enabled | false telnet enabled | false max web log buffer | 75 web log buffer | 51 Devices |   0 |   type | "boiler" name | "Enviline/Compress 6000AW/Hybrid 3000-7000iAW/SupraEco/Geo 5xx/WLW196i/WSW196i" device id | "0x08" product id | 172 version | "01.16" entities | 62 handlers received | "0xBF 0xC2 0xD1 0xE3 0xE4 0xE5 0xE9 0x0494 0x0495 0x048F" handlers fetched | "0x14 0xE6 0xEA 0x048D 0x048A 0x04A2 0x0485 0x0486 0x0492 0x0488 0x0484 0x048B 0x0491 0x0499 0x049C 0x049D" handlers pending | "0x10 0x11 0x15 0x1C 0x18 0x19 0x1A 0x35 0x16 0x33 0x34 0x26 0x2A" handlers ignored | "0x049F 0x04A0 0x04A3 0xF9 0xF6 0xF7" 1 |   type | "thermostat" name | "RC300/RC310/Moduline 3000/1010H/CW400/Sense II/HPC410" device id | "0x10" product id | 158 version | "13.07" entities | 22 handlers received | "0x06 0x02BA 0x02BB 0x02BC 0x02BD 0x02BE 0x02BF 0x02C0 0x031D 0x0267" handlers fetched | "0x02A5 0x02B9 0x02AF 0x029B 0x0471 0x02CC 0x0467 0x0291 0x0292 0x0293 0x0294 0x02F5 0x023A 0x0240 0xBB 0x023E" handlers pending | "0xA3 0xA2 0x12 0x13 0x02A6 0x02B0 0x029C 0x0472 0x02A7 0x02B1 0x029D 0x0473 0x02A8 0x02B2 0x029E 0x0474 0x02A9 0x02B3 0x029F 0x0475 0x02AA 0x02B4 0x02A0 0x0476 0x02AB 0x02B5 0x02A1 0x0477 0x02AC 0x02B6 0x02A2 0x0478 0x02CE 0x0468 0x02D0 0x0469 0x02D2 0x046A 0x031B 0x031E" handlers ignored | "0xF9 0xE7 0x02E0 0x02EA 0xBF" 2 |   type | "thermostat" name | "RC100H" device id | "0x38" product id | 200 version | "40.07" entities | 3 handlers received | "0x042B 0x047B" handlers fetched | "0x0273" handlers ignored | "0xBF" 3 |   type | "gateway" name | "KM200/MB LAN 2" device id | "0x48" product id | 189 version | "04.08" entities | 0

`

[tp1de]

Was this working before with 2 thermostats? Something must have changed in response to http://ems-esp/api/thermostat. Could you have a look what is different between 3.6 and 3.7 to response?

[harvey637]

yes, both thermostats wer working and still are! see: ...

this is exactly as before, also all the data from the "boiler" are correct. I will try to go back in emsp-esp to provide screenshots .... But I guess that there is no problem. Why? I also have some scripts in raspberrynmatic aside from the iobroker adapter, and the work and produce no error (log in the ems-esp). So my Idea is, that one if the 7 api calls from the iobroker-adapter are unanswered, but it is not the /boiler, /thermostat, /system ...

[harvey637]

I think I found something:

19:41:49.331557 IP ems-esp.fritz.box.http > ioBroker-RasPi.fritz.box.33526: Flags [S.], seq 414663796, ack 2198309510, win 5744, options [mss 1436], length 0
19:41:49.331634 IP ioBroker-RasPi.fritz.box.33526 > ems-esp.fritz.box.http: Flags [.], ack 1, win 64240, length 0
19:41:49.331934 IP ioBroker-RasPi.fritz.box.33526 > ems-esp.fritz.box.http: Flags [P.], seq 1:63, ack 1, win 64240, length 62: HTTP: GET /api/custom HTTP/1.1
19:41:49.343097 IP ems-esp.fritz.box.http > ioBroker-RasPi.fritz.box.33526: Flags [P.], seq 1:171, ack 63, win 5682, length 170: HTTP: HTTP/1.1 400 Bad Request
19:41:49.343168 IP ioBroker-RasPi.fritz.box.33526 > ems-esp.fritz.box.http: Flags [.], ack 171, win 64070, length 0
19:41:49.344447 IP ioBroker-RasPi.fritz.box.33526 > ems-esp.fritz.box.http: Flags [F.], seq 63, ack 171, win 64070, length 0
19:41:49.348329 IP ems-esp.fritz.box.http > ioBroker-RasPi.fritz.box.33526: Flags [F.], seq 171, ack 64, win 5681, length 0

looks like the /api/custom causing the trouble:

[harvey637]

I dont know weather the the response to /api/custom changed or only the logging in the ems-esp is more active but now I am logging with tcpdump the communication between iobroker and ems-esp (with specail grep ...)

`19:53:48.187518 IP ioBroker-RasPi.fritz.box.33850 > ems-esp.fritz.box.http: Flags [P.], seq 1:63, ack 1, win 64240, length 62: HTTP: GET /api/system HTTP/1.1 19:53:48.210892 IP ems-esp.fritz.box.http > ioBroker-RasPi.fritz.box.33850: Flags [.], seq 1:1437, ack 63, win 5682, length 1436: HTTP: HTTP/1.1 200 OK 19:53:48.397662 IP ioBroker-RasPi.fritz.box.33866 > ems-esp.fritz.box.http: Flags [P.], seq 1:63, ack 1, win 64240, length 62: HTTP: GET /api/boiler HTTP/1.1 19:53:48.629740 IP ems-esp.fritz.box.http > ioBroker-RasPi.fritz.box.33866: Flags [P.], seq 1:1199, ack 63, win 5682, length 1198: HTTP: HTTP/1.1 200 OK 19:53:48.636404 IP ioBroker-RasPi.fritz.box.33866 > ems-esp.fritz.box.http: Flags [.], ack 1200, win 63494, length 0

19:53:48.801765 IP ioBroker-RasPi.fritz.box.33878 > ems-esp.fritz.box.http: Flags [P.], seq 1:67, ack 1, win 64240, length 66: HTTP: GET /api/thermostat HTTP/1.1 19:53:48.890730 IP ems-esp.fritz.box.http > ioBroker-RasPi.fritz.box.33878: Flags [P.], seq 1:596, ack 67, win 5678, length 595: HTTP: HTTP/1.1 200 OK 19:53:49.109008 IP ioBroker-RasPi.fritz.box.33892 > ems-esp.fritz.box.http: Flags [P.], seq 1:67, ack 1, win 64240, length 66: HTTP: GET /api/thermostat HTTP/1.1 19:53:49.230849 IP ems-esp.fritz.box.http > ioBroker-RasPi.fritz.box.33892: Flags [P.], seq 1:596, ack 67, win 5678, length 595: HTTP: HTTP/1.1 200 OK 19:53:49.518769 IP ioBroker-RasPi.fritz.box.33902 > ems-esp.fritz.box.http: Flags [P.], seq 1:63, ack 1, win 64240, length 62: HTTP: GET /api/custom HTTP/1.1 19:53:49.529852 IP ems-esp.fritz.box.http > ioBroker-RasPi.fritz.box.33902: Flags [P.], seq 1:171, ack 63, win 5682, length 170: HTTP: HTTP/1.1 400 Bad Request 19:55:48.204966 IP ioBroker-RasPi.fritz.box.60724 > ems-esp.fritz.box.http: Flags [P.], seq 1:63, ack 1, win 64240, length 62: HTTP: GET /api/system HTTP/1.1 19:55:48.228026 IP ems-esp.fritz.box.http > ioBroker-RasPi.fritz.box.60724: Flags [.], seq 1:1437, ack 63, win 5682, length 1436: HTTP: HTTP/1.1 200 OK 19:55:48.416503 IP ioBroker-RasPi.fritz.box.60740 > ems-esp.fritz.box.http: Flags [P.], seq 1:63, ack 1, win 64240, length 62: HTTP: GET /api/boiler HTTP/1.1 19:55:48.635131 IP ems-esp.fritz.box.http > ioBroker-RasPi.fritz.box.60740: Flags [P.], seq 1:1199, ack 63, win 5682, length 1198: HTTP: HTTP/1.1 200 OK 19:55:48.644009 IP ioBroker-RasPi.fritz.box.60740 > ems-esp.fritz.box.http: Flags [.], ack 1200, win 63494, length 0 19:55:48.816595 IP ioBroker-RasPi.fritz.box.60746 > ems-esp.fritz.box.http: Flags [P.], seq 1:67, ack 1, win 64240, length 66: HTTP: GET /api/thermostat HTTP/1.1 19:55:48.905527 IP ems-esp.fritz.box.http > ioBroker-RasPi.fritz.box.60746: Flags [P.], seq 1:596, ack 67, win 5678, length 595: HTTP: HTTP/1.1 200 OK `

[harvey637]

easier in graphic mode:

see the two successfull /thermostat requests, also successfull /boiler and /system, problem with /custom ...

[harvey637]

see https://emsesp.github.io/docs/Commands/#http there is no /api/custom ?!?!?!?

[tp1de]

Thanks for input. I added the integration of custom entities from esp. Was this adapter version working with 3.6 without errors?

[harvey637]

hmmmm, at least I do some quick testing after every ems-esp update and dont remember error entries in the ems-esp log. I am more interested in "newer" findings of entities of my heatpump, as I am still missing e.g. the temperatures for activatiing the cooling mode ( If found the setting "summermode" equals the temperature where the heating starts, sadly no good wording). Also I would "like" to have decimals with the power consumption (possibly not published by bosch) or somethin about the control of the auxillary heater. may be in some future :-)

Possibly the integration of custom entities (or custom naming of devices ...) is still a bit ongoing and we expect some success in future.

by now I can live with this minor problem (only in the log :-), data is coming correctly. I will keep you informed about findings with next ems-esp version. have a nice (rest of) weekend! ciao Harvey

[tp1de]

Errors in log was due to polling custom entities from ems-esp. I introduced a config parameter in new version2.4.1.

[harvey637]

perfect, no more errors in ems-esp! (may be that the ems-esp should also be more friendly to possibly correct request with answering "none configured" instead of logging this as error, will ask for that in ems-esp)

ciao Harvey

[proddy]

see https://emsesp.github.io/docs/Commands/#http there is no /api/custom ?!?!?!?

I'll update the EMS-ESP docs this weekend. Also will look at suppressing the error in the logs.

[tp1de]

@proddy best solution would be to include custom elements in api/system similar to sensors to be able to identify the existence of these elements.

[harvey637]

yes, agreed! I dont have sensors (are part of my vdmot-valve solution, which is near the in/out temperatures of the heating). So it is this empty "sensors {}" entry in /api/system? Having something like "custom {}" might be handy if more people use custom entries ... not yet played with it :-)

Or have a valid "device" like boiler, thermostat ... system for "custom entities" answering with {}/empty without error.

Thank You Harvey

[proddy]

added http://<hostname>/api/custom/ to the EMS-ESP docs. It doesn't make sense to me to show this in /api/system