Help and feedback: report a bug as an issue on GitHub and an idea as a discussion. Nothing gets lost, everyone sees the state, and you are credited in the release notes once it is built. The two buttons for it are also at the bottom of the editor's sidebar and on the Extensions page.
How do I get the latest update? Settings → System → Updates. The Marketplace only looks for new versions every few hours, so a fresh update may not show there yet; then look again a little later. With HACS (Home Assistant before 2026.11) it works right away: HACS → NeonPlan 3D → ⋮ → Update information → Download. Then restart Home Assistant and reload the page (Ctrl+F5; in the Companion app: Settings → Companion app → reset frontend cache).
Can I use helpers instead of real sensors?
Yes. Wherever NeonPlan expects a number (power, charge, range, position …), input_number and number helpers can be picked too, and wherever it expects on/off (contact, presence …), input_boolean as well. For power the helper needs the unit W or kW.
An Echo's volume does not change.
Alexa Media Player does not set the volume on some Echos, or only with a delay, and reports the new value late. Check it in Developer tools → Actions with media_player.volume_set: if nothing happens there, it is the integration (see chapter 6.5).
"Restart needed" appears at the top. After an update the old version still runs in the background. Restart Home Assistant.
On an iPhone or iPad NeonPlan closes when I move or zoom with two fingers. That is no crash: the Home Assistant app has gestures of its own. If a two-finger swipe has an action there (e.g. to the start page), the app runs it and leaves the page. In the app, set the two-finger gestures under Settings → Companion App → Gestures to None. It never happens in Safari.
A device is missing in a room's device list. The room needs an area, and the device must belong to that area, either the device or the entity itself. If the entity sits under a device with several entities, it is behind "+n more". The search field finds it directly. Entities hidden or disabled in Home Assistant are never taken in by themselves; one that was placed in the room before stays in the list, so you can remove it or hide it with 👁.
A camera is hard to hit. Tap its wedge on the floor, it counts like the camera.
Furniture shows as grey boxes. The pack it comes from is not installed. Import it again or install it through the shop connection.
Dragging in 3D, an item does not pass through the wall. That is on purpose: in the 3D view furniture and devices stay in their room while dragged and slide along the wall. Move them into another room in the floor plan, where they move freely.
A tap hits the device in the next room. Walls catch taps. In the room view only things in the room count. If it still hits the wrong thing, the Cut switch helps.
The view stutters on the tablet. Set quality to Tablet and check with FPS what is drawing. At rest it should read 0 fps. If something keeps running, the reason is shown next to it, e.g. a lamp's colour effect.
Time travel shows nothing, "unknown" or gaps.
Time travel takes the history from Home Assistant's recorder. If the bar says "Without Home Assistant's recorder there is no history", the recorder is switched off (recorder: in configuration.yaml). A device reading "unknown" is excluded from the recorder (exclude: under recorder:) or new. Grey areas at the start of the bar: the recorder has not collected 24 hours yet (freshly set up, or purge_keep_days is below 1). Hatched areas: Home Assistant was off or restarting then. Temperatures and power come from the five-minute statistics; a sensor without a state class (state_class: measurement) is shown from its states instead. If the bar says "Please restart Home Assistant", an older version still runs in the background.
The 3D view breaks off right after it starts (graphics lost, "Error creating WebGL context"). Some older graphics chips fail on the sun's arc, the house shadow or the window glow at night (e.g. older AMD chips in Chrome on a Mac). If the 3D view loses its graphics within the first seconds, the browser remembers it: from the next load on, this browser starts without these effects, and ⚙ Settings says so. Every new NeonPlan version tries them again once. If Chrome has blocked the graphics after several crashes, quit Chrome completely and open it again.
Sunlight falls through the wrong windows. Check North under Settings: degrees clockwise from "up" in the plan.
The shop connection reports "limit reached". The key was connected to more than five new installations in the last twelve months. Contact us, we will help.
Activation says "The shop is busy right now" or "HTTP 429". The shop's web host throttles too many requests from one address. Since 1.9.1 NeonPlan retries twice with a pause by itself; if it still fails, wait a minute and click Activate again. Versions before 1.9.1 were turned away by the host because of their user agent – there only the update helps.
The notice "This page still shows NeonPlan 3D x.y, Home Assistant already has …" stays. The browser or the companion app still holds an old NeonPlan bundle. Tap Reload; in the companion app go to Settings → Companion app → Reset frontend cache, then close the app completely and open it again. Restarting Home Assistant does not help here. The same applies when a bought Pro add-on says "needs a newer NeonPlan version" under the packs.
Two holograms hang on the roof (Energy Pro). That is intended: the big one is the house balance (Solar & Energy), the smaller one the plant card of the inverter whose field that is – with several plants each has its own. Too much? In the Hologram section hang the house balance Free in the plan (handle ◈), or untick Show the plant card in the inverter form. A small card that seems to stick to the roof is often the device hologram of a device in the room below – turn the camera a little.
The shop cannot be reached. Installed packs and Pro add-ons keep working. Updates arrive as soon as the shop answers again.
Where do I report bugs? In the issue tracker on GitHub: https://github.com/Mastershort/neonplan3d/issues