Troubleshooting

Troubleshooting

Card not found

Confirm that /wiser/wiser-controls-card.js is registered as a JavaScript module when resources are managed manually. Restart Home Assistant and hard-refresh the browser after installation.

Old version still displayed

The frontend can retain an older JavaScript bundle. Try, in order:

1. Reload the dashboard.
2. Hard-refresh the browser.
3. Clear Home Assistant frontend cache.
4. Test in a private browser window.
5. Confirm the version displayed at the bottom of the visual editor.

Local -dev.N builds are test assets. Published beta updates omit the trailing development component; stable releases use versions such as 0.5.0.

Controls update does not appear after the rename

Install the Wiser Frontend Panel Config update first. It replaces the old Rooms registry entry with the Controls repository and filename. Check for updates again; Wiser Controls Card should then be offered. The previous wiser-rooms-card.js bundle is recognised as the installed legacy version.

Dashboard resource listed more than once

Early rename testing could leave two identical Controls resource entries. It is safe to choose Clear the extra copies, keep the most recent in Spook. Current integration builds serialise resource registration and automatically remove duplicate current or legacy Wiser resources.

Devices are missing

• Confirm the entity belongs to the Wiser integration and is enabled.
• Check the selected Hubs and device-type buttons.
• Check Hide devices, excluded_entities and any explicit entities list.
• New devices appear automatically only when an explicit entities list is not limiting the card.

For a multi-hub card, also check that the entity is configured under the correct hub_configs item. Entity IDs, ordering and device options are scoped to their owning hub.

Controls or feature editor are unavailable

The feature editor relies on Home Assistant's native Tile components. Update Home Assistant and reload the browser. Unavailable entities cannot be controlled.

Secondary status causes a configuration error

Secondary status now uses its own setting rather than an item in features. Use a list for state_content, even when showing one item:

secondary_status:
  state_content:
    - state

Current builds also normalise a single scalar value automatically. In Master mode, make sure entity-map keys belong to rooms of the active type.

A new Master type has Heating settings

Update to a current build. New Master types now start from their own defaults. Remove and re-add the affected type to discard an older retained configuration.

Reporting a problem

Open an issue with:

• Card and Home Assistant versions
• Relevant card YAML
• Entity domain and important attributes
• Browser-console error text
• A screenshot when the issue is visual