-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing unique ID on touchline integration #80900
Comments
@pilehave any comments on this? |
Should be simple to add unique_id to be generated, as pytouchline returns the device ID with get_device_id(). If You are bold enough, I have linked to a new version of climate.py for the component. Be sure to make a backup of the old version to restore if the new one doesn't work ;-) |
awesome. it works. Thanks |
Great! Too bad that the new Touchline units are different from the old ones, regarding the embedded webserver, it would be nice to support them as well. But as I don't have the new one, I can't really do much. |
That would be nice to support the new one as well. But i don't want to buy it before there is support in HA. Do you make a PR on this? |
I have been working on it for a while, ended up putting configuration in a config flow as well as fixing the "unique id" thing. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
The problem
Touchline integration does not generate unique ids as per https://www.home-assistant.io/faq/unique_id
What version of Home Assistant Core has the issue?
2022.10.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
touchline
Link to integration documentation on our website
https://www.home-assistant.io/integrations/touchline/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: