iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For most Home Assistant installations, begin with the built-in Proxmox VE integration. Enable CPU, memory, disk, backup, and VM/LXC status entities for a useful health dashboard; add network counters and uptime when you have a specific diagnostic or capacity use for them. Enable control buttons only for operations you genuinely perform, and give Home Assistant a dedicated Proxmox account with the minimum permissions for those operations.
The right configuration depends on whether you want visibility, backup awareness, availability alerts, troubleshooting data, or remote administration. The sections below map each goal to the entities and permissions it needs, then explain the safer way to enable them.
Start with the entities that answer a real question
A large list of sensors is not automatically a better monitoring system. Every enabled entity should support a dashboard card, an alert, or an automation that you would actually use. This is a practical starting point for the built-in integration:
Recommended Free Tools
| Goal | Enable first | Why it matters |
|---|---|---|
| Quick health overview | CPU, memory, disk, VM/LXC status | Shows whether hosts and guests are running normally and whether resources are becoming constrained. |
| Backup awareness | Last backup time, backup duration, node backup-status binary sensor | Shows when the last backup completed and whether Proxmox reported its last backup as successful or not. |
| Availability alerts | VM/LXC status | Lets Home Assistant distinguish a running guest from other states. |
| Capacity troubleshooting | Disk, memory, network input/output counters | Helps explain storage pressure, memory exhaustion, or unusual traffic. |
| Historical context | Uptime | Provides a quick indication of restarts and host stability. |
| Remote operations | Only the required action buttons | Allows deliberate administration without turning Home Assistant into an unrestricted Proxmox console. |
Some entities are disabled by default. That is an intentional way to keep a new installation from creating an overwhelming device page. You can enable them individually from the relevant Proxmox device in Home Assistant.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.
Install and verify the built-in Proxmox VE integration
The official integration needs at least one Proxmox node with at least one virtual machine or container. Without a guest, there may be no guest entities to display.
- In Home Assistant, open Settings.
- Choose Devices & services, select Add Integration, and search for Proxmox VE.
- Enter the Proxmox host details and the dedicated account or API-token credentials you created for Home Assistant.
- Complete the setup and open the new Proxmox device. Review the entity list rather than assuming every sensor is active.
- Open a disabled entity and choose the option to enable it. Repeat only for sensors and controls that match your monitoring plan.
If the integration discovers the node but not the guests, first confirm that the account can see the relevant node, virtual machines, and containers. Permissions are applied to Proxmox resources, so a credential that can read one node may not be able to enumerate another.
Which sensors are most useful?
CPU usage
CPU sensors are the fastest way to spot sustained host or guest contention. Put them on a dashboard when you want to know whether a workload is consuming its allocation, or create an alert for an unusually high value that persists long enough to avoid reacting to a short burst. CPU alone does not explain a slow application: correlate it with memory and disk before taking action.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteMemory usage
Memory is usually more actionable than a momentary CPU spike. It can reveal a guest approaching its limit or a node running out of headroom for another service. Display the percentage and, where your chosen entity exposes it, the underlying amount so that a small percentage on a large host is not mistaken for a small absolute allocation.
Disk usage
Enable disk sensors for capacity management. A nearly full guest filesystem can break updates and databases; a nearly full Proxmox storage resource can prevent snapshots, backups, or new guests. Treat a high reading as a planning signal first: identify which filesystem or storage resource is filling, then remove data or expand capacity using a controlled Proxmox procedure.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Last backup time and duration
The last-backup timestamp answers “when did a backup last run?” Duration adds context: a sudden increase can indicate storage contention, a changed guest workload, or a slow destination. Use both in a dashboard or automation, but do not interpret a recent timestamp as proof that you can restore successfully. A restore test and a review of the backup schedule remain separate operational tasks.
Node backup-status binary sensor
The node backup-status binary sensor describes the status reported for the last backup. It is useful for an alert that calls attention to a failed or otherwise unhealthy result. It does not replace checking that every required guest is included, that retention is appropriate, or that the destination is available.
VM and LXC status
Guest status is the best entity for availability monitoring. Home Assistant describes the binary state as on when a virtual machine or container is running and off for other states. Use it for a notification when a critical guest unexpectedly stops, or for a dashboard that shows the services currently online. If a guest is intentionally powered down, suppress or acknowledge the alert rather than treating every off state as an incident.
Network input and output counters
Network counters are valuable when you are investigating traffic, validating a busy service, or looking for a guest that is transmitting more than expected. Interpret them correctly: the documented counters represent traffic since the VM or LXC started, not a rolling per-minute rate. A reboot therefore resets the accumulated value. For rate-based alerting, compare successive readings in Home Assistant instead of treating the raw counter as an instantaneous speed.
Uptime
Uptime is a compact stability indicator. It can reveal an unplanned reboot that is not obvious from an application dashboard. It is most useful alongside status and backup information: a recently restarted node may still be healthy, but you should know whether scheduled backups and critical guests recovered as expected.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Controls: enable only deliberate operations
Controls turn a monitoring integration into an administration surface. Enable them only after deciding who may use them and what should happen when a button is pressed. Home Assistant documents guest buttons for starting, stopping, restarting, rebooting, shutting down, snapshotting, hibernating, and resetting guests, as well as node-level actions where the account has permission.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Control type | Operational meaning | Important caution |
|---|---|---|
| Start | Requests that a stopped guest begin running. | Starting a guest may also start dependent workloads; use it only where that dependency is understood. |
| Stop / Stop all | Stops a running system immediately. | Immediate stopping can interrupt applications and risk data loss. Protect these buttons from casual dashboard access. |
| Restart | Stops a running system immediately as part of the restart operation. | This is not the same as asking the guest operating system to reboot cleanly. |
| Reboot | Attempts a graceful reboot, using the guest agent when it is installed. | Graceful behavior depends on guest cooperation and agent availability. |
| Shutdown | Attempts a graceful shutdown, using the guest agent when it is installed. | Do not assume graceful shutdown is possible if the guest agent is absent or unresponsive. |
| Snapshot | Creates a Proxmox snapshot when the account and storage configuration allow it. | A snapshot is not a substitute for an independent backup and consumes storage. |
| Hibernate | Requests the documented hibernation action for the guest. | Confirm that the guest and its storage support the operation before exposing it. |
| Reset | Requests a reset of the guest. | Treat it as a recovery action, not a routine restart; it can be disruptive. |
The critical distinction is between immediate and graceful actions: the documentation states that Restart and Stop/Stop all stop a running system immediately, while Reboot and Shutdown attempt graceful behavior. Label dashboard buttons clearly and put disruptive actions on a restricted view.
Permissions and authentication
Use a dedicated account, not root
Create a separate Proxmox identity for Home Assistant and assign only the permissions required by your chosen entities and controls. Home Assistant recommends avoiding root. A dedicated identity makes revocation, auditing, and troubleshooting much easier than sharing an administrator credential.
Monitoring-only permissions
For monitor-only sensors and binary sensors, Home Assistant identifies PVEAuditor as typically sufficient. Apply the permission at the narrowest resource scope that still includes the node, guests, or storage you want to display. If Home Assistant should see only one node, do not grant visibility across the entire cluster.
Permissions for buttons
Controls need additional privileges for their specific actions. PVEVMUser is given as an example for monitoring plus basic guest actions, but it should not be treated as a universal answer for every button or node operation. If that role is broader than necessary, create a custom role and grant only the required actions on the specific guests or nodes.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
API tokens
An API token gives Home Assistant a separate, revocable credential. Proxmox supports privilege separation: when it is enabled, the token can have permissions distinct from the user; when it is disabled, the token inherits the user’s permissions. Choose deliberately, document the scope, and store the token secret securely. Proxmox displays the secret only once when the token is created, so losing it means creating a replacement token.
A safe procedure for enabling sensors and buttons
- Write the outcome first. Decide whether you need a dashboard, an availability alert, backup visibility, capacity diagnosis, or remote administration.
- Start with read-only entities. Enable CPU, memory, disk, status, and the backup entities that answer that outcome.
- Check the values. Confirm that the node and each intended guest report sensible states before building automations around them.
- Create the least-privilege credential. Use PVEAuditor for monitoring where it is sufficient; add narrowly scoped action permissions only when required.
- Enable one control at a time. Test a non-destructive path first, then add disruptive controls only to a restricted dashboard or automation.
- Document recovery. Record which account, token, resources, and buttons Home Assistant can use so another administrator can revoke or repair access.
Do not expose stop, restart, reset, or node-level controls on an unsecured wall tablet. A read-only dashboard is usually the better default for shared spaces.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Built-in integration or the custom integration?
The built-in integration is the sensible default when you need the documented node and guest sensors, binary sensors, and basic controls. It is maintained as part of Home Assistant’s normal integration experience and avoids adding another component to update.
A maintainer’s custom integration replaces the built-in integration when installed. Its documentation describes broader cluster and storage entities, additional node and guest readings, discovery, more actions, and optional hardware and physical-disk monitoring. It can select particular nodes, virtual machines, containers, and storage resources, which may suit a larger Proxmox environment.
| Consideration | Built-in integration | Custom integration |
|---|---|---|
| Best fit | Standard monitoring and basic controls | Advanced cluster, storage, hardware, or discovery requirements |
| Scope | Documented node and guest entities | Broader cluster, storage, and hardware coverage |
| Physical-disk SMART | Not the focus of the documented built-in entity set | Optional, according to the custom integration documentation |
| Hardware temperatures, fans, and voltages | Not the focus of the documented built-in entity set | Described as using PVE-mods |
| Operational trade-off | Fewer moving parts | Third-party updates, permissions, and compatibility become additional responsibilities |
Enable SMART monitoring only when you need it. The maintainer notes that reading SMART data wakes sleeping disks, so frequent polling can defeat a disk’s power-saving behavior. Hardware readings also depend on PVE-mods, adding another dependency to maintain. Most readers do not need this custom integration for CPU, memory, disk, backup, status, and basic controls.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Troubleshooting missing or misleading entities
The integration is present but entities are missing
- Confirm that at least one Proxmox node and one VM or container exist.
- Open the device page and check whether the entity is merely disabled by default.
- Verify that the Home Assistant account can view the resource where the entity belongs.
- Check whether you configured the intended node or accidentally scoped permissions to a different resource.
A control does not appear
Controls are permission-gated. Recheck the role and resource scope, then verify that the action is appropriate for that guest type. Do not solve a missing button by granting full administrator access; narrow, action-specific permissions are safer.
Network values look enormous
Remember that the documented counters accumulate traffic since the guest started. Compare readings over time to derive a rate, and expect the counter to reset after a reboot.
A graceful action does not shut down the guest
Reboot and Shutdown attempt graceful behavior and can use the guest agent when installed. If the agent is missing or unresponsive, the request may not behave as expected. Treat Stop or Restart as disruptive fallbacks, not as interchangeable labels.
Backup appears healthy but recovery is uncertain
The last-backup time, duration, and status describe the latest reported job. Confirm coverage, retention, destination health, and an actual restore procedure separately before relying on the backup for recovery.
Recommended baseline
For a new installation, enable CPU, memory, disk, VM/LXC status, last backup time, backup duration, and the node backup-status binary sensor. Add uptime when restart history matters, and add network counters when you are troubleshooting or measuring traffic. Keep controls disabled until you have a dedicated, least-privilege credential and a clear operational reason. Start with the built-in integration; move to the custom option only when its additional cluster, storage, SMART, discovery, or hardware features solve a requirement the built-in entities cannot.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
