Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 29 2019 00:42
    tomww starred john30/ebusd
  • Jan 27 2019 12:41
    MoellerDi starred john30/ebusd
  • Jan 27 2019 09:13

    john30 on master

    updated (compare)

  • Jan 27 2019 09:03
    john30 closed #258
  • Jan 27 2019 09:03
    john30 commented #258
  • Jan 27 2019 09:02
    john30 labeled #257
  • Jan 27 2019 09:02
    john30 commented #257
  • Jan 27 2019 09:00
    john30 closed #256
  • Jan 27 2019 09:00

    john30 on master

    fixed escaping with quote or dq… (compare)

  • Jan 27 2019 08:59
    john30 labeled #256
  • Jan 24 2019 19:26
    lukicsl edited #258
  • Jan 24 2019 19:25
    lukicsl opened #258
  • Jan 23 2019 23:26
    fluppie edited #257
  • Jan 23 2019 23:20
    fluppie opened #257
  • Jan 23 2019 10:43
    memtew opened #256
  • Jan 19 2019 16:05
    akraxx starred john30/ebusd
  • Jan 17 2019 05:52
    john30 commented #254
  • Jan 16 2019 18:24
    andr2000 commented #254
  • Jan 16 2019 15:39
    emeins starred john30/ebusd
  • Jan 16 2019 09:10
    danielkucera commented #252
Szymon Gładysz
@komw
Ok, few hours later I fount that this 06 means the length of following data, and I don't need to insert it to config line because ebusctl automaticli add the length of data
Would be nice to add it to documentation ;)
I prepare some additional tips to ebusd documentation and I put it as pull request later
Szymon Gładysz
@komw
Hm, another question. I'm getting 2 message types from my boiler one is 70fe207309c3000017060a130101 where interesting data is a c3000017, and another message 70fe207309000000000000000001 which is useless for me
how to write a template for it ? I can inly rely that last part of my message won't change: 060a130101 but I cannot see an option to specify on template config an constant "ending" of message
my template looks: r,boiler,overwritten_until,Overwritten until time,70,fe,2073,,overwritten_until,m,UIN;VTM,,,,,,,,,,,,,,,,,,,,,,, but in that way, ebusd watch only first message from bus, and it uses this with only zeros
Do i need to use conditions ?
John
@john30
looking for a constant value at the end of a message is not supported. does the "c3" identify the message? If so, you can add this as discriminator as described in the wiki
Szymon Gładysz
@komw
Not really :( The message ID is 2073, then 2bytes of length, and c3000017 means 2 variables c300 and 0017 The only constant values are in the beggining 70fe207309 and at the end 060a130101
Szymon Gładysz
@komw
So it won't be possible to read this values via ebusd ?
John
@john30
not without major code changes
Szymon Gładysz
@komw
What a pity. Many of other values I've collected, and probably I'll send a pull request with it
But from another hand it will be hard to integrate it with ebusd, because Ariston Bus BridgeNet doesn't response toaeBUS identification messages :/
John
@john30
thats pretty easy. you can just switch off the "--scanconfig" and then ebusd will just read every CSV file from the "--configpath=..."
Szymon Gładysz
@komw
Indeed, I'm doing in that way, but I'd like to prepare a configuration which can be added to ebusd project. Unfortunately, perhaps it won't be possible, because ebusd can't check that it is a ariston heater. Maybe could be possible checking the Master/slaves address, because Ariston protocol uses different master/slaves addresses than Valiant producent. Eg. Heater uses a 37/3c address, thermostat uses a 7f/84, and also there is master with address 70, which probably is also another address of thermostat
John
@john30
thats not unique enough and would also mean weird changes to ebusd source. another option would be to pass some pre-scan information to ebusd to make it force using e.g. a certain manufacturer. but that also has to be developed first
Szymon Gładysz
@komw
Hm, I have a strange errors with my ebus adapter. I have and new PCB v2.2 but I'm waiting for the parts, so currently I'm using a v2.0 version
I'm using a base PCB + extension PCB (without attached wemos) and and external wemos connected to my base PCB
In my debug log I see a lots of erros like:
notify request: ERR: read timeout
poll boiler heating_temp_return failed: ERR: read timeout
ERR: read timeout during receive response, switching to skip
ERR: read timeout during receive command CRC, switching to skip
ERR: arbitration lost during ready, retry
And now strange part
If I have attached a extension PCB (only PCB, without wemos, so it only has a blinking leds)
I can send an messages to bus, and my thermostat, boiler receive it
When I detach extension PCB, my boiler/thermostat doesn't receive my messages
I'm gettin errors like 2019-10-14 23:03:54.980 [bus debug] notify request: ERR: read timeout 2019-10-14 23:03:54.980 [bus error] send to fe: ERR: read timeout, retry 2019-10-14 23:03:55.069 [bus debug] notify request: ERR: read timeout
what do you thing guys, what is going on?
John
@john30
youo need to have the LEDs connected, especially when detaching the extension from the base. Other than that you could expermient increasing the device latency with ebusd options since sending the data over WIFI usually imposes some delay
Szymon Gładysz
@komw
It is quite interesting how the LED could have an impact to latency ?
Also, with extension board connected I faced many errors like 2019-10-15 07:18:52.262 [bus error] poll boiler heating_temp_out failed: ERR: SYN received 2019-10-15 07:21:58.289 [bus error] poll boiler heating_temp_out failed: ERR: read timeout 2019-10-15 07:32:49.244 [bus error] poll boiler heating_temp_out failed: ERR: read timeout 2019-10-15 07:52:58.829 [bus error] poll boiler heating_temp_out failed: ERR: arbitration lost 2019-10-15 08:04:38.026 [bus error] signal lost 2019-10-15 08:09:30.032 [bus error] poll boiler boiler_pressure failed: ERR: wrong symbol received 2019-10-15 08:12:52.419 [bus error] send to fe: ERR: arbitration lost, retry 2019-10-15 08:22:25.062 [bus error] poll boiler heating_temp_out failed: ERR: wrong symbol received 2019-10-15 08:23:27.094 [bus error] poll boiler boiler_pressure failed: ERR: wrong symbol received
I've tried to change latency/receivetimeout options but without any success
Szymon Gładysz
@komw
Perhaps my problems is because my adapter and wemos response to slow, It is possible to make it faster? I'm using newest ebusd and esp-ebus. It will be better if I'll use a direct USB->serial adapter and connect it directly to my server?
John
@john30
sure, to avoid WiFI issues, a direct UART connection will always be better
Bloodoff
@Bloodoff
Hi, I have issues with ebusd: http query to /data/bai/FlowTemp?exact&verbose&maxage=20&required - don't update the values, and counter "messages" in global section not changing a value. Ebus copieled from latest sources, and manual update with ebusctl works perfect (but messages counter still freez at value 210). Any ideas?
Maddin2020
@Maddin2020
Hello ist der chatroom noch aktiv
die Fehlermeldungen von meiner Vaillant Heizung bekomme noch nicht ausgelesen wenn ich diese auslesen möchte schreibt er immer ERR: Time out wie kann ich das beheben
John
@john30
counter "messages" is just counting the defined messages in the loaded CSVs, so don't expect that to change unless you add more definitions
wenn da err timeout kommt, heißt das dass der slave nicht darauf antwortet. könnte höchstens noch mit deinem adapter zusammenhängen
Bloodoff
@Bloodoff
ok, thanks. Does EBUSD automatically poll data from heater?
Web API show that timestamp of data not changing
John
@john30
you can make it do so by setting the poll priority for those messages either in your copy of the config CSVs or by using the read command through the TCP port
Bloodoff
@Bloodoff
ok, I'll see
violant
@violant
Could you compile ebusd for latest raspbian buster
John
@john30
you can use the stretch images as well
tremichl
@tremichl
Hi John, have attached interface board directly to raspi it seems to be working fine, can get values but sometimes get errors like that "[bus error] send to 15: ERR: arbitration lost, retry" tried to increase latency but no effect. Are there other parameters to deal with?
John
@john30
arbitration losses are quite normal on a multi-master bus, nothing to worry about
Jean-Louis Dupond
@dupondje_twitter
Seems quite silent here :)