Question: micro-ebusd, how to use custom config files?

[scabrero]

Hi, how micro-ebusd gets the configuration files?

Here it seems they are bundled into the firmare:

Combined with my own Huffman context compression all of the message definitions of the ebusd-configuration repository can be bundled into the firmware

But there is a command to remove files which suggests they are downloaded from somewhere:

“rm”:
remove a downloaded file or all of them (using “rm /data/*”, needs a reboot to fill them up again)

One way or the other, my main point is how to use custom configuration files.

I have additional message definitions for VWZIO and I am using BASV3 from john30/ebusd-configuration#482.

How can I load my files to micro-ebusd?

[burmistrzak]

@scabrero AFAICT, the CDN endpoint seems to be hard-coded at the moment.

I really hope @john30 publishes the eAS source code someday.
Would be super sad if all these adapters where to become e-waste in case he is no longer able to continue development for whatever reason.

[john30]

this feature is on my list of todos and in the top priority, but it'll take a bit to be implemented

[meierchen006]

Hello John,
By the time this comes with customisable files, most testers will have exceeded their 30-day trial period.
It is questionable whether they will pay again afterwards without knowing what it is and how it works!

[mwrben]

This is great news, thank you.
So for example currently I've got a tweaked csv config file that my adapter is pointed to. How do i get that into the micro-ebusd adapter. Do I have to convert it to a typespec file first so that tsp2ebusd can send it to the adapter?

[john30]

Do I have to convert it to a typespec file first so that tsp2ebusd can send it to the adapter?

yes, see here: https://token.ebusd.eu/messages

[burmistrzak]

@john30 Updated eAS and tried converting my local copy of john30/ebusd-configuration#564...
Unfortunately, the web service returns an error:

connecting micro-ebusd...
preparing for micro-ebusd e**********4
Error: conversion: failed with conversion service returned 400 Bad Request, {"error":"conversion failed: Error: invalid response"}

While I really appreciate the clever engineering that went into this, I must say that I'm not a huge fan of that cloud-binding stuff (and the additional points of failure). Nevertheless I paid 60 bucks because good work deserves compensation. 😊
However, the increasing dependence on closed-source firmware/software is a bit worrisome and IMHO the total opposite of what such a project needs.

Many folks use an eAS precisely because they want to get away from Vaillant's proprietary, cloud-locked software.
If for example micro-ebusd and the conversion tool were open source, I'd probably be able to fix this issue myself and contribute a patch. But sadly, I can't.

All this made me think:

• How do you ensure the web service stays online? And what happens to micro-ebusd adapters if the server is unreachable?
• Are there any contingency/succession plans in the event you suddenly become unable to maintain the project?
• Is the infrastructure protected against malicious updates? And if so, how?
• Lastly, can you guarantee that currently cloud/token-less modes (UART, TCP, etc.) will stay that way?

I think everyone here understands that the backend/firmware development is mostly a one-man show at the moment, but it doesn't have to be this way. There're many knowledgeable people around that would be more than happy to help out. 🤝

[mwrben]

Just to let you know I have successfully uploaded a couple of customised .tsp files into the microebusd adapter and subsequently included on the webservice.
If there is any interest I can write up an account of what I found. It is essentially following John's instructions but there are a couple of details that might catch people out.

[burmistrzak]

@mwrben Please do! Maybe I somehow missed something because I wasn't able to convert john30/ebusd-configuration#564 at the time... 👀

[burmistrzak]

Ok, seems like John has updated the web service in the meantime, but now micro-ebusd is refusing the converted config with -i option:

connecting micro-ebusd...
preparing for micro-ebusd e**********4
conversion: successful, 20965 inline
micro-ebusd reload: 500 Internal Server Error, content too long

Dropping the inline/temporary argument seems to work, but eAS simply isn't loading the custom config:

connecting micro-ebusd...
preparing for micro-ebusd e**********4
conversion: successful, message: OK
micro-ebusd reload: ok

Writing the config to disk with --output produces an empty file. Interesting. 🧐