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
Create a separate Proxmox VE account for Home Assistant, then give it only the permissions needed for the features you plan to use. For monitoring, Home Assistant identifies PVEAuditor as typically sufficient; basic VM power controls may require VM.PowerMgmt or a role such as PVEVMUser. You can authenticate with the account’s password or, optionally, an API token.
What the dedicated account does
The account is a Proxmox VE credential used by Home Assistant’s Proxmox VE integration to query your Proxmox environment and, if permitted, perform actions such as powering a VM on or off. It is separate from your Home Assistant login. You do not need to create a new household member or person in Home Assistant to use it.
Home Assistant distinguishes user accounts from persons: an account used by a service or integration does not have to represent a tracked person in the household. Treat this Proxmox user as an integration credential, not as a new Home Assistant login or a person you need to add to your household.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Proxmox permissions are role-based and path-scoped: a user or group receives a role on a particular path in the Proxmox resource tree. A permission assigned at / can cover the whole tree when propagation is enabled. That is convenient for cluster-wide monitoring, but it also gives the account scope over more resources. If Home Assistant only needs access to selected assets, consider a narrower path and confirm that the integration can still see the required nodes, VMs, and containers.
#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.
Think of the permission as three decisions working together: the subject is the user or group, the role determines the allowed operations, and the path determines the resources to which those operations apply. A read-oriented role assigned broadly can be less powerful than an administrative role, but it still has broad visibility. Conversely, a suitable role on a path that does not include a VM will not enable Home Assistant to monitor or control that VM.
Choose the role for the actions you need
Start with the smallest capability set that matches your intended use. Monitoring and control are separate: sensors can work even when a particular button or entity lacks its required action permission. Before creating permissions, decide whether Home Assistant only needs to read status or whether you also want it to change VM state, create snapshots, or expose the node update entity.
| What you want Home Assistant to do | Permission or role to consider | What to know |
|---|---|---|
| Monitor Proxmox and expose sensors or binary sensors | PVEAuditor |
Home Assistant says this role is typically sufficient for monitoring. |
| Monitor and use basic VM power actions | VM.PowerMgmt or PVEVMUser |
PVEVMUser is an available starting role for basic power operations. A custom role may be preferable if it grants more access than you want. |
| Create VM snapshots | VM.Snapshot or a role such as PVEVMAdmin |
Snapshot creation needs an additional privilege beyond basic monitoring. |
| Use the node update entity | Sys.Modify or PVEAdmin |
Home Assistant identifies this permission requirement for the node update entity. It is broader than read-only monitoring. |
These are capability clues, not a reason to grant an administrative role preemptively. If an action fails while monitoring works, first check the specific privilege required for that action. Home Assistant advises trying a custom role with the required privileges where a built-in role grants more than necessary.
Recommended Free Tools
For a monitoring-only installation, begin with PVEAuditor and check that the expected sensors and binary sensors appear. If you later decide you want power controls, add only the permission needed for those operations, or move to an appropriate role after considering what else it grants. The same incremental approach applies to snapshots and node updates: add their extra requirements only when you actually plan to use those capabilities.
Role names are not interchangeable with a single universal “Home Assistant permission.” PVEVMUser can be a convenient built-in starting point for power actions, while a custom role gives you a way to keep the granted privilege set narrower in deployments where the built-in role includes more than you need. If you choose a custom role, build it around the documented action requirements and test each intended function rather than assuming that a successful login means every entity can operate.
Create the Proxmox group and assign its role
A group makes the integration’s permissions easier to manage: assign the role to the group, then add the dedicated account to it. This separates the permission assignment from the individual user entry, so you can review the access granted to the group and which account receives it.
- Create a group: In the Proxmox interface, open Datacenter → Permissions → Groups and create a group, for example
HomeAssistant. - Grant the group a role: Open Datacenter → Permissions → Add → Group Permission. Set Path to
/, choose the new group, and select the role you decided to use. - Set propagation deliberately: Leave Propagate checked if the permission should apply through the tree to nodes, VMs, and containers. If you do not want cluster-wide scope, choose an appropriate narrower path instead and verify the integration’s visibility afterward.
The group permission is effective for accounts placed in that group. Assigning it at / with propagation is a convenient cluster-wide setup, not a requirement for every installation.
Use the root path and propagation when you intentionally want the permission to apply throughout the resource tree—for example, when Home Assistant should monitor multiple nodes and their guests. If your goal is to expose only selected assets, a narrower path can reduce scope. The tradeoff is that resources outside that path may not appear to the integration, so validate the result against the nodes, VMs, and containers you expect to see.
Do not treat the propagation checkbox as a harmless default. It is part of the scope decision. A permission granted at / without propagation and one granted there with propagation do not express the same intended reach through the tree. Check the path and propagation setting together, and avoid broadening them just to solve an unrelated authentication or action error.
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
Create a PVE-realm user and add it to the group
- Go to Datacenter → Permissions → Users → Add.
- Enter a username such as
hassand select the PVE realm. - Add the user to the
HomeAssistantgroup, or the group you created. - Keep the account enabled. If you plan to authenticate with a password, set a secure password and store it safely.
The PVE realm is the recommended choice for an account intended for Proxmox API access. It helps keep this integration credential separate from Linux system authentication and remote SSH access. When configuring password authentication in Home Assistant, the credential is represented in username@realm form; the integration setup may ask you for the username while you select the realm separately.
The username and realm are both part of identifying the account. If you create a user called hass in the PVE realm, it is not the same realm identity as a similarly named Linux system account. Use the PVE-realm account details consistently when entering the integration credentials; a mismatch can look like a password problem even when the account was created correctly.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteChoose the authentication method before finishing the account setup. For password authentication, you need a secure password for the enabled PVE user. If you plan to use only an API token, the token will be the credential entered for the integration, but the underlying dedicated user and its permissions remain part of the setup.
Add the Proxmox VE integration in Home Assistant
- In Home Assistant, open Settings → Devices & services → Add Integration, then add Proxmox VE.
- Enter the Proxmox host name or IP address and the API port. The default port is
8006. - Choose the authentication method and provide the dedicated account’s username and password, or the API token details if you created a token.
- Enable SSL certificate verification when Home Assistant can validate the Proxmox certificate. Do not disable verification casually; use it when the certificate setup allows it.
- Finish setup, then check that the expected entities appear before testing any control actions.
The integration needs at least one Proxmox node with at least one VM or container for entities to appear. If the connection is configured but no entities show up, confirm that the environment contains those resources and that the account can access them at the path where its permission was assigned.
Use the Proxmox host name or address that Home Assistant can reach, and keep the port at the Proxmox API default of 8006 unless your deployment uses another configured port. The username, realm, and authentication method must match the identity or token you created. Also consider certificate verification as part of the connection setup: enable it when the certificate can be validated, and do not disable it as a first response to a permissions error.
Entity availability has a resource prerequisite as well as an account prerequisite. A Proxmox node without any VM or container does not meet the integration’s stated minimum for entities. Likewise, a node or guest outside the account’s permission scope may not be visible even if other entities load correctly. Check these environmental and scope conditions before rebuilding credentials.
Free tools Windows power users keep installed
One-click scans. No signup required.
Optional: authenticate with an API token
An API token is an alternative to entering the user’s password for the integration. It is optional; the account and its Proxmox permissions still need to be set up appropriately.
- In Proxmox, open Datacenter → Permissions → API tokens.
- Select the dedicated user and enter a token ID.
- Choose privilege separation if you want to assign permissions specifically to the token rather than have it use the user’s permissions without separation.
- Create the token and copy its secret immediately. Proxmox displays the generated secret only once, so store it securely before leaving the screen.
- Enter the token ID and secret in the Home Assistant integration setup.
With privilege separation, token-specific permissions matter: a token may not be able to perform an action simply because the associated user belongs to a group with that permission. Grant the token only the permissions needed for the integration’s intended functions.
Privilege separation is a choice about where the token’s effective access comes from. With separation enabled, plan and assign the token’s own permissions for the capabilities Home Assistant should have. Do not assume the user’s group assignment alone will make every action available to the separated token. Without separation, the token uses the user’s permissions, so the user’s role and path scope remain central to what the token can do.
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.
Keep the token ID and secret distinct: the ID identifies the token, while the secret is the sensitive credential shown at creation. Copy the secret immediately and put it somewhere secure. If you leave the creation screen without saving it, the one-time display means you cannot simply retrieve that same secret later; create and configure a replacement token if needed, then remove the unused credential.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →A token does not make an overbroad role safer by itself. Least privilege still depends on the role, resource path, propagation, and—when privilege separation is enabled—the token’s permissions. Use the token as an authentication option, not as a substitute for reviewing what the integration is authorized to see and do.
Test access by capability, not just connection
A successful connection or working sensor does not prove that the account can perform every action. Verify the behavior you intend to use, and avoid testing unrelated or destructive operations.
- Monitoring: Confirm that expected sensors and binary sensors are present.
- Power actions: If a start, stop, or reboot operation fails, check for
VM.PowerMgmton the relevant VM path or use an appropriate role such asPVEVMUser. - Snapshots: Check for
VM.Snapshotor a role that includes it, such asPVEVMAdmin. - Node updates: If the update entity is unavailable, Home Assistant identifies
Sys.ModifyorPVEAdminas the required permission. - Visibility: If entities are missing, check the permission path and propagation, as well as whether the account can see the relevant resources.
Home Assistant notes that not all Proxmox storage types are fully exposed through the Proxmox API. Missing storage information may therefore reflect API coverage rather than a problem with the account’s role.
Test in layers. First establish that the integration connects and that the expected read-only entities appear. Then test only the power or other control actions you intend to use, on an appropriate guest. If a sensor is present but a button fails, retain the working connection details while investigating that button’s specific permission. This avoids changing host, port, certificate, or password settings when the evidence points to an authorization gap.
Keep the scope of the test aligned with the scope you granted. If permissions cover only selected resources, compare the visible entities with those resources rather than expecting cluster-wide visibility. If the entities you want are within the intended scope but missing, inspect whether the permission path and propagation include them and whether the minimum node-plus-VM-or-container requirement is met.
Troubleshoot when sensors work but controls fail
Read-only entities work, but VM power buttons fail
This usually points to an action-specific permission rather than a bad host, port, or password. Check that the account or, when using privilege separation, the token has VM.PowerMgmt for the affected VM. If you use a built-in role, confirm that it is appropriate for the action and assigned on a path that covers that VM.
Confirm which credential Home Assistant is actually using. With password authentication, inspect the dedicated PVE user and its group role. With a separated token, inspect the token’s permissions as well as its user association; user-level access alone may not authorize the token’s action. If the VM is outside the permission path, adding the action privilege elsewhere will not address the scope mismatch.
Power actions work, but snapshots fail
Snapshot creation has a separate privilege requirement. Check for VM.Snapshot or a role such as PVEVMAdmin; do not assume that permission to power a VM also permits snapshots.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
Keep snapshot access separate from power-management access in your review. A role chosen to enable start, stop, or reboot does not automatically communicate that snapshot creation is intended. Add the snapshot capability only if Home Assistant should be able to create snapshots, and apply it to the relevant resource scope.
The node update entity is unavailable
Home Assistant lists Sys.Modify or PVEAdmin as a requirement for the node update entity. Because these permissions extend beyond read-only monitoring, add them only if you intend to use that entity and accept the resulting access.
Do not grant PVEAdmin simply because the entity is absent. First decide whether node updates through Home Assistant are a feature you actually want. If not, leave the account at its narrower monitoring or control role; the unavailable update entity is consistent with not granting the additional update permission.
No entities appear
Confirm that Proxmox has at least one node and at least one VM or container, then check the account’s access to the relevant path. Also confirm the host, port, realm, and authentication details used by the integration.
If the account connects but still sees no expected resources, review the complete chain: the account is enabled, it is a member of the intended group, the group has the selected role, the permission is on a path covering the resources, and propagation is set as intended. For token authentication, account for privilege separation when reviewing whether the token itself has the required permissions.
Some storage details are missing
Not all storage types are fully exposed through the Proxmox API according to Home Assistant’s integration notes. If other expected entities work and the missing detail concerns a storage type, an account role change may not resolve it. Avoid widening permissions unless the symptom actually indicates an authorization problem.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Remove the integration cleanly
If you stop using the Proxmox VE integration, remove its associated Proxmox permissions as well. Review the group permission, the dedicated user’s group membership, and any API token and token-specific permissions you created, then delete or revoke the integration credentials that are no longer needed.
Removing an integration entry in Home Assistant does not by itself explain which Proxmox access you granted. Clean up the Proxmox side too: remove permissions created for the group or token, remove the service account from the group if it is no longer needed, and revoke or delete the token. If the user was created only for this integration, disable or delete it once no other use depends on it.
Crashes, 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 minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallKeep Home Assistant VM sizing separate from account setup
The Proxmox user configuration does not require additional server hardware or a special Home Assistant subscription. If you are also installing Home Assistant OS as a Proxmox VM, Home Assistant’s Linux installation guidance gives minimum resources of 2 GB of RAM and 2 vCPUs. Those are VM sizing figures, not prerequisites for creating the integration account. Home Assistant also provides a KVM/Proxmox QCOW2 image for installing Home Assistant OS.
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.
That VM guidance is adjacent to, not part of, the account workflow. You can configure the integration credential independently of whether Home Assistant OS is installed as a Proxmox VM, and the 2 GB RAM and 2 vCPU minimums apply to the Home Assistant OS VM context rather than to a Proxmox user or API token.
Frequently Asked Questions
Should I use root for the Home Assistant Proxmox integration?
No. Use a dedicated Proxmox VE user and grant only the permissions needed for your chosen features. Home Assistant recommends a dedicated account rather than broad root access; for an API-focused integration credential, the PVE realm is the recommended choice.
Which Proxmox role is enough for Home Assistant monitoring?
Home Assistant says PVEAuditor is typically sufficient for monitoring and exposing sensors or binary sensors. If you want power controls, snapshots, or node updates, check the extra permission requirements for those actions.
Why can I see sensors but not start or stop a VM?
Monitoring and control use different capabilities. Check for VM.PowerMgmt on the relevant VM path or use an appropriate role such as PVEVMUser. If you enabled privilege separation for an API token, check the token’s permissions too.
Do I need an API token?
No. Token authentication is optional. You can use the dedicated user’s password, or create a token and enter its ID and secret in the integration. If you choose privilege separation, configure permissions specifically for the token.
What happens if I lose the API-token secret?
Proxmox displays the generated secret only once. If you did not save it, create and configure a replacement token, then remove the unusable one; do not rely on being able to retrieve the original secret.
Why are some Proxmox storage details missing?
Home Assistant notes that not all storage types are fully exposed through the Proxmox API, so missing storage information may reflect API coverage rather than insufficient account permissions.
Recommended Free Tools
What does Home Assistant need in Proxmox before entities appear?
The integration requires at least one Proxmox node with at least one VM or container. The account or token also needs access to the resources through its assigned role and permission path.
The Bottom Line
Create a dedicated PVE-realm user, grant it a role suited to the actions you actually want, and scope that permission to the resources Home Assistant should access. Start with PVEAuditor for monitoring; add action-specific permissions only when needed. Password authentication is sufficient, while an API token is optional—if you use one, save its one-time secret and account for token-specific permissions when privilege separation is enabled.
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.
