2018-12-01 21:54:38 WARNING (MainThread) [homeassistant.loader] You are using a custom component for wink which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
Hmmm are you seeing it for the same sensor as before? While I was testing had to delete my .storage directory to get sensor to show up. Which I was okay with because it was a testing instance I use. You could try that?
in the “.storage” folder there are 5 files. I only deleted 2 files where there is a reference to wink.
core.config_entries and core.device_registry. I restarted HA and still there is a same error.
2018-12-01 22:07:53 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/app/homeassistant/helpers/entity_platform.py", line 343, in _async_add_entity
raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: sensor.wink_relay_sensor_temperature. Platform wink does not generate unique IDs
2018-12-01 22:07:53 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/app/homeassistant/helpers/entity_platform.py", line 343, in _async_add_entity
raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: sensor.wink_relay_sensor_temperature. Platform wink does not generate unique IDs
So maybe this is a docker thing. I tested with my test instance like I said which isn’t in docker. I’ll have to test with my real instance tomorrow. It is in docker. I’ll try using the custom component like you and see what happens. My testing was with a full install.
thank you for your time. here is what I did.
I cleared docker container, redownloaded HA - latest, deleted .storage folder which is not inside docker container. I restarted HA but no luck. I will wait for an official fix I guess.
Really weird I can’t get it to work with my docker either. I am pretty confident all is good since I was able to create the problem with my dev instance and then make it go away by applying this fix and restarting. However like I said I did have to delete the .storage directory so that is a bit of a pain. Hopefully that was caused by me doing something wrong and everyone won’t have to do it.
The fix is scheduled for the next hot fix so it should be in 0.83.3