I have used the application for months with no issues, yesterday i keep getting a time out when trying to load a new device.
app:362021-09-26 02:46:45.081 pm errororg.codehaus.groovy.runtime.InvokerInvocationException: java.net.SocketTimeoutException: Read timed out (addDevicesPage)
I'd suggest posting this question on the thread for the app
1 Like
Open the App Edit page and select the Kasa App. On line 551 you will see
timeout: 3,
Change this line to
timeout: 5,
I have noted a slowdown in LAN communications on the current Hubitat Version. I do not know where the issue, but this may fix it for now and I will update the distributed code to fix this and other new timing issues.
Dave
1 Like
Are HE aware of the LAN issues you mention, or is that just your own observation? I have noticed my C-4 running hotter and potentially higher CPU usage, but I have also introduced a reasonable number of changes, so can't attribute this to HE with any confidence.
Tried extending the time out, same issue.
2021-09-26 06:26:22.800 pm errororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_app_davegut_Kasa_Integration_97.pollForIps() is applicable for argument types: () values: [] (pollForIps)
What is the device model/type?
Dave
No, I have no explicit data to support a issue. Would be told to pound sand.
I concur though. I am a novice who has tinkered for many years
But my system is running very slowly.
Not sure if this helps but the app is working again and Hubitat is responding much quicker than before. Appreciate the quick responses
1 Like
Yeah I'm certainly not proposing raise an issue with support, was just interested if anyone else had. I fully expect my experience is self inflicted, or potentially a combination, but should get my own house in order before looking elsewhere for improving performance.
The error message from your latest response is indicative that you are not on the current application / driver version set. This is indicated by the error for no method "pollForIps". For this to occur, it would have to call the method somewhere. The method is not called from any of the current applications/drivers and is not in the current application.
What is the version of the Application (it is on the start page).
For your devices, what is the driver version (in the data section on the device edit page.
Have you set "use Kasa Cloud" in the app? If so, the password may have expired. Reset this and try again. I need to know this.
Once I have that, there is a possibility I can assist.
Version 6.3.2
Driver & App
What was the device type/model?
I must ask, have you completed to install via the Kasa phone application? (has happened before)
What were the app setting for the following:
- Use Alternate Lan Segment (True=blue/False)
- If True, Alternate Lan Segment. (This should be NNN.NNN.NN, example: 192.168.55).
- Interface to Kasa Cloud (True/False)
- If true, recommend you run "Kasa Login and Token Update"
Yes I used Kasa first. Never had the issue before and I love the app thank you. Yes both the above are true. Ran the token update, Back to the same error.
app:362021-09-27 03:12:09.901 pm errororg.codehaus.groovy.runtime.InvokerInvocationException: java.net.SocketTimeoutException: Read timed out (addDevicesPage)
app:362021-09-27 03:12:04.447 pm info[KasaInt/6.3.3]: cloudGetDevices 9003d5c6-ATMTKfRLd7eN5gSO4r2eyJs
Kasa Smart Plug HS103P4
Installed into Kasa via iPhone Software 15
Used alternate LAN segment and ran the kasa login and token update. This error is happening on my Mac mini, I'll install a new plug later via my iPhone and try the app there to see if it has the same error.
Try setting "interface to Kasa Cloud (True/False) to FALSE. The error is in the cloud communications and is failing to allow carryover. If you rely on cloud comms, you can set Interface to Kasa Cloud after the install.
I will fix in a future version if this works.
Dave
One other item. You could try to change line 333 of the app from
def cloudUrl
to
def cloudUrl = ""
This change came about due to nuances in the latest Hubitat release. (I was probably violating something and they tightened the rules.)
I added a new plug to Kasa app using my iPhone and then using the HE app via the phone was able to load it straight away. Did the same thing using and iPhone then the Mac mini and that also worked. So from a novice as I am I would say there is something going on with the Kasa Server and the issue is not on your side.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
