Glad it is working OK and that the instructions helped. As you may guess, complex LAN structures (like yours) can have issues and that is why the "static IP" address is recommended.
As far as the other problem: It is a issue with the built-in app migration function.
When you reboot, the built-in app looses (oprhans) the migrated devices. Your devices were no longer children of the application.
There is essentially no impact day-to-day operations of the devices.
The work-around is to remove and re-install the devices. BUT THIS IS NOT NECESSARY except in very rare circumstances.
The issue does not impact devices installed with the built-in app (like your EP40 and HS100).
I receive the following when trying to add two new plugs with the built in Kasa integration.
I do still have some devices on the 3rd party integration and get a similar error.
Error: No signature of method: davegut_KasaIntegration.prodVer() is applicable for argument types: () values: [] Possible solutions: println(), println(), grep()
If you check the logs I think you'll see that the device already exists (duplicate IP address.) That was the case for me and I deleted the device and re-added. I also set all 18 of my Kasa devices to have static IP addresses. Sounds the same as my issue above ^^.
I apologize, not too saavy with setting custom attributes.
I am attempting to set pollInterval to 1 minute within a RM rule when a plug turns on, and then after set time change it back to 5 minutes. What am I setting as the parameter type and string value.
Is it string and string value the value is X amount in seconds or minutes?
Using the community app, I need you to run the app again and capture the logs. Send these to me via a Private Message (this is accessible by clicking my icon at the top-left of this message. Instructions
Open a log window
Open the App
Set debugLogging to TRUE (blue)
Run the standard discovery.
copy the logs AS TEXT and PM to me.
Also, provide me with the IP address of you Hub.
Finally, read the installation instructions. It gives some other options for discovery when all else fails (i.e., cloud installation). These can be accessed via a link in the Help screen for the app (accessed from upper right of the app).
That was it. I had forgotten I used two of the plugs for something else temporarily and did not remove them. Remembered when I saw your response. We are back in business. Thanks!!!
Awhile back I had asked about re-ip'ing devices to a new network/subnet. I moved a couple this way (Remove from kasa app, re-add to new network under same name, scan for devices in Kasa integration, check the device I change, etc) and worked fine.
I haven't had a chance to move the rest of my devices, but something changed recently and I'm getting a error when I try now. Here's the log entries with logging on.
I'm guessing I can't do it this way anymore and need to remove the device from hubitat then re-add it? Thinking this is the case I was going to make a virtual switch as a placeholder and use the swap device in apps tool but noticed it doesn't work with any of my kasa devices.
app:8622022-12-03 01:28:41.161 PMerrorgroovy.lang.MissingMethodException: No signature of method: davegut_KasaIntegration.prodVer() is applicable for argument types: () values: []
Possible solutions: println(), println(), grep() on line 336 (method addDevStatus)
app:8622022-12-03 01:28:41.144 PMinfoKasaInt: addDevStatus
app:8622022-12-03 01:28:38.135 PMwarnKasaInt: addDevice: [status:failedToAdd, label:Testplug1, driver:Kasa Plug Switch, ip:10.40.40.106, errorMsg:java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI]
app:8622022-12-03 01:28:38.107 PMinfoKasaInt: addDevices: [selectedDevices: [005F67B1647B]]
Note this is with the built in version of the kasa integration.
I believe the design of the app will cover this. Put the device at the new IP/Port and go to the app and discover either on the new segment or as a manual install. The Software usually updates the IP / port on all devices if they have changed. (Never tested across segments since I do not use these segments.
No luck using the manual method to get it to update either...
From the app interface I get this:
An unexpected error has occurred trying to load the app. Check Logs for more information.
Error: No signature of method: davegut_KasaIntegration.prodVer() is applicable for argument types: () values: [] Possible solutions: println(), println(), grep()
And here's the debug output
...
app:8622022-12-03 08:29:05.332 PMerrorgroovy.lang.MissingMethodException: No signature of method: davegut_KasaIntegration.prodVer() is applicable for argument types: () values: []
Possible solutions: println(), println(), grep() on line 336 (method addDevStatus)
app:8622022-12-03 08:29:05.314 PMinfoKasaInt: addDevStatus
app:8622022-12-03 08:29:02.306 PMwarnKasaInt: addDevice: [status:failedToAdd, label:TestPlug, driver:Kasa Plug Switch, ip:10.40.40.106, errorMsg:java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI]
app:8622022-12-03 08:29:02.280 PMinfoKasaInt: addDevices: [selectedDevices: [005F67B1647B]]
app:8622022-12-03 08:28:55.392 PMwarnKasaInt: manualGetDevices: Kasa device already assigned to 10.40.40.106
app:8622022-12-03 08:28:55.388 PMinfoKasaInt: manualGetDevices: [segment: 10.40.40, addresses: [106], port: 9999]
app:8622022-12-03 08:28:55.387 PMdebugKasaInt: addDevicesPage: [scan: null]
app:8622022-12-03 08:28:52.398 PMinfoKasaInt: manAddDevicesPage
app:8622022-12-03 08:28:44.887 PMinfoKasaInt: starting Kasa Integration
...
I can't emphasize enough that you should NOT migrate to the built-in app at this time. There is an issue where your devices will be orphaned from the built-in app after the migration and any subsequent Hub reboot.
Normal (day-to-day) LAN operations are not impacted.
CLOUD operations will no longer work.
IP and Ports will not be able to be updated (this is handled by the app).
I got everything moved over. I ended up changing the DNI on the old device and adding OLD to the name in hubitat, rediscovering it with the new IP then moved all the in use by stuff over, then removed the old orphaned device.
Hopefully that doesn't break/hurt anything. Everything seems functional, and all devices show Installed: Yes in the integration.
Lastly, should the KP200 outlets be using the Plug Switch driver, or the Multi Plug driver? The old ones were multi, but when they got rediscovered they are using the plug switch one.
to the left of the Kasa Integration).
