Closed Jodifoto closed 3 years ago
@Jodifoto thanks for reporting. Could you update to the latest version of Home Assistant? (2021.3.3). We only support the latest versions, since we target core
with our integration.
@iMicknl, thanks for your answer. I was afraid of loosing my well working (but for me complex) Hassio system (including InfluxDB, Grafana & Mosquitto) inside my Docker on my Synology ... that is why I did not dare to push the upgrade button in the GUI in the past. I hope you understand that I would like to ask 2 questions to you and other experts: -1- is there a risk that things will go wrong & stop working when I push the upgrade button under Hassio Supervisor GUI ? -2- is there a good way to backup before upgrade ... so I can restore in case of problems ? -> PS1: in Portainer I can make an Image of a running docker container ... and I can export this Image to a zip-file <=> is this the way to do it ? & get protection ? -> PS2: an alternative is doing a direct export of a running container to a zip-file in the Docker application on my Synology ... with an ubuntu container I was able to do restore in the past <=> is this the way to do it ? & get protection ?
Best would be to discuss this on the Home Assistant Community forum or on HA Discord.
I am not sure how it is when you run it on Docker on Synology, but always make a backup/snapshot that you can put back.
I will close this issue for now, but feel free to reopen if it wasn't an issue of an HA version that is too old.
Describe the bug I have installed ha-tahoma v2.4.8 and activated debug-logging.
I got no errors and the next results ... where all seems OK:
However none of these devices are available in homeassistant ... AND I got the next notification:
........................................................... Invalid config
The following integrations and platforms could not be set up:
Please check your config.
...........................................................
There are only 5 devices that are coming in ... they are all scenes like "scene.close_all"
I do not know where I can do the suggested "Please check your config".
I did a new Github download, extracted it and copied the tahoma folder again into custom_components + restarted homeassistant. I hope this is the only thing I needed to do ... The results were the same.
PS: I have Homebridge running and the " @dubocr homebridge-tahoma v0.3.71 " plugin to get ALL the devices into HomeKit ... and this works 100% ... the native HomeKit-Tahoma connection does not bring in all my devices. I hope this is not the problem ... if tahoma only supports 1 connection it could be ...??...
To Reproduce I repeated above installation & de-installation several times, with a home-assistant restart after each step & a check on the log-file to see if de-install/install was OK, but always got the same end-result.
Expected behavior I hope that all the items recognized by the plugin (see log-file) also appear in the HA devices list so I can use them.
Screenshots
Environment (please complete the following information):
Device:
Additional context
PS: I have Homebridge running and the " @dubocr homebridge-tahoma v0.3.71 " plugin to get ALL the devices into HomeKit ... and this works 100% ... the native HomeKit-Tahoma connection does not bring in all my devices. I hope this is not the problem ... if tahoma only supports 1 connection it could be ...??...