H100 Failed : another cmd is running
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.H100 Failed : another cmd is running
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi all,
Has anyone else encountered this problem? Our H100 plugs stopped responding to Alexa voice commands about 3 weeks ago. We have tried reinitialising them, but when we get to the point where we switch on the remote control setting, it states "Failed, another cmd is running"
Our plugs are using firmware version 1.2.5
Thanks in advance
Liz
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Good day.
Sorry for delay.
May I know how long have you had the plug and when did the issue start?
And how many plugs do you have and did all of them have the same issue, or just one of them?
Can I have a picture of the product label on the bad plug?
Have you tried the following suggestions:
1) Reset the Kasa device and set it up again.
2) Disable firewall on router and modem. Reboot the router and modem.
3) Change the primary DNS address of the router to 8.8.8.8.
Thank you very much and have a nice day.
- Copy Link
- Report Inappropriate Content
When I had an issue with my plug not responding I reset my Echo device and it started working again. You might try that.
Ryan
- Copy Link
- Report Inappropriate Content
I bought 3xHS110s over the weekend and had the same problem on all three of them. When trying to enable remote control, the app immediately shows the error "another cmd is already running". I tried deleting them from the app then resetting the hardware and starting over but same issue. I also tried adding them via two different phones (one running Android and one running iOS) but same issue on both. I had the same firmware version as you do. I ended up contacting TP Link Tech Support chat and they were not able to help me, they advised to return the devices to the store as they are defective. I ended up doing that...the plugs did work perfectly when controlled via my local network but I really need remote access. I'm wondering if there is a bug with this version of firmware and the current kasa app.
- Copy Link
- Report Inappropriate Content
This happened one of my HS200's. I changed its name within my router and the "another cmd is running" error went away, remote control turned on, and Alexa discovered the device. Rebooting your wireless router may also fix this issue.
- Copy Link
- Report Inappropriate Content
Thanks for your sharing. ^_^
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Try to power cycle it.
And please ensure that the device time of HS100 is correct.
You can try to re-snyc the location and change the time zone to another and change it back to the correct one.
Besides, you can uninstall the app and re-install it or hard reset the plug and reconfigure it.
May it help.
- Copy Link
- Report Inappropriate Content
My stopped working also around 12-29. Reset, re-installed both in Alexa app and Kasa. Both Apps can turn lights on/off, but no voice commands
- Copy Link
- Report Inappropriate Content
Hi, try to change the device name on Kasa app and try voice command again. Check if Alexa app is using the user account. Households account cannot manage the device.
Do you have any other smart products that can be voice-controlled by Alexa? What's the model number, hardware version and firmware of your device?
- Copy Link
- Report Inappropriate Content
@jtc i have the same problem. i had reconnected all my tp link bulbs and sockets, but nothing works in alexa. i had deactivated the skill in alexa, but it was not successful. i always get the error message. sometimes i did not see all my devices in the Kasa App also... it's wired.
- Copy Link
- Report Inappropriate Content
@Nnn what can i do, if i have this problem?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 6549
Replies: 17
Voters 0
No one has voted for it yet.