Repository navigation
Releases
Releases · maxm/ptz-360
7
- Cameras that don't report their position are recognised in calibration: some cameras answer pan 0, tilt 0, zoom 0 whatever they do. Calibration now stops after its first small move and says so ("the camera reported the same position … after a move, so it doesn't say where it is over ONVIF"), instead of failing later with "is the picture changing, or plain?".
- On a failed calibration the camera is stopped before it's sent back, for cameras that take a move to a position as "keep turning this way".
6
- Card settings are in the dashboard editor: edit the dashboard, then the card. The editor has the camera, the video source, the panorama's colour, presets, Set home to the current view and Recalibrate…. The card's ⋯ menu is gone.
- Presets: turn the preview to a view and choose Add the current view; each preset becomes a button under the picture. Presets can be renamed, moved to the current view, reordered or removed, and are saved in the card's config (
presets:). - The panorama's colour is now a card setting (
colour:, 0–1), the same on every device. A colour set earlier with the old slider was kept per browser and goes back to the default (0.3) until set in the editor. - For bug reports, hover over the LIVE badge to see whether the video is WebRTC or MJPEG and how the last move went.
5
- Absolute moves are tried, not read from a list: adding a camera now sends it a move to where it already is (so it stays put) and refuses it only if it doesn't accept the move. Before, it read the first PTZ node's list of position spaces, and some cameras list absolute moves elsewhere or not at all and still take them. If release 4 refused your camera for absolute moves, remove it and add it again.
- The outlines option is removed; the panorama's colour slider stays.
4
- How the panorama looks: the card's ⋯ menu (now shown to everyone) has a Colour slider, from grey to the panorama's own colours, and an Outlines only option that draws the panorama as light lines on dark. Both are kept per camera in each browser. Set home and Recalibrate are still only for admins.
- Cameras that can't work are refused at setup: adding a camera now checks that it moves to absolute positions and reports its position over ONVIF, and says which one it can't do. A camera added earlier that can't fails setup with the same reason, instead of errors like
'NoneType' object has no attribute 'PanTilt'.
3
- Fixes "Custom element doesn't exist: ptz-360-card" on dashboards with Home Assistant 2026.9 and 2026.10. The card's script could run before Home Assistant's frontend replaced the page's element registry, and the card then wasn't found. It now registers only once the frontend is up, however long that takes.
After updating, restart Home Assistant and reload the dashboard.
2
1
The first release. From here on HACS offers each release as an update instead of every push to main.
- The card on a dashboard: the script registers itself again in Home Assistant's element registry (it could load before it, and the dashboard said "Custom element doesn't exist").
- Calibration: a dropped camera call reconnects and is sent again, instead of ending the calibration.