We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Would it be possible to populate some eBus Adapeter info into ebusd and then read them in KNX / HA? For example WiFi strength or FW version?
The text was updated successfully, but these errors were encountered:
firmware version is already reported to HA and reflected as device update check entity. wifi strength might be interesting to add indeed
Sorry, something went wrong.
For HA there is already the option to fetch the data via API request from your Adaper:
The in-built MQTT option which got recently released did not work unfortunately, as it does comes with a few bugs, so I helped myself:
sensor: - platform: rest name: "eBUS Adapter JSON" resource: http://192.168.178.XX/api/v1/status json_attributes_path: "ebus" value_template: "{{ value_json.ebus.signal }}" json_attributes: - on - connected - proto - host - signal headers: Content-Type: application/json scan_interval: 60
Other values can be fetched too, by changing the json_attributes_path.
being a bit more specific wrt "comes with a few bugs" would certainly be helpful...
No branches or pull requests
Would it be possible to populate some eBus Adapeter info into ebusd and then read them in KNX / HA?
For example WiFi strength or FW version?
The text was updated successfully, but these errors were encountered: