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 minuteCreate a separate Proxmox VE account for Home Assistant, assign it only the permissions needed for your intended tasks, and use that account in the integration instead of a Proxmox administrator or root login. For monitoring, Home Assistant says the built-in PVEAuditor role is typically sufficient. If you also want basic VM power controls, PVEVMUser is a starting point; a narrower custom role may be preferable if it grants more than you need.
The account described here is a Proxmox credential used by the integration. It is not a new Home Assistant household login. The steps below cover account creation, role and scope choices, password or API-token authentication, and what to check when monitoring works but a control action fails.
As an Amazon Associate I earn from qualifying purchases.
Decide what Home Assistant should be allowed to do
Choose permissions based on the entities and actions you intend to use. Proxmox permissions are assigned to a user or group, through a role, at a path in the resource tree. That means both the role and the path matter: a read-oriented role at a broad path is different from a power-control role limited to one VM.
| Intended use | Role or privilege to consider | What to know |
|---|---|---|
| Monitor Proxmox resources | PVEAuditor |
Home Assistant identifies this as typically sufficient for sensors and binary sensors. |
| Monitor and use basic VM power actions | PVEVMUser, or a custom role including VM.PowerMgmt |
The needed power-management privilege is action-specific. Confirm the role’s effective access in your setup rather than assuming that monitoring access also permits controls. |
| Create VM snapshots | VM.Snapshot, or a role such as PVEVMAdmin |
Snapshot creation requires a separate privilege; monitoring or power access alone does not establish it. |
| Use the node update entity | Sys.Modify, or PVEAdmin |
Home Assistant lists this as a requirement for the node update entity. It is a broader permission than read-only monitoring, so grant it only if this function is needed. |
These built-in roles are convenient starting points, not a reason to grant more access than the integration needs. If a built-in role enables unwanted capabilities, create a custom role with the specific privileges required for the actions you plan to use. Proxmox’s administration guide describes access control in terms of a subject (user or group), a role, and a path.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Think of those three parts as separate decisions. The subject determines which account receives access; the role determines which operations it can perform; and the path determines which parts of the Proxmox resource tree the assignment covers. Changing only one part can have a different effect from changing another. For example, using a monitoring-oriented role at a broad path can expose information across many resources while still not granting power controls. Conversely, a role with a control privilege can be scoped to the assets that need that action.
Start with the smallest capability set you can use, then add a specific privilege only when a planned feature requires it. Monitoring, powering guests, creating snapshots, and using a node update entity are not interchangeable permissions. If you do not intend to use a feature, there is no need to grant its extra privilege simply because it appears in a more powerful built-in role.
Create a group and assign its role
Using a group makes the integration’s permissions easier to manage: assign the role to the group, then place the dedicated account in that group. In the Proxmox web interface, use the following workflow.
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 minutePC 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 & 11- Create the group. Open Datacenter → Permissions → Groups and create a group, for example
HomeAssistant. - Assign the group’s role. Open Datacenter → Permissions → Add → Group Permission. Select the group and the role you chose, such as
PVEAuditor. - Choose the permission path. Set the path to
/if the integration should have the selected access across the Proxmox resource tree. Leave Propagate checked when that access should apply to nodes, VMs, and containers below that path. - Save and review the assignment. Before continuing, check that the path, group, role, and propagation setting match the intended scope.
A permission at / with propagation is convenient for cluster-wide monitoring, but it also broadens the scope of that role. If Home Assistant only needs to see selected assets, consider a narrower path and test that the integration can still access every object it needs. Avoid compensating for a scope mistake by giving the account a more powerful role.
The broad path is a convenience, not a requirement for every installation. A narrower assignment can make sense when you want Home Assistant to see only selected resources. The trade-off is that you must confirm the integration can access the node, VM, or container objects it is expected to monitor. If some entities are missing, revisit the path and propagation settings as well as the role; do not assume a missing object automatically means the role itself is inadequate.
Using a group also makes later permission changes easier to reason about: the role assignment is attached to the group, while membership identifies which account receives it. Keep the group dedicated to this integration if that makes its access easier to review. If you later change the intended capabilities, review both the group role and its path rather than adding an unrelated broad permission assignment.
Add a dedicated Proxmox user
- Open Datacenter → Permissions → Users → Add.
- Choose a name such as
hassand select the PVE realm. - Keep the account enabled and set a secure password if you plan to authenticate with a password.
- Add the new user to the group you created, such as
HomeAssistant, and save.
Home Assistant recommends the PVE realm to limit this account to Proxmox API access rather than Linux system authentication and remote SSH access. The integration user is separate from a Home Assistant login. Home Assistant’s user documentation distinguishes a user account from a tracked person; a service or integration account does not need to represent another household member.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
This distinction helps avoid creating the wrong kind of account. The Proxmox user is the credential Home Assistant presents to Proxmox; it does not add a person to the Home Assistant household or change who can sign in to Home Assistant itself. Give it a recognizable name and keep its purpose clear so that its group membership and permissions can be reviewed later.
Connect the account in Home Assistant
- In Home Assistant, open Settings → Devices & services → Add Integration, then select Proxmox VE.
- Enter the Proxmox host name or IP address and the API port. The default port is
8006. - Provide the dedicated Proxmox username and choose password or API-token authentication, according to the credentials you prepared.
- For password authentication, use the username in the
username@realmformat. If the integration flow asks you to choose the realm separately, enter the username in the form requested by that UI; it generally asks for only the username when the realm is selected as the authentication method. - Enable SSL certificate verification when Home Assistant can validate the certificate presented by Proxmox. If verification fails, check the certificate and host name configuration rather than turning verification off without understanding the security trade-off.
- Finish setup, then check whether the expected Proxmox entities appear.
The integration needs at least one Proxmox node with at least one VM or container for entities to appear. If you have just installed Proxmox or have not yet created a guest, an empty entity list may reflect that prerequisite rather than an account problem.
When entering credentials, make sure the authentication method matches the credential type. A password login uses the account and realm; token login uses the token ID and its secret. The host and port identify the Proxmox API endpoint Home Assistant should contact, while certificate verification checks whether the certificate presented for that connection can be validated. Keeping these details distinct makes it easier to diagnose a failed connection without changing permissions unnecessarily.
Optional: authenticate with an API token
An API token is an alternative to entering the account password in the integration. It is optional; password authentication can be used with the dedicated PVE user. If you choose a token, Proxmox can apply permissions to the token separately when privilege separation is enabled.
- In Proxmox, open Datacenter → Permissions → API tokens.
- Select the dedicated user and enter a token ID.
- Choose whether to enable Privilege Separation. Enable it when you want to assign token-specific permissions instead of relying only on the user’s permissions.
- Create the token and copy its secret immediately. Proxmox displays the secret only once; store it securely before closing or leaving the result screen.
- In the Home Assistant integration setup, select token authentication and enter the token ID and secret in the fields provided.
Privilege separation is useful when the token should have a deliberately limited permission set. It does not remove the need to plan the user’s role and scope: configure the effective permissions needed for the token to perform its intended tasks, then test those tasks. Do not treat possession of a token as a substitute for reviewing Proxmox ACLs.
Decide whether you need token-specific permissions before creating the token. With privilege separation enabled, review the permissions granted to the token as well as the account’s group and ACL assignments; otherwise, a token can be correctly entered yet lack permission for an operation. The token secret is not recoverable from the creation screen after it has been dismissed. If it was not stored, create a replacement and update Home Assistant with the replacement credentials rather than guessing or reverting to a more privileged account.
A token is still an authentication credential for this Proxmox integration, not a separate Home Assistant user. Store it as carefully as a password and avoid placing it in notes or configuration that other people or services can access unnecessarily. Whether you use a password or token, the access level is determined by Proxmox permissions, so least privilege still applies.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Check monitoring and control separately
After setup, verify the integration against the capabilities you actually need. First check that sensors and binary sensors appear for the node and guests. Then test only the intended controls, using a non-critical VM or container where practical. Seeing monitoring data does not prove that the account has permission to start, stop, reboot, create snapshots, or perform node updates.
- Sensors and binary sensors: confirm that the relevant node and guest entities are present and have values.
- Power controls: verify the account has
VM.PowerMgmtat the path of the VM or container.PVEVMUseris a built-in starting role for basic power operations. - Snapshots: verify
VM.Snapshotaccess, or a role such asPVEVMAdmin, at the relevant guest path. - Node update entity: verify the
Sys.Modifyprivilege or a role such asPVEAdminif you intend to use this entity.
Use the narrowest role and path that support the required action. In particular, do not upgrade a monitoring account to a broad administrative role merely because one button is denied: identify the missing action privilege and add only what that action requires.
Verification should follow the same capability plan you used when choosing the role. If monitoring is the goal, confirm the expected sensors and binary sensors rather than testing controls you do not intend to enable. If you do need control, test the specific operation with an appropriate guest and check the result. A successful connection or populated sensor list confirms that some access is working; it does not demonstrate that every separate operation is authorized.
For a custom role, make a note of which feature prompted each added privilege. This gives you a practical review point if your needs change: you can remove privileges no longer used rather than leaving a role to accumulate permissions. The same principle applies to scope. A control privilege assigned only where needed can be a better fit than applying a more powerful role across the entire resource tree.
Troubleshoot common setup failures
No entities appear
- Confirm that at least one Proxmox node has at least one VM or container; this is an integration prerequisite for entities to appear.
- Check that the host, port, realm, and credentials in the integration match the account you created.
- Review the group’s role assignment and path, including whether propagation is enabled where access needs to extend to child resources.
- Remember that Home Assistant notes not all storage types are fully exposed through the Proxmox API. Missing storage information is not necessarily evidence that the account has no access at all.
Separate an empty-resource prerequisite from a permissions issue: the integration needs a node and at least one VM or container for entities to appear. If those exist, verify that the intended account is in the group and that the group’s permission is attached to the expected path. A permission at a narrower path can leave some resources outside the integration’s view even when other entities load.
Sensors work, but a button or action fails
This pattern usually points to an action-specific permission rather than a complete authentication failure. Check the privilege required for that operation: VM.PowerMgmt for power management, VM.Snapshot for snapshot creation, or Sys.Modify for the node update entity. Confirm that the ACL applies at the relevant guest or node path. If a broad built-in role is the only way you have found to make the action work, consider a custom role containing the needed privilege instead.
Do not infer that the password or token is invalid simply because one action is denied while sensors continue to work. Authentication and authorization answer different questions: the credential may connect successfully while the assigned role does not permit a particular operation. Identify which entity or action failed, then compare its required privilege with the role and path assigned to the user or token.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Token authentication fails
- Check that you copied the token secret when it was created; it is shown only once. If it was not saved, create a replacement token and store the new secret securely.
- Check that the integration is using the token ID and secret in the token-authentication fields, rather than the account password.
- If privilege separation is enabled, review token-specific permissions as well as the user’s permissions and the resource path. A token created with a restricted permission set may authenticate without having access to a requested operation.
SSL verification fails
When certificate verification is enabled, Home Assistant must be able to validate the Proxmox certificate for the configured connection. Check that the host name or IP used by Home Assistant corresponds to the certificate and that the certificate is trusted in that environment. Disabling verification may bypass a validation error, but it also removes that certificate check; prefer correcting the trust or name mismatch when possible.
Check the exact host value in the integration as part of this diagnosis, because the certificate must be valid for the host Home Assistant is using. A host-name mismatch or an untrusted certificate is a connection-validation problem, not a reason to grant the Proxmox user more privileges.
Recommended Free Tools
Remove the integration’s Proxmox access when it is no longer needed
Removing the integration from Home Assistant does not by itself remove the Proxmox account’s permissions. When retiring the integration, remove the associated Proxmox permissions and credentials as appropriate: revoke or delete its API token if one was created, remove its group membership, and remove the integration-specific group or ACL assignments if they are no longer used. If the account exists only for Home Assistant, disable or delete it after confirming that no other service depends on it.
Review the group and permission assignment as well as the account itself. Removing a user from a group removes that membership, but an integration-specific ACL or token may also need attention. If the group is shared with another service, do not delete it until you have checked what else relies on it. The goal is to leave no unused credential or permission behind while preserving access for any other legitimate service.
Keep Home Assistant VM requirements separate from account setup
The Proxmox user and permission workflow does not require a particular server purchase or a special Home Assistant subscription. If you are also installing Home Assistant OS as a VM, Home Assistant’s Linux installation guidance lists minimum resources of 2 GB RAM and 2 vCPUs; those figures describe the VM installation context, not a requirement for creating the Proxmox integration account. Home Assistant also provides a KVM/Proxmox QCOW2 image for installing Home Assistant OS.
These installation details are useful only if you are also planning the Home Assistant OS guest. They do not change which Proxmox realm, role, path, or authentication method to choose for the integration. The account setup itself is a permissions task and does not call for purchasing hardware or a separate subscription.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Frequently Asked Questions
Which Proxmox role should I use for Home Assistant monitoring?
Home Assistant identifies PVEAuditor as typically sufficient for monitoring sensors and binary sensors. Use a broader role only if you intend to enable actions that require additional privileges.
Can I use the same account to control VMs?
Yes, if you grant the action-specific permissions. VM.PowerMgmt is required for power management, and PVEVMUser is a built-in starting role for basic power operations. You can use a custom role if you want to limit access more narrowly.
Why do sensors work but VM power buttons fail?
Monitoring access does not automatically authorize power actions. Check for VM.PowerMgmt and confirm that the permission applies at the relevant VM or container path. Snapshots and the node update entity have their own additional privilege requirements.
Do I need an API token, or can I use a password?
An API token is optional. You can authenticate with the dedicated PVE user and its password, or create a token and enter its token ID and secret in Home Assistant. If using a token, save its secret when it is created because Proxmox displays it only once.
Should the group permission path be set to /?
Use / with propagation when the selected access should cover nodes, VMs, and containers throughout the Proxmox resource tree. If Home Assistant should see only selected assets, consider a narrower path and verify that it still covers every object the integration needs.
Why are some storage details missing?
Home Assistant notes that not all storage types are fully exposed through the Proxmox API. Missing storage information does not necessarily mean the account has no access at all.
Is this a Home Assistant login account?
No. It is a Proxmox account used to authenticate the integration to Proxmox. It does not need to be linked to a tracked Home Assistant person or represent another household member.
The Bottom Line
Create a dedicated user in the PVE realm, give it a role matched to the features you intend to use, and scope that role only as broadly as necessary. PVEAuditor is typically enough for monitoring; power controls, snapshots, and the node update entity require additional privileges. Verify sensors and actions separately, and remove the associated Proxmox permissions and token when the integration is retired.
Free tools Windows power users keep installed
One-click scans. No signup required.
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.
