Sunrise and Sunset sensors not created after upgrading to v3.0.0
kaizersoje opened this issue · 6 comments
After upgrading to v3.0.0, I noticed the sunrise and sunset sensors have not been created. I can only see the integration creates only the following sensors by default.
Same here.
...unless it is now (using your example)
sensor.test_sun_setting
sensor.test_sun_rising
The entity IDs will not be identical to what they were before. If you need the older entity IDs, you can change them from the settings for each entity.
Per the documentation, there are many entities that are created automatically, but most will be disabled by default. If the default set (which is similar to the built-in sun integration) is not what you want, go to the Devices & services page, view the entities for the Sun2 integration, and enable/disable the entities as desired.
I think the OP is not referring to the start of the new entity_id (eg: sensor.sun... becoming sensor.test_sun..., but the end where ...sunset has become ...sun_setting
...at least that's what confused me for a short while!
I think the OP is not referring to the start of the new entity_id (eg: sensor.sun... becoming sensor.test_sun..., but the end where ...sunset has become ...sun_setting
Ah! Well, for various reasons I had to change things up a bit. And for those two, I kind of modeled it after the built-in sun integration. It creates sun_next_rising & sun_next_setting instead of sun_next_sunrise and sun_next_sunset.
@kaizersoje has your issue been resolved? Or do you have further questions?
Yes @pnbruckner