-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Confirm the Wiser integration is loaded. It installs and updates the card bundle, registers the card resource and manages its version automatically. Avoid adding a duplicate resource entry or installing the card separately. Refresh the browser and check Home Assistant’s logs if the card is still unavailable. See Installation.
Reload each browser or companion app displaying the dashboard. The editor shows the loaded card version. If it remains stale, reload the Wiser integration or restart Home Assistant, then refresh the browser. Installation, bundle replacement and resource versioning are automatic; there is no need to edit the resource or its version query string manually.
Check that the Wiser integration is loaded and its hub is available. This card relies on the integration's wiser/hubs and wiser/zigbee WebSocket commands. Select the exact hub name in the visual editor and try Refresh. Capture any displayed error and relevant browser console message when reporting a problem.
Details depend on what the integration provides and whether the card can match a signal entity in the Home Assistant registry. Check the device and entity assignments for the selected hub. A missing or disabled signal entity can limit metrics and prevent native More info from opening, while a normal tap still shows available map details. Paired zero RSSI/LQI readings are deliberately omitted.
Assign the device to a Home Assistant area. The card falls back to a matched signal entity's area when the device has no area. Devices that cannot be matched also appear under Unassigned. Refresh after changing assignments.
Labels hide when no collision-free space is available. Increase the card size, use Fit view or Tidy, or try another orientation. Tap a device or expand the devices and connections list to inspect information that does not fit on the map.
Press Save layout on an editable storage dashboard, or merge Copy's YAML fragment into the dashboard configuration. Saving only to browser storage does not transfer positions. If using the card editor, finish with its Save button. See Saving layouts.
Confirm the dashboard supports editing and the card can be identified uniquely. Give duplicate cards different layout_id values. YAML and strategy-generated dashboards cannot be saved by this mechanism; use Copy and update their configuration manually. Browser storage restrictions can also prevent local persistence.
Leave Map height empty for Auto and adjust rows in the Sections card's Layout settings. For a fixed map area, use a numeric map_height between 100 and 2000. Detailed view adds content outside the map; use map_only: true for a compact presentation.
The card uses native Home Assistant components. The demo can exercise the map, but it does not recreate the complete Home Assistant editor or dashboard environment. Verify those features inside Home Assistant.
Include the card and Home Assistant versions, browser/device, dashboard mode, a minimal card configuration, steps to reproduce, and the exact error. For routing or display issues, a screenshot can help. Remove information you do not want to share before posting to the issue tracker.