DHIVA LABS · LEARN

Appearance

Troubleshooting and FAQ ​

Answers to the problems people run into most often with HomeDeck. HomeDeck is in early access, so if your problem is not here, please report it.

Devices and network ​

The network scan finds nothing ​

The device is probably on a guest network, which keeps devices from seeing each other. Connect it to your main Wi-Fi network and scan again. On a slow device, give the scan a minute or so to finish.

A device I hid has gone and I want it back ​

In this version a hidden device cannot be shown again from the app. Choose Forget instead of Hide next time: a forgotten device comes back with the next scan, without its name and room.

Wake does nothing ​

Wake-on-LAN must be turned on in the target computer's BIOS or UEFI settings and in its network adapter's settings. It generally does not work when the computer is on Wi-Fi; connect it with a network cable.

Cameras ​

No ONVIF cameras answered ​

Some cameras ship with ONVIF turned off. Turn it on in the camera's own settings or app, then scan again. Or add the camera by hand with its RTSP address. See Add security cameras.

A camera appears but will not play ​

Check the username and password first. If they are right, the device may not be able to decode the camera's main stream: old graphics chips often cannot handle high-resolution video. Use the camera's lower-resolution sub-stream as the Stream URL.

Home Assistant ​

Token rejected ​

The token was mistyped or has been revoked. Tokens are long; paste rather than type. If unsure, create a new one in Home Assistant under your profile › Security › Long-lived access tokens.

Reached the server, but no Home Assistant API at that address ​

Usually the wrong port. Home Assistant listens on port 8123 unless it is behind a reverse proxy: check the address ends in :8123.

Find on network does not find Home Assistant ​

Type the address yourself: usually http://homeassistant.local:8123. If .local names do not work on your network, use the Home Assistant machine's IP address, for example http://192.168.1.20:8123.

Voice assistant ​

The wake word never triggers ​

  • Check Microphone access says Granted in Settings › Assistant › Voice assistant, and that Voice assistant is turned on.
  • Raise Sensitivity. In version 1.0.1 the open engine hears the wake word only rarely at the default 50%; try about 75%.
  • Keep HomeDeck open on screen.
  • Choose a longer wake phrase, such as hey jarvis rather than one short word.

It triggers when nobody said the wake word ​

Lower Sensitivity a little, or pick a phrase that is less like everyday speech.

It heard me but did the wrong thing, or nothing ​

Use the device's name exactly as it appears in HomeDeck, and the room names you created. If two devices match, the assistant asks Which one?. Remember it only controls devices: it does not answer questions, chat or set timers.

Does HomeDeck send my voice to the cloud? ​

The wake word and the command rules run on the device. Speech-to-text uses Android's recogniser, offline when the device has an offline speech model; without one, Android may use its online service. Typed commands never leave the device.

Performance ​

The app feels slow ​

Look at what Performance mode on Auto decided in Settings. If it left effects on but the device still struggles, choose On. Add snapshot URLs to cameras so the grid shows still pictures. See Make a wall panel.

Getting help ​

Report bugs and ask questions on the GitHub issues page. Never include your Home Assistant token, MQTT password or camera passwords in a report.

Next steps ​