-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ & Troubleshooting
Add the integration again or add another profile through the existing integration flow, then place separate cards that point to that profile's sensor entity.
Yes. Convert your historical start dates into YYYY-MM-DD values and use menstruation_cycle.set_cycle_history.
Use menstruation_cycle.export_history for cycle history exports and menstruation_cycle.export_doctor_report when you want an HTML summary. Keep normal Home Assistant backups as well.
Use menstruation_cycle.erase_all_history with an explicit entity_id and erase_all: true.
Yes. Multi-profile use is one of the main design goals. Target automations and cards with the correct entity_id.
HACS is easier because it handles updates and automatic resource registration. Manual installation works, but you must copy the component and register every frontend resource yourself.
Cycle history and related data are stored locally in Home Assistant storage via the integration's storage helpers.
No. Predictions are approximations and the project is not a medical device.
Yes. Use the countdown timer, statistics flows, or call menstruation_cycle.log_product_usage and menstruation_cycle.add_symptom directly.
The integration includes dedicated services and sensor handling for those lifecycle modes.
Usually one of these is true:
- the JS resource is missing
- the browser is using a stale cached bundle
- the card type is wrong
Check the resource list in Installation, then reload the browser cache.
Verify the card type exactly:
custom:menstruation-cycle-cardcustom:menstruation-cycle-compact-statuscustom:menstruation-calendar-cardcustom:menstruation-cycle-history-card-rowcustom:menstruation-cycle-heatmap-cardcustom:menstruation-countdown-timercustom:menstruation-product-inventory-cardcustom:menstruation-statistics-card
Restart Home Assistant and confirm the integration loaded successfully. Services are registered by the backend, so frontend reloads alone are not enough.
Add the daily refresh automation for menstruation_cycle.refresh_cycle_model. Without it, date-based values do not automatically roll forward once per day.
Try this order:
- Hard refresh the page
- Close and reopen the tab
- Clear browser or app cache
- Re-check dashboard resources
One or more resource URLs were probably skipped. Register all 9 card resources, not just the main card.
The legacy custom:menstruation-gauge-card name still exists for compatibility, but new setups should use custom:menstruation-cycle-card.
Exports are written to <config>/menstruation_cycle_exports/ so they remain available inside your Home Assistant environment.
Write one automation per profile when the behavior differs, or use a shared automation that targets all profiles by leaving the refresh service unscoped.
Usually no for normal households, but very dense dashboards render faster if you split daily views and analytics views across separate dashboards.
It becomes more useful after history and product usage data exist. Log a few cycles or hygiene events first.
Initialize it with menstruation_cycle.manage_household_inventory, then set thresholds and update quantities.
Not reliably through the integration. Treat erasure as destructive and keep backups.
Yes, but app cache behavior can lag behind browser behavior after frontend updates, so clearing the app cache may be necessary.
- Use the project for visibility and support, not medical certainty.
- Get explicit agreement before using shared notifications or automations.
- Keep backups if the stored data matters to you.