tnmendes / watt

iOS App for TP-Link Devices (Kasa Smart & Tapo) | Support page for issues related to Watt iOS App
49 stars 4 forks source link

Fail to togle switch, The operation couldn't be completed. (Watt_for_S-mart_Devices.RequestError error 8.) #113

Closed Bogey closed 1 year ago

Bogey commented 1 year ago

Controlling the P100 still works with native Tapo app, Home app and Homebridge. Unfortunately an error with Watt: Fail to togle switch, The operation couldn't be completed. (Watt_for_S-mart_Devices.RequestError error 8.)

IMG_0728

The error occurs with just switching on/off of the “Garageplug”. I tried deleting app, clearing plugs, reinstalling app, etc. Nothing fixed it.

tnmendes commented 1 year ago

Thanks for reporting this bug, I'll look into it!!!

tnmendes commented 1 year ago

Hi, I already made a Hotflix to solve this problem with the Tapo device toggle. The app has been submitted to the Apple AppStore review team and now it can take between 12 hours to 48 hours to be available! Sorry for the inconvenience

tnmendes commented 1 year ago

The hotfix is already available for iOS/iPadOS with version (5.1.2) The MacOS version is still on Apple's review

Bogey commented 1 year ago

Thank you! Yes, I noticed Watt working as before this morning :)

I do have a request for Watt: I use it with my iPhone's Automation app and I want to check if the plug is plugged in. So not if it's on or off (it can already do that) but if it's powered at all. Is that possible?

mickstone commented 1 year ago

I'm also having similar issues with TPlink HS100. Siri shortcuts no longer work even after recreating them. Watt still works if I manually trigger actions, but shortcuts refuse to work.

tnmendes commented 1 year ago

Hey

@Bogey using Siri shortcuts with Watt you can check the "Device Status" and the result is a number (Double) with the consumption, if is higher than zero you can know that it is connected (I don't know if that answers your question).

tnmendes commented 1 year ago

@mickstone are you getting some error messages from the Siri shortcuts? Are you just giving voice commands or running directly from app shortcuts?

mickstone commented 1 year ago

Running from shortcuts created by Watt in the shortcuts app. image

mickstone commented 1 year ago

It worked perfectly until the recent update.Sent from my iPhoneOn 10 Jun 2023, at 11:56 pm, Tiago Mendes @.***> wrote: @mickstone are you getting some error messages from the Siri shortcuts? Are you just giving voice commands or running directly from app shortcuts?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Bogey commented 1 year ago

Hey

@Bogey using Siri shortcuts with Watt you can check the "Device Status" and the result is a number (Double) with the consumption, if is higher than zero you can know that it is connected (I don't know if that answers your question).

Yep, that's what has been working, but not anymore. In this case it should go take the 'Otherwise' route and show just a notification that my iPad is charged. IMG_0729

tnmendes commented 1 year ago

A new version of Watt (v5.1.3) is available, can you install it? This version will show more details on shortcut error

mickstone commented 1 year ago

I’ve installed the new version and this is the error I get when I try to run the Siri shortcut that Watt creates.Noting that if I use Watt directly it works okay and can control my HS100, just not via the shortcut.Sent from my iPhoneOn 10 Jun 2023, at 11:56 pm, Tiago Mendes @.***> wrote: @mickstone are you getting some error messages from the Siri shortcuts? Are you just giving voice commands or running directly from app shortcuts?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

mickstone commented 1 year ago

Posting the error as it didn't make it via email

image

Bogey commented 1 year ago

Yeah!! That works. Thank you 🙏

tnmendes commented 1 year ago

That is great @Bogey !! Hey @mickstone can you delete the shortcut that is not working and then go back to the Watt app and add again the Siri shortcut directly from the Watt app?

mickstone commented 1 year ago

I have done so multiple times with no change to the behavior.

tnmendes commented 1 year ago

Hey @mickstone let's move this conversation to email, can you send me an email to voless.app@gmail.com with a print screen with details of the shortcut that is not working and also a print screen of the device? Example: IMG_92F3134BB92E-1

IMG_B310F1613222-1

I'm going to close this issue because the error with which this thread was opened is already resolved

Bogey commented 1 year ago

Tiago meant sending a regular email, NOT replying on the Github email 😉

mickstone commented 1 year ago

Ah yes, I see I didn't read the instructions properly. Hopefully no damage done.

I deleted my post.

Bogey commented 9 months ago

Hey @Bogey using Siri shortcuts with Watt you can check the "Device Status" and the result is a number (Double) with the consumption, if is higher than zero you can know that it is connected (I don't know if that answers your question).

Yep, that's what has been working, but not anymore. In this case it should go take the 'Otherwise' route and show just a notification that my iPad is charged. IMG_0729

@tnmendes Tiago, I'm afraid the old 'bug' has found it's way back in with the last iOS update.

Bogey commented 9 months ago

It's a little different than above. When I check the status of the Tapo 100 then it reports back the power status of when it was last online. However, when I "pull the plug" (take the Tapo 100 out of the power socket) the status still is 'yes'.

ErwinEdx commented 9 months ago

Nevermind, I have this fixed by checking for 0 instead of checking for > 0 and by swapping the if clauses.

tnmendes commented 9 months ago

Great to hear you managed to solve it. (A small aside, sometimes the device has been unplugged but for a few minutes the TP-Link servers will say that it is still connected, is a cache issue related with TP-Link servers)