VoIP.info Device reference

HP Poly Studio E60 smart PTZ camera

Evaluate Studio E60 as a camera-only USB or version-gated IP-LLN peripheral while preserving host, codec, power, pairing, provider-mode, privacy, framing and firmware boundaries.

Reviewed 2026-10-21HP product, specification, user, administrator, room-planning and release-note records reviewed October 21, 2026. Published optics, tracking, room, connector, platform and certification statements are manufacturer records, not installed-room acceptance. Exact regional SKU, package, host, codec, provider mode, cable, hub, switch, injector, camera count, software path, availability, price, warranty and support status require confirmation. No Studio E60, host, codec, room, mount, cable, hub, switch, injector, network, account, tenant, application, camera, firmware, update, meeting, image, media stream or call was inspected or testedAdvancedDocumentation based · not lab tested

Documented specifications

Open IP Phone Compare →

HP Poly · HP maintained a live product page, current specifications, user and administrator documentation and VideoOS release notes at review. Regional orderability, package, firmware entitlement, warranty and remaining support were not established.

Studio E60: manufacturer-sourced facts
SpecificationDocumented value
System boundaryCamera-only peripheral; it does not provide room microphones or speakers, and the attached PC or room system owns meeting identity, audio, service and session behavior Source ↗
Optical pathManufacturer specifies a 4K mechanical pan-tilt-zoom camera with 12x optical zoom, pan range ±170 degrees and tilt ±30 degrees; installed framing remains a room acceptance result Source ↗
AI lensA fixed AI lens detects participants within a 107-degree horizontal field of view to drive group framing or presenter tracking; detection is not proof that the optical output was transmitted Source ↗
Room planningHP positions E60 for large conference rooms, boardrooms and classrooms and lists a 71-degree horizontal field of view; room fit remains installation-specific Source ↗
USB pathUSB 3.0 Type-B connects the camera to a PC or supported room system through a Type-B to Type-A cable; USB enumeration and application selection remain separate Source ↗
Power and EthernetThe Ethernet port can power E60 with 30 W PoE+ Type 2/Class 4; a link or powered camera does not by itself establish IP pairing or a host video path Source ↗
Privacy and statusE60 uses a manually removable physical privacy cover and separate power and standby LEDs; cover, orientation, LED, preview and transmit state are different evidence Source ↗
Current release recordHP VideoOS 4.X release notes list E60 camera software 1.1.6.5 in March 2026; that record is not proof of one camera’s installed build or update result Source ↗

Unlisted fields remain unverified. Platform compatibility and remaining support life require confirmation for the exact ordered model.

Classify E60 as a camera-only peripheral

Studio E60 supplies video to an attached computer or supported room system. It is not a video bar, microphone, speaker, standalone SIP endpoint or native meeting appliance. The host or codec, meeting application, account and tenant own sign-in, meeting identity, audio and service behavior.

Record the exact E60 label and SKU, connection mode, host or codec, provider mode, room, mounting, power source, cable path and installed camera and system software before assessing fit.

Keep USB, IP-LLN, power and management separate

USB 3.0 Type-B is the direct camera path to a PC or supported room system. Ethernet can provide PoE+ power and supports documented IP-LLN workflows, but power, network link, management reachability, pairing and active video input remain separate evidence.

For direct PoE, HP specifies 30 W PoE+ Type 2/Class 4. Confirm the source, voltage class and link rather than assuming every PoE port or injector is suitable.

Apply the exact codec and provider-mode topology

Current administrator guidance keeps USB and IP-LLN camera modes distinct and says they cannot be mixed. The documented IP-LLN transition requires at least VideoOS 4.4.0 and E60 software 1.1.3.6, followed by explicit pairing; moving the camera back to USB or another system requires unpairing.

G62 and G7500 power differently: the G62 LLN port does not power E60, while the G7500 LLN path provides power. Camera counts also vary by codec and provider mode. Treat each system, mode, cable, power source and release as an exact compatibility record.

Use optics and tracking as planning inputs

HP publishes 12x optical zoom, ±170-degree pan, ±30-degree tilt, a 107-degree AI detection field and large-room positioning. Those values do not prove that one installed camera can frame every required seat, follow a presenter through occlusion, resolve whiteboard content or deliver acceptable remote video.

Validate mounting height, sight lines, lighting, backlight, minimum and maximum subject distance, presets, group framing, presenter tracking and manual control from the actual room positions.

Interpret privacy, orientation and LEDs separately

E60 uses a removable physical cover. The guide also maps power and standby LEDs to power, startup, awake, standby, update and pairing states, with the camera facing the room or wall in documented conditions. None of those observations alone proves what a meeting application is sending.

Preserve cover position, camera orientation, LED pattern, local preview, selected input, client video state and far-end receipt as separate evidence before changing settings.

Version updates and accept the complete room

Use current release notes for the installed camera and room-system versions. HP lists E60 camera software 1.1.6.5 in a March 2026 VideoOS build; the older 1.1.3.6 record is a minimum for the documented 4.4.0 IP-LLN transition, not a universal current target.

After an authorized change, repeat power, enumeration or pairing, active-input selection, preview, framing, transmit, leave, reboot and recovery. Validate room microphones and speakers through their own paths. No E60, host, codec, room, cable, network, firmware, meeting, image, media stream or call was inspected or tested for this reference.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.