You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hardware: eBUS Adapter (Firmware 20260118) in micro-ebusd mode.
Integration: MQTT to Home Assistant.
The Problem: My adapter successfully connects to the bus and "sees" the masters, but the automatic configuration download fails with a 404 error for the BAI/HCM and BM-2 components.
Log Snippet:
Infoebusd: seen 10
Errorebusd: unable to download/store 5008..hc.ead ... 404 open
Status: 08: *recv, MF fail
Observations:
Address 10 (BAI/HCM): Identified as "seen", but no CSV is loaded, so all entities in Home Assistant remain "Unknown".
Address 08 (BM-2): Returns MF fail, preventing the adapter from identifying the correct manufacturer ID and loading the 08.csv.
Configuration Tab: The "Config path" field is not visible in the Web-UI (even in Admin mode), so I cannot easily point it to a local mirror or a different GitHub branch.
Questions for the community:
Is there a specific CSV branch or a manual URL I should use for the Wolf BM-2 / CGB-20 combination to avoid the 404 error?
How can I force a configuration path in micro-ebusd mode if the field is hidden in the Web-UI?
Does the MF fail on GA 08 usually indicate a hardware/timing issue or just a missing definition file for the Wolf identification string?
I have already tried manual scans via MQTT (eas/ebusd/scan), but without the translation files, the entities stay unpopulated. Any help or hints on where to place local CSV files on this adapter firmware would be greatly appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
System Environment:
Boiler: Wolf CGB-20 (BAI/HCM)
Controller: Wolf BM-2 (GA 08)
Other Modules: Wolf MM/SM (GA 30)
Hardware: eBUS Adapter (Firmware 20260118) in micro-ebusd mode.
Integration: MQTT to Home Assistant.
The Problem: My adapter successfully connects to the bus and "sees" the masters, but the automatic configuration download fails with a 404 error for the BAI/HCM and BM-2 components.
Log Snippet:
Observations:
Address 10 (BAI/HCM): Identified as "seen", but no CSV is loaded, so all entities in Home Assistant remain "Unknown".
Address 08 (BM-2): Returns MF fail, preventing the adapter from identifying the correct manufacturer ID and loading the 08.csv.
Configuration Tab: The "Config path" field is not visible in the Web-UI (even in Admin mode), so I cannot easily point it to a local mirror or a different GitHub branch.
Questions for the community:
Is there a specific CSV branch or a manual URL I should use for the Wolf BM-2 / CGB-20 combination to avoid the 404 error?
How can I force a configuration path in micro-ebusd mode if the field is hidden in the Web-UI?
Does the MF fail on GA 08 usually indicate a hardware/timing issue or just a missing definition file for the Wolf identification string?
I have already tried manual scans via MQTT (eas/ebusd/scan), but without the translation files, the entities stay unpopulated. Any help or hints on where to place local CSV files on this adapter firmware would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions