home-assistant
Invalid authentication for Rituals Perfume Genie
The problem
Rituals Perfume Genie reports invalid authentication:
The same username and password works on the Rituals website and in the Genie iPhone app. I noticed the issue after updating to 2025.12.4, but it may have been present before. The integration worked in 2025.12.0 and possibly .1 through .3.
I don't think it's related to #158213 because that user was running 2025.5.3.
What version of Home Assistant Core has the issue?
core-2025.12.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Rituals Perfume Genie
Link to integration documentation on our website
https://www.home-assistant.io/integrations/rituals_perfume_genie/
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Logger: homeassistant.config_entries
Source: config_entries.py:789
First occurred: 12:30:53 (1 occurrence)
Last logged: 12:30:53
Config entry '[email protected]' for rituals_perfume_genie integration could not authenticate: Auth HTTP error: 405, message='Not Allowed', url='https://rituals.apiv2.sense-company.com/apiv2/account/token'
Additional information
No response
📝 CodeRabbit Plan Mode
Generate an implementation plan and prompts that you can use with your favorite coding agent.
- [ ] Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord or schedule a call!
![coderabbitai[bot] avatar](https://avatars.githubusercontent.com/in/347564?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hey there @milanmeu, @frenck, @quebulm, mind taking a look at this issue as it has been labeled with an integration (rituals_perfume_genie) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of rituals_perfume_genie can trigger bot actions by commenting:
@home-assistant closeCloses the issue.@home-assistant rename Awesome new titleRenames the issue.@home-assistant reopenReopen the issue.@home-assistant unassign rituals_perfume_genieRemoves the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-informationRemove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
rituals_perfume_genie documentation rituals_perfume_genie source (message by IssueLinks)
![home-assistant[bot] avatar](https://avatars.githubusercontent.com/in/97978?v=4 "Published by a pub.dev verified publisher"){kind=small}
Same here HA says "Einrichtungsfehler: Auth HTTP error: 405, message='Not Allowed', url='https://rituals.apiv2.sense-company.com/apiv2/account/token'" and wants the passwort to be entered but then i get a timeout. HA has no connection since 2 hours to the integration. Genie App is working fine
Here we go again...
App is working fine for me in the UK, so it looks like a change Rituals have made on their end (and updated the app to accomodate).
Here we go again...
App is working fine for me in the UK, so it looks like a change Rituals have made on their end (and updated the app to accomodate).
Let's hope not. We finally had a working version, after 15 months.... I'm probably goiing to look into flashing esphome for local control. Getting tired of having my genies as a paperweight in my home.
Is the issue really affecting everyone? I also had a brief outage in Homebridge yesterday.I think the API was temporarily down, but everything is working again today. I don’t have time to check it properly right now, but since both are based on the same API, it should work. Maybe try re-authenticating?
Is the issue really affecting everyone? I also had a brief outage in Homebridge yesterday.I think the API was temporarily down, but everything is working again today. I don’t have time to check it properly right now, but since both are based on the same API, it should work. Maybe try re-authenticating?
Re-authentication runs in the same issue error 405: 'not allowed'. Both stopped around the same time today 12:03 and 12:08 CET.
Previously they have blocked Home Assistant before for to many requests or blocked Homey and as collateral, blocked HA also because they filtered on 'Home'.
Is there anyway we can attention from InsaneSoftware, tag him in this? It seems a serverside issue. The API is blocking Home Assistant again.
@quebulm it affects me aswell, it just did disconnect (not available) and when i deleted the integration and readd it again I'm also getting the 405 response.
Invalid authentication:
InsaneSoftware reacted on the original issue post of last year. It's a rituals side thing, give them a couple of hours and it will be fixed.
But still, I probably will flash my genies with ESPHome to avoid further cloud issues.
https://github.com/home-assistant/core/issues/125437#issuecomment-3680709384
As "a insider of this Rituals Genie Dev team" :
Home Assistant was polling several legacy sensor endpoints that are no longer used by the original application.
We’ve re-enabled Home Assistant access, but temporarily restricted polling of these legacy sensor endpoints only.
On Genie 2.x devices there is a “fill” sensor available; however, with newer scent formulations this sensor has proven to be inaccurate. For that reason, it is no longer used by the original application on 2.x Genies.
In the meantime, we’re reviewing and optimizing these legacy sensors so they can be safely and reliably polled again in the future (but hey christmas times ^^ give us some time )
PS: ESPHome can only work on old devices ^^ Thank the EU for the new encryption law...
