I think I found the issue. I pushed a new build for you to test and confirm.
Thanks for having a crack at this! The new version runs when I do the sync entities, it steps through my seven devices and is definitely doing something but the device list still isn’t picking up their areas and continuing to show ‘no area’.
It’s not vital of course.
That’s odd.
Are you using it as an HA add-on or docker stand alone?
Can you grab the logs from
Browser console (F12 → console)
and
From the output of the app, eitther in settings/apps/bl manager/logs or the docker container output.
I def found a bug when I tested it and resolved that bug, but you might be experiencing something different.
Tony
Thanks Tony. Running HAOS on a dedicated NUC so BM2 is installed as an app.
I’ve managed to look at the log files and this is what its been throwing out for the ten remotes it pulled across from Broadlink. (I have been using most of them before I discovered your brilliant app direct from Broadlink using scripts to dashboard remotes).
All the remotes are learning and transmitting fine from the app. It’s just the area that’s nots being pulled across.
To avoid lots of repetition, this is what I get for each remote in the log file
2026-04-11 16:25:30,591 - api.devices - INFO - Found device 'Meridian Remote' in device_manager
2026-04-11 16:25:30,592 - api.devices - INFO - Built entity_id: media_player.Meridian Remote
2026-04-11 16:25:30,610 - area_manager - ERROR - Command failed: {'code': 'invalid_format', 'message': "Entity ID media_player.Meridian Remote is an invalid entity ID for dictionary value @ data['entity_id']. Got 'media_player.Meridian Remote'"}
2026-04-11 16:25:30,613 - api.devices - INFO - Entity media_player.Meridian Remote not found in HA registry yet (entities not generated or HA not restarted)
Ah… There is a space in the entity “Meridian Remote”. This was only affecting the sync logic and nothing else. It was trying to get the entity ‘media_player.Meridian Remote’ which is invalid. Once you install the new release it will now fetch ‘media_player.Meridian_Remote’ Which IS valid.
Give it a try and let me know.
Still getting the same errors in the logfile.
Oh, and I’ve been playing with the import code functionality, it works really well though getting the code in a compatible format can be a challenge so I’ll leave this conversion site here for anyone searching in the future Sensus IR & RF Code Converter
Can you share the logs again. And confirm the version you are on?
2026-04-15 12:02:23,649 - web_server - INFO - Making GET request to: http://supervisor/core/api/states
2026-04-15 12:02:23,682 - web_server - INFO - ✅ Response status: 200
2026-04-15 12:02:23,693 - web_server - INFO - Response data type: <class 'list'>, length: 621
2026-04-15 12:02:23,695 - api.config - INFO - Found 7 remote devices from HA API
2026-04-15 12:02:27,335 - api.devices - INFO - Found device 'Hifi room TV' in device_manager
2026-04-15 12:02:27,336 - api.devices - INFO - Built entity_id: media_player.hifi_room_tv (from device_id: Hifi room TV)
2026-04-15 12:02:27,365 - api.devices - INFO - Entity media_player.hifi_room_tv not found in HA registry yet (entities not generated or HA not restarted)
2026-04-15 12:02:27,388 - api.devices - INFO - Found device 'MSR remote' in device_manager
2026-04-15 12:02:27,389 - api.devices - INFO - Built entity_id: media_player.msr_remote (from device_id: MSR remote)
2026-04-15 12:02:27,411 - api.devices - INFO - Entity media_player.msr_remote not found in HA registry yet (entities not generated or HA not restarted)
2026-04-15 12:02:27,430 - api.devices - INFO - Found device 'Family room TV' in device_manager
2026-04-15 12:02:27,431 - api.devices - INFO - Built entity_id: media_player.family_room_tv (from device_id: Family room TV)
2026-04-15 12:02:27,450 - api.devices - INFO - Entity media_player.family_room_tv not found in HA registry yet (entities not generated or HA not restarted)
2026-04-15 12:02:27,471 - api.devices - INFO - Found device 'Meridian Remote' in device_manager
2026-04-15 12:02:27,472 - api.devices - INFO - Built entity_id: media_player.meridian_remote (from device_id: Meridian Remote)
2026-04-15 12:02:27,492 - api.devices - INFO - Entity media_player.meridian_remote not found in HA registry yet (entities not generated or HA not restarted)
2026-04-15 12:02:27,519 - api.devices - INFO - Found device 'hifi_room_aircon' in device_manager
2026-04-15 12:02:27,519 - api.devices - INFO - Built entity_id: climate.hifi_room_aircon (from device_id: hifi_room_aircon)
2026-04-15 12:02:27,542 - api.devices - INFO - Entity climate.hifi_room_aircon not found in HA registry yet (entities not generated or HA not restarted)
2026-04-15 12:02:27,561 - api.devices - INFO - Found device 'oppo_br_player' in device_manager
2026-04-15 12:02:27,562 - api.devices - INFO - Built entity_id: media_player.oppo_br_player (from device_id: oppo_br_player)
2026-04-15 12:02:27,581 - api.devices - INFO - Entity media_player.oppo_br_player not found in HA registry yet (entities not generated or HA not restarted)
2026-04-15 12:02:27,601 - api.devices - INFO - Found device 'panasonic_4k_player' in device_manager
2026-04-15 12:02:27,602 - api.devices - INFO - Built entity_id: media_player.panasonic_4k_player (from device_id: panasonic_4k_player)
2026-04-15 12:02:27,627 - api.devices - INFO - Entity media_player.panasonic_4k_player not found in HA registry yet (entities not generated or HA not restarted)
2026-04-15 12:02:27,650 - api.devices - INFO - Found device 'Hifi room aircon' in device_manager
2026-04-15 12:02:27,651 - api.devices - INFO - Built entity_id: switch.hifi_room_aircon (from device_id: Hifi room aircon)
2026-04-15 12:02:27,671 - api.devices - INFO - Entity switch.hifi_room_aircon not found in HA registry yet (entities not generated or HA not restarted)
2026-04-15 12:02:27,692 - api.devices - INFO - Found device 'Study aircon' in device_manager
2026-04-15 12:02:27,692 - api.devices - INFO - Built entity_id: switch.study_aircon (from device_id: Study aircon)
2026-04-15 12:02:27,713 - api.devices - INFO - Entity switch.study_aircon not found in HA registry yet (entities not generated or HA not restarted)
2026-04-15 12:02:27,737 - api.devices - INFO - Found device 'Ballroom Aircon Fujitsu' in device_manager
2026-04-15 12:02:27,738 - api.devices - INFO - Built entity_id: climate.ballroom_aircon_fujitsu (from device_id: Ballroom Aircon Fujitsu)
2026-04-15 12:02:27,762 - api.devices - INFO - Entity climate.ballroom_aircon_fujitsu not found in HA registry yet (entities not generated or HA not restarted)
Home Assistant OS Core2026.4.2, Supervisor2026.04.0, Operating System17.2, frontend20260325.7
Broadlink Manager v2 (Beta) version 0.4.0-beta.19
And if this is all getting too painful, please say so. My enjoyment of the app is not impaired - I wanted it to easily manage my Broadlink remote codes and it does that really well
Hey, no worries. I don’t mind tracking down these issues. I appreciate your patience and providing feedback.
Sorry if this is a stupid question but did you generate entities?
Below is the output from Claude with additional things to check if you have generated entities.
If the user has already generated entities, here’s what to ask for to diagnose the issue:
Key Diagnostic Questions
1. Verify Entity Generation Success
- “Can you check if the files
package.yamlandhelpers.yamlexist in your Home Assistant config folder underpackages/broadlink_manager/?” - “What does the entity generation success message say? Does it show how many entities were created?”
2. Verify HA Restart
- “Have you restarted Home Assistant after generating the entities?”
- “After restart, can you see the entities in Home Assistant? (Developer Tools → States, search for
media_player.meridian_remote)”
3. Check Entity Registry
- “In Home Assistant, go to Settings → Devices & Services → Entities”
- “Search for one of your devices (e.g., ‘meridian_remote’)”
- “Does it show up in the list? If yes, what area is it assigned to?”
4. Check YAML Files
- “Can you share the contents of
/config/packages/broadlink_manager/package.yaml?” - “Look for entries like
media_player.meridian_remote- do they exist?”
5. Get Fresh Logs
- “After confirming entities exist in HA, try the area sync again”
- “Share the new logs from the sync attempt”
- “Specifically look for whether it still says ‘not found in HA registry’ or if there’s a different error”
Most Likely Scenarios
If entities were generated but sync still fails:
Scenario A: Entities exist but HA wasn’t restarted
- Solution: Restart Home Assistant
Scenario B: Entity IDs in YAML don’t match what the sync is looking for
- Check: Compare entity IDs in
package.yamlvs what the logs show - Issue: Mismatch between generated entity ID and what sync is querying
Scenario C: Entities exist but aren’t in HA’s entity registry
- Check: Developer Tools → States
- Issue: YAML might have errors preventing entity loading
Quick Verification Command
Ask them to run this in Home Assistant Developer Tools → Template:
{{ states.media_player.meridian_remote }}
If it returns <state media_player.meridian_remote=...>, the entity exists.
If it returns unknown or an error, the entity doesn’t exist in HA.