Messages

Each firmware version of micro-ebusd comes with the message definitions as of ebusd-configuration, usually on the most recent commit unless otherwise noted in the Changelog.

In order to use custom messages definitions, micro-ebusd can be fed with these by using the eBUS TypeSpec library and definitions like those in ebusd-configuration.

The key for that is an online conversion webservice used by the tsp2ebusd script of the eBUS TypeSpec library.

The steps for having this are as follows:

  1. clone ebusd-configuration
  2. install npm packages using npm i
  3. edit a .tsp file as needed
  4. convert and upload it to micro-ebusd using e.g. npx --package=@ebusd/ebus-typespec tsp2ebusd -- -m <IP-address> -i <sourcefile.tsp>

If all is valid, the conversion process logs something like this:

connecting micro-ebusd...
preparing for micro-ebusd xxxxxxxxxxxx
conversion: successful, NNN inline
micro-ebusd inline reload: ok

The example above is using the inline mode, i.e. the definitions are uploaded directly to the device but not stored for subsequent use.

In order to have them available even after reboot, omit the -i option to the tsp2ebusd command. It will then store the converted definitions on the webservice for future use and download them from there immediately.