Xiaomi sensors via deconz
If not language, then perhaps the card you are using. For example, Iâm using the standard entity card and it correctly shows Open/Closed for doors and Detected/Clear for motion.
1 Like
Hi Fabio,
Yes I could read that, but it just shows an example beneath that looks like it is still possible to implement this manually?
Very fair, I just tested. I will seek in this direction. Thank you.
The problem is from lovelace-multiple-entity-row
Yes, but not anymore in sensor, itâs in config now
ok thanks Franck, good to know this is as intended. Though persons is a bit surprising talking about Z-wave 
and still listed:
and I can reload them, just like the zones, which arenât listed btw, and not available on the system either:
one more âanomalyâ: Sonos canât be dismissed and upon each restarts is being discovered and notifying persistently:
Not all reload capabilities are available via the UI yet. This is an open issue/task.
However, the reload services are available.
Person can be loaded up as a dependency of: default_config, device_sun_light_trigger, mobile_app or onboarding
(Please note, that those in their turn can be a dependency of another integration)
That will be addressed in 0.110, where we changed a large part of the way discovery works. Furthermore we have enforced ADR-0011, which requires discovered items to be ignorable.
6 Likes
sorry, youâre right, and I should have mentioned I dont have these setup, my configuration.yaml is edited manually.
So maybe only âonboardingâ would cause the integration to be there, though one wouldnât expect that.
Maybe some short explanation I this regards could be added to the main docs, stating integration to be listed/used, without actual devices/entities of that integration being alive on the system.
Iâm not sure what the added value of that would be. But that is a personal opinion.
Okay - thanks man!
well, if I may, a listing is of value if the people checking the list understand its workings. Ive long had a python script and templates showing me which integrations and components live on my system.
I was pleasantly surprised when this started to become available in Ha by default. Now this list is also starting to show other integrations I dont use, have installed, or even recognize to be related to my system, the whole list is becoming more of a mystery to me than it is of added valueâŚ
A small explanation could mitigate that 
example from my main system, showing only available items:
1 Like
Just updated and my tellstick wont load anymore⌠Service calls seem to be working though. I get current values in the log when I fetch sensors. I get this:
Log Details (ERROR)
Logger: homeassistant.setup
Source: components/tellstick/__init__.py:112
First occurred: 5:34:17 PM (1 occurrences)
Last logged: 5:34:17 PM
Error during setup of component tellstick
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 175, in _async_setup_component
component.setup, hass, processed_config # type: ignore
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/tellstick/__init__.py", line 112, in setup
tellcore_devices = tellcore_lib.devices()
File "/usr/local/lib/python3.7/site-packages/tellcore/telldus.py", line 173, in devices
count = self.lib.tdGetNumberOfDevices()
File "/usr/local/lib/python3.7/site-packages/tellcore/library.py", line 257, in check_int_result
raise TelldusError(result)
tellcore.library.TelldusError: Could not connect to the Telldus Service (-6)
I just installed 0.109.1
Broadlink for my broadlink M3 mini is working again
1 Like
Integrations do not have to provide entitiesâŚ
My Tellstick-issue was resolved when I removed the deprecated unifi-component from my yaml. I understand that it is configured through the UI now. Dont understand why it disturbed the tellstick component tho. Anyways, happy now 
Does it even go through configuration validation? When I added this in the same format as you did, i got error message after validation:
Invalid config for [synology_dsm]: [platform] is an invalid option for [synology_dsm]. Check: synology_dsm->synology_dsm->2->platform. (See /config/configuration.yaml, line 573).
So I did used the old format, just changed integration name to new:
- platform: synology_dsm
host: 192.168.52.21
username: xxxx
password: yyyy
but this does not seem to work, both my units seem to be discovered, but only one goes through complete configuration process.
BTW Iâm not sure if all of your options are valid for changed integration. According to documentation now only host, port, ssl, username, password, volumes, disks are valid options and monitored_conditions are discardedâŚ
Its not just tuya covers, I am using MQTT cover and I have the same problem - up/down arrow greyed out.
It doesnât matter if I set optimistic mode true/false or whether I use state topic or not, up and down arrow are always greyed out.