Thank you for your feedback, I will check the discovery issue. The datatime is only a time value. But internally it uses a Java Calendar object that always contains date and time. So you should format your item to ignore the date. The same goes for the date command.
Can you share an example
You should try "Time [%1$tH:%1$tM]"
@csowada
i tried and is not working properly -
10:03
and showing mm:ss not hh:mm
for Date no results
DateTime vr470_time "Time [%1$tH:%1$tM]" <temperature> (HeatingUnit) {channel="ebus:vrc430:home:15:vrc430_controller_time#time"}
DateTime vr470_date "Date [%1$td.%1$tm.%1$tY]" <temperature> (HeatingUnit) {channel="ebus:vrc430:home:15:vrc430_controller_date#date"}
I need the raw telegram to check this here, but I’n not sure if you can get the telegram via log level trace.
I will enhance the logging for the next release. I will also try to convert the recorder from 1.x binding. It helps a lot to record all received telegrams.
sounds perfect let’s wait for new revision.
By the way did you implement write function for date & time is also?
I see that this is not stablestill same config and look for result :
Regarding the boiler pressure, I can’t get any data on it, while it was working during my experiment with the 1.8 binding version.
Hi,
i have a problem with the new version. When i try to add a thing from the Inbox, I get the ERROR: 409 - Conflict. Any ideas to solve the problem ?
There is a id generation issue in this version. Try to change/complete the id when you add the discovered thing.
Same Problem with an new id. I also test an other PC with an new Installation from openhab. Alpha 12 works on booth Systems without problems
Have you used text based configuration with a thing file? Have you restarted your server?
Anyone else with this issue?
I will move the configuration files to a separate repository. So it is much easier to update the configurations without the binding.
I don’t use the text bassed configuration and restart the Server a few times. In the afternoon i will try it on a Linux System
I had strange issues after reinstalling the last Alpha, The bridge was installed properly but when trying to add manually a Vrc470, I had 2 bridge available to link it to, both having the same id. I believe it’s much an issue of cleaning the things between each try try, and I’m switching a lot from the 1.8 binding to the alpha, I do not see how to collect messages in a csv in the Alpha, which is really great to understand what is properly understood and what is not.
What should be the best way to clean up when removing the alpha version, as well as the 1.8 binding ?
Hi i have install the Ebus Bindung and i found 4 Ebus Standard Things but i see no data. What can i do ? Here the log
2017-11-05 16:19:07.760 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command common.time from 10 to FE …
2017-11-05 16:20:09.495 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command common.time
2017-11-05 16:20:09.499 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command common.time from 10 to FE …
2017-11-05 16:21:10.055 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command common.time
2017-11-05 16:21:10.059 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command common.time from 10 to FE …
2017-11-05 16:22:10.352 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command common.time
2017-11-05 16:22:10.354 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command common.time from 10 to FE …
2017-11-05 16:23:10.723 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command common.time
2017-11-05 16:23:10.726 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command common.time from 10 to FE …
2017-11-05 16:24:11.287 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command common.time
2017-11-05 16:24:11.291 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command common.time from 10 to FE …
2017-11-05 16:25:12.527 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command common.time
2017-11-05 16:25:12.536 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command common.time from 10 to FE …
2017-11-05 16:26:08.137 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command common.time
2017-11-05 16:26:08.144 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command common.time from 10 to FE …
Hi,
I believe that the default is to not poll the data.
So if you edit each channel and set a polling interval (I use 60 seconds for my VRC470 channels and 300 sec for my bai channels) you should get the values reported.
Hi i think i need another Configruation File because the heating unit use the follow csv data files.
08.ehp.csv
15.uih.csv
23.ehp.cc.csv
25.ehp.hwc.csv
50.ehp.mc.csv
Can everybody convert this CSV from John (github) to use the files with open Hab Binding. Thanks so much
Hello @Maddin2017,
The current version doesn’t support that devices. I need help from the community to add more devices, I’m focused on the code at the moment.
Hi Christian,
So I tried to add my json file to support some broadcast messages sent by my VRC470.
2017-11-06 22:00:34;"01";"10";"FE";B5 16;"08";00 34 00 22 06 11 01 17;"CE";;;;;<unknown>
2017-11-06 22:00:54;"01";"10";"FE";B5 16;"03";01 90 06;"E3";;;;;<unknown>
Based on http://ebus-wiki.org/doku.php/ebus/serviceb516, for now my json looks like:
Per your recommandation, I changed the id value to “testvrc470”:
{
"id": "testvrc470",
"vendor": "Vaillant",
"label": "Vaillant VRC 430(f)/470(f)",
"description": "Programming unit Vaillant VRC 430, 430f, 470 and 470f",
"commands":
[
{
"label": "Outside temperature",
"id": "controller.broadcast.temp_outside",
"command": "B5 16",
"broadcast": {
"master": [
{"type": "static", "default": "01"},
{"name":"temp_outside", "type": "data2b", "label": "Outside Temperature", "min": -50, "max": 50, "format":"%.1f°C"}
]
}
},
{
"label": "Outside temperature",
"id": "controller.broadcast.time",
"command": "B5 16",
"broadcast": {
"master": [
{"type": "static", "default": "00"},
{"name":"seconds", "type": "bcd", "label": "seconds", "min": 0, "max": 59, "format":"%.1f°C"},
{"name":"minutes", "type": "bcd", "label": "minutes", "min": 0, "max": 59, "format":"%.1f°C"},
{"name":"hours", "type": "bcd", "label": "hours", "min": 0, "max": 59, "format":"%.1f°C"},
{"name":"day", "type": "bcd", "day": "second", "min": 1, "max": 31, "format":"%.1f°C"},
{"name":"month", "type": "bcd", "month": "second", "min": 1, "max": 12, "format":"%.1f°C"},
{"name":"weekday", "type": "bcd", "weekday": "second", "min": 1, "max": 7, "format":"%.1f°C"},
{"name":"year", "type": "bcd", "label": "year", "min": 0, "max": 99, "format":"%.1f°C"}
]
}
}
]
}
The json is properly loaded, but the log shows regular error like this:
2017-11-07 10:31:08.936 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to FE with command controller.broadcast.temp_outside
2017-11-07 10:31:08.939 [INFO ] [nding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command controller.broadcast.temp_outside from 10 to FE ...
I had the same behavior before changing the id value from vrc430 to testVRC470.