Whats home assitant and Tplink big bleeping problem with each other.?

Install and setup home assistant without any issues and after setup add the devices.

It finds my pfsense router
Roku tv
plex
Smart-life devices
Heck it even finds my printer

But it flat out refuses to see anything tplink related and even adding the devices to the config.yaml doesn’t work.
It keeps saying invalid config and direct me to the tplink resources. but everything looks as it should.

tplink:
discovery: false
lights:
- host: 192.168.1.116
- host: 192.168.1.67
switches:
- host: 192.168.1.68
- host: 192.168.1.160
Plugs:
- host: 192.168.1.142
- host: 192.168.1.11
- host: 192.168.1.118

First off please properly format you code snippets when posting them to the forum. We can’t help you fix syntax errors if we can’t see the syntax as it is in your actual code.

but…

Have you looked at the docs for tplink? According to that there is no “Plugs:” option. And if there was it wouldn’t be capitalized anyway.

And also note if you have devices on the list that are known to be supported.

Everything i have is in the supported device list.

I had already mentioned i got sent to the Tplink resources .

Before commenting next time it may be a good idea to actually glance at those resources since the very first thing in supported devices is plugs.

That’s not a copy of the code but rather from a word document but i see the confusion and i even posted the wrong one as i already removed the plugs from the list and listed all them as switches.

Of course this didn’t fix anything as it still flat out refuses to see anything tp link related.

Right, but Plugs: isn’t a valid configuration option (as finity said). That’s what they were talking about.

Anyway, please post your actual code for tp-link properly formatted (three backticks above and below the code) along with the error in your logs related to it.

There is no error log other then invalid config and that because the resources are out of date it turns out which happens on every project.
Already figured out where the change was and fixed it so they show.

Auto discovery is broken for Tplink i would guess due to Tplink changing something again.

I am also confused as to why people keep referring to editing the config as code when its got little to do with it. Maybe referring it to format would make a lot more sense and cause less confusion.

Thanks for the help.

Developer tools > logs should have more information on the invalid config error. Definitely submit an edit to the docs if you found something that’s incorrect, it’s always appreciated.

YAML is indentation sensitive, so seeing the code properly formatted is important for troubleshooting. What are you confused by?

The log was empty regarding tp link which was frankly confusing as i already looked.

Why its confusing is that adding a few words and some ip’s to a config is stretching the term coding paper thin at best.
But that’s just splitting hairs and is merely terminology so call it as you wish.

Although in the future if this is to become more user friendly the documentation needs to be done in a way that a laymen going to understand easily and using wording a coder or engineer would understand doesn’t translate so well.

Why its confusing is that adding a few words and some ip’s to a config is stretching the term coding paper thin at best.
But that’s just splitting hairs and is merely terminology so call it as you wish.

Sure, “code” is often loosely used here to refer to YAML, but I think you could figure that out by context. I’m actually not sure when I started saying code instead of YAML though, so perhaps I’ll switch back.

Although in the future if this is to become more user friendly the documentation needs to be done in a way that a laymen going to understand easily and using wording a coder or engineer would understand doesn’t translate so well.

Again, feel free to submit some edits to the documentation. I’ve made multiple edits before for things that were unclear.

But you didn’t say that you actually looked at them. And since you had some extraneous keys in your code then I think it was probably a fair assumption that you didn’t.

Maybe before being crappy to me for voluntarily trying to help you:

  1. you should look at the community guides for how to properly post your code so we can see the syntax. that guideline isn’t there just to annoy you and make me ask you for no reason. If the actual code in your config isn’t formatted properly then it will give you and invalid config error even if all the devices are supported. If I can’t see your actual copde syntax then I can’t help you effectively troubleshoot your problem.

  2. If you look at the “code” you posted then you have to forgive me for assuming that you actually had the word “Plugs:” in your actual code. And that would have also given you an invalid config error. So, again, I didn’t mention that just to waste my time and yours. Based on what you posted it was a valid reply my me.

  3. The reason I sent you back to the docs (in addition to the reasons above) is that at the bottom there are the actual valid config options (Plugs isn’t included) along with examples showing how your config should properly look…including syntax (indentation & formatting).

And how exactly was I supposed to know that? Am I a mind reader? All I can do is respond to the information I’ve been given. No need to get crappy with me because you failed to give me correct information.

Maybe you ought to be a good community neighbor and post what you found actually worked in case anyone else happens to come across this thread in the future and has the same problem.

Not to mention I’d like to see how your final working config differs from the “out of date” docs.

I guess I don’t know what there is an issue with calling it “code”.

Besides, we call it code so as they say “when in Rome…”

If HA is too complex for some people then there are multiple commercial dumbed-down apps that those people can use. The benefit of HA is that it’s a lot more flexible and powerful than those dumbed-down solutions and with that flexibility comes inherent complexity. learning how to run/code the software is part of the trade-offs to using this system. Again, if that’s too much to ask then there are other solutions.

1 Like

You know that this is a community driven project: see that Edit link on the tplink integration page? Please consider using it. Yes the documentation could be better. No it doesn’t do it itself.

And bugs don’t fix themselves either. The author of this particular piece of code may not know it is broken (if indeed it is). Please post an issue here Issues · home-assistant/core · GitHub

And in future if you want to see more logs, take a look here Logger - Home Assistant - you can get a good deal more information by upping the logging level.

Ignore anything i typed as its turns out i was having a stroke at the time and became a argumentative dick before passing out.

I apologize to anyone i may have insulted lord knows i don’t remember much but she tells me i was a ass lol.

Thankfully it was a TIA and no major lasting damage but it was a warning so its blood thinners form now on.
Beats the hell out of the other option…

1 Like

Good lord, I am very sorry to hear that, and I hope nothing any of us said made your situation any worse.

All the best with your health and your ongoing home assistant adventure (although more so the health!)