HS103 (v5) and HomeAssistant not working
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I've got 30+ TP-Link smart home devices and basically everything is integrated to HomeAssistant, with the exception of this ONE plug (and some of the new homekit plugs I have).
I use Homekit for everything, and HomeAssistant does a great job integrating TP-Link plugs and switches.
I tried a TP-Link support ticket, but they sent me info on how to link it to google assistant.
On HomeAssistant forums, it appears they at one point changed the firmware to not provide for direct access from HomeAssistant, but that you could request compatible firmware. Does anyone have any info on this?
This one is an HS103 v5, with firmware 1.0.3 and works fine via the app and internet, but just won't show up in HomeAssistant like all the other ones do.
If you're wondering why this is in the bulbs forum, I tried posting it in plugs but the system told me the HS103 needs to be posted in plugs and bulbs.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Well, I just got it and learned something new perhaps.
Most of the integrations I have, have some customization, but the TP-Link integration only lists the devices and the ones it knows about, you can configure.
So I tried adding another instance of the integration (or so I thought) and it asked me to put in an IP address. When I added that IP, it found the device and works fine now.
I guess maybe they just need to document the integration better, and perhaps update the UI for it in HomeAssistant. Glad it is now working!
- Copy Link
- Report Inappropriate Content
So the information that was pinned on the home assistant site and can be found on our forums regarding removing home assistant compatibility, is only in relation to one specific region of one model of smart plug. There was a security flaw identified in the HS100/110 for the UK versions that required the local communication of the device to be patched out. US versions of the plug were unaffected.
This is interesting in that all of the warnings that were placed throughout the Home Assistant Documentation and references to the HS100 not being able to have local control have been removed, and the HS100 is placed on the compatible device list. I am now curious if the integration has found a way to regain local control of the device, even though I find it unlikely; or if this is just in reference to the more common US version being compatible with HA.
I would honestly double-check that the device version in the app is matching the device version on the label, as this might cause confusion when in discovery. Are you able to setup the device manually using a static IP instead of using the discovery method?
- Copy Link
- Report Inappropriate Content
@Riley_S That's interesting. I didn't realize it was just that one device. I came across that topic when searching for the HS103.
The stuff I have integrated right now is all set up using static DHCP reservations, so they have basically static IPs, and then in my configuration.yaml, I have stuff like this:
tplink:
discovery: false
switch:
- host: 172.29.11.66
- host: 172.29.11.67
- host: 172.29.11.68
strip:
- host: 172.29.11.55
- host: 172.29.11.160
dimmer:
- host: 172.29.11.89
- host: 172.29.11.165
I did try turning discovery to true a couple weeks ago, but maybe now that I've done a full reset and have the device with me, I will try that again. What I was hoping was that I could find some firmware that would fix it, but maybe you're right and it's something else. I have a few Tuya devices as well, that use cloud integration, and that works ok. But the local control stuff with TP-Link is so nice and fast. HomeAssistant integration is the "Must Have" thing, for me. Although I do like that the homekit plugs that TP-link has now work natively, so I've bought a couple packs of those as well.
I'll keep playing with it, but maybe there's more that I need to add to the config to get this thing happy.
Thanks for replying!
- Copy Link
- Report Inappropriate Content
Well, I just got it and learned something new perhaps.
Most of the integrations I have, have some customization, but the TP-Link integration only lists the devices and the ones it knows about, you can configure.
So I tried adding another instance of the integration (or so I thought) and it asked me to put in an IP address. When I added that IP, it found the device and works fine now.
I guess maybe they just need to document the integration better, and perhaps update the UI for it in HomeAssistant. Glad it is now working!
- Copy Link
- Report Inappropriate Content
I have had a few brands of devices in my personal setup that don't like to be discovered naturally by HA, in almost all theses situations the device can still be added using its IP.
If I am remembering correctly, it was only like 4 or 5 months ago when Home Assistant started allowing/encouraging the setup of multiple integrations for one brand. The community devs for the integration just may have not updated their code for the newest HA interfaces.
Glad you were able to get it working.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2376
Replies: 2
Voters 0
No one has voted for it yet.