search

csowada / openhab2-addons

Add-ons for openHAB 2.x
Eclipse Public License 2.0
6 stars 2 forks source link

Some telegrams are unresolved #5

Closed Rolli1962 closed 4 years ago

Rolli1962 commented 4 years ago

After update with Openhab 2.5 from ebus-2.4.0.RC7b to ebus-2.5.1-5: 3 telegrams are listed in ebus-unresolved. To compare them the telegrams after the update, and before the update (with additional info of mapping): In addition my exact ebus-version of the log-entries. ´´´ 29.01.2020 21:48 FF 15 B5 24 06 02 00 00 00 3D 00 48 00 08 01 00 3D 00 63 0E 00 00 84 00 29.01.2020 14:10 FF 15 B5 24 06 02 00 00 00 3D 00 48 00 08 01 00 3D 00 63 0E 00 00 84 00 GET > vrc700_general.gen.solar_yield_total

29.01.2020 21:48 FF ED B5 09 03 29 3B 00 0B 00 04 3B 00 90 90 D2 00 29.01.2020 14:11 FF ED B5 09 03 29 3B 00 0B 00 04 3B 00 90 90 D2 00 GET > custom-vms02.YieldCurrentYear

29.01.2020 21:58 FF ED B5 09 03 29 56 00 E4 00 06 56 00 63 0E 00 00 6D 00 29.01.2020 14:11 FF ED B5 09 03 29 56 00 E4 00 06 56 00 63 0E 00 00 6D 00 GET > custom-vms02.YieldTotal

2020-01-29 21:48:27.748 [INFO ] [internal.things.EBusTypeProviderImpl] - Load custom configuration file 'file:///etc/openhab2/vaillant-vms02-configuration.json' ... 2020-01-29 21:48:28.530 [WARN ] [internal.things.EBusTypeProviderImpl] - eBUS command boiler.control.setopdata only contains a setter channel! 2020-01-29 21:48:29.860 [INFO ] [ing.ebus.internal.EBusHandlerFactory] - Use eBUS binding 2.5.1.202001291838 [eBUS core: 1.0.5.202001291834, eBUS configuration: 1.0.5.202001291835] 2020-01-29 21:48:29.934 [INFO ] [ing.ebus.internal.EBusHandlerFactory] - eBUS core -> timestamp 202001291834, commit: #3d1c915, build-no: #null 2020-01-29 21:48:30.008 [INFO ] [ing.ebus.internal.EBusHandlerFactory] - eBUS configuration -> timestamp 202001291835, commit: #3f20d94, build-no: #null

Rolli1962 commented 4 years ago

Additionally I found out: All three configuration try to get the data by vaillant.energy4. Configurated in vaillant-templates.json as: {"name":"energy4", "template": [ {"name": "value", "type": "uchar", "length": 4, "format": "%s kWh"} ]},

With this configuration the telegram is unresolved. Have changed my custom-vms02 configuration to other kind, special without using parameter "length". Than the telegram go to resolved. Have seen other standard-vaillant configuration are using also energy4. I think tey will be ignored also, if activated by an user.

csowada commented 4 years ago

The energy4 template is wrong, the type should be unumber for unsigned number. I'll fix it with the next release.

csowada commented 4 years ago

Fixed in upcoming release