Marjo Wenzel van Lier
1244bffcb4
- Modify sensor and switch setup to use `extend` instead of list reassignment. This prevents overwriting entities from previously processed devices. - Update `OwletBaseEntity` initialisation to correctly store the coordinator instance. - Refine device information retrieval using `getattr` for enhanced robustness and provide more specific device details (e.g., serial number in name). This change addresses a bug where, in setups with multiple Owlet devices, only the entities belonging to the last device in the configuration were registered. Using `extend` ensures all entities across all devices are correctly added. Device information presentation is also improved.
Owlet Custom Integration
A custom component for the Owlet smart sock
Installation
- Use HACS, in
HACS > Integrations > Explore & Add Repositoriessearch for "Owlet". - Restart Home Assistant.
or in the HA UI go to "Settings" -> "Devices & Services" then click "+" and search for "Owlet Smart Sock".
Usage
The Owlet integration offers integration with the Owlet Smart Sock cloud service. This provides sensors such as heart rate, oxygen saturation, charge percentage.
This integration provides the following entities:
- Binary sensors - charging status, high heart rate alert, low heart rate alert, high oxygen alert, low oxygen alert, low battery alert, lost power alert, sock diconnected alert, and sock status.
- Sensors - battery level, oxygen saturation, oxygen saturation 10 minute average, heart rate, battery time remaining, signal strength, and skin temperature.
Options
- Seconds between polling - Number of seconds between each call for data from the owlet cloud service, default is 5 seconds.