I’ve just done the update again with the yaml removed first, and there’s a lot less duplicates this time. A few items need some tweaking, but it’s in a much better state than before. There’s still a few of the Android ones, but I need to hunt those down as they might be in the router.
My other “issue” is I have a fritz repeater as well as a fritz box (as a mesh network), so this time I’ve just put the repeater integration to ignore or else I think I’ll get even more duplicates. But I still have a few devices (a couple of Pi’s and my iPhone) which have 2-3 devices, only some of which work.
of course, I was also responding to the second sentence I quoted. It may be deprecated, or phased out, but we don’t do ‘everything’ through the UI just yet.
Since the integrations still using the known_devices.yaml hold many of our ‘presence detectors’, this is a statement that needs some dedicated precision.
Yep, I feel like people are trying to argue semantics here. It’s been almost 3 years since the announcement. Continue to use known_devices at your own risk but it can be ripped from your grips whenever the integrations get updated into the UI. It’s not a planned deprecation where it’s dead 2 weeks from now. It’s planned as in “We’ll remove it when we update the integrations that use it”.
Maybe but until the integrations using it are migrated it’s still current and not deprecated even if being phased out… If 10 integrations used it and 8 have been migrated it’s being phased out but still current - not deprecated - for the other 2.
sure. but still… there’s much confusion over the term deprecated, and it seems to be taken as ‘no longer in use’, where ‘being phased out’ decribes the process more accurately.
@DavidFW1960 exactly. And even though I learned Petro’s thesaurus explanation in school, (some moons ago…), I also learned computer programmers can be thinking more from a digital perspective than their end-users who tend to use a more humane perspective
Now who needs to adapt here
btw, what’s the incorrect depreciate doing there, that’s a mistake being made here too, quite often to be honest. I am somewhat amazed it’s listed in the thesaurus?
this is a bit odd don’t you think? Who would be editing a known_devices.yaml, if it would be no longer used by the system. That would be pointless, and have no effect in the system at all.
Until then, it is created by the system, and we need to maintain it, because it is used. In my config by 129 devices…hardly semantics.
It’s not odd, that’s literally what the announcement was back in (apparently) 0.94… don’t shoot the messenger. Long term, that file will be no longer in use.
I like the mutesync integration, sounds better than my current scripting work-arounds. When I want to Download and execute this it reported by windows defender as “blocked because it could harm your device”, is it actually safe to download this?
(i cannot find any info on the HA forum or google on this)
Or when the devs say “2 more months only, then its right out the door”.
Then maintainers who aren’t paying attention or no longer care will miss the deadline. Users will rant and moan that the devs broke their system and that “this is the worst release ever”, “you stopped caring about users” and “I’m gonna move to smartthings” or “time for a fork”.
since the update the boolean sensors provided by the sure petcare integration to indicate when my cats arrive/leave via the catflap have stopped working… they appear ok but there are no updates
I think it fails on the SSL-sertificate.
To make it work you have to have ssl: false in your motionEye addon config.
You also have to set a port to your web-interface in the same place.
Then use http://ip:port in the integration configuration. You can also use the hostname (a0d7b954-motioneye) here.
I found that it gives an error if you have blank passwords, so you should probably make them.
I never told you to remove it. I wasn’t even talking to you. I was talking to the people who use Fritz box. You you and Others decided to bring me into a deprecation argument. Do whatever you wanna do, I don’t care.
