Page 1 of 1

Powerview Plugin issue

PostPosted: Sat Jun 06, 2020 3:23 pm
by alang_94526
I have installed Eric Hodel's V1.0.0 Powerview plugin but it doesn't seem to call the API in the hub from the "activateScene" command in powerview.py.
I see the correct scene ID from the debugLog statement in python.py but it seems the call is never made.

In Safari, I can issue the API scenes commands and they work fine.


When I start the plugin, I get the following errors. Not sure if these are relevant to this issue.
Jun 6, 2020 at 2:21:36 PM
Reloading plugin "PowerView 1.0.0"
Stopping plugin "PowerView 1.0.0" (pid 7922)
Stopped plugin "PowerView 1.0.0"
Starting plugin "PowerView 1.0.0" (pid 8072)
Started plugin "PowerView 1.0.0"
PowerView Debug Updating shade 192.168.0.26:48295
PowerView Error exception in deviceStartComm(Door): state value type must be bool, int, real, or string
PowerView Debug Updating shade 192.168.0.26:64316
PowerView Error exception in deviceStartComm(Master 1): state value type must be bool, int, real, or string
PowerView Debug Updating shade 192.168.0.26:43728
PowerView Error exception in deviceStartComm(Master 2): state value type must be bool, int, real, or string
PowerView Debug Updating shade
PowerView Debug Updating shade 192.168.0.26:15484
PowerView Error exception in deviceStartComm(No shade Connected To This): state value type must be bool, int, real, or string
PowerView Debug Updating shade 192.168.0.26:16881
PowerView Error exception in deviceStartComm(Shade 1): state value type must be bool, int, real, or string
PowerView Debug Updating shade 192.168.0.26:31651
PowerView Error exception in deviceStartComm(Shade 2): state value type must be bool, int, real, or string
PowerView Debug Updating shade 192.168.0.26:17365
Error device "Shade 3" state key signalStrength not defined (ignoring update request)
PowerView Error exception in deviceStartComm(Shade 3): state value type must be bool, int, real, or string
PowerView Debug Updating shade 192.168.0.26:62458
PowerView Error exception in deviceStartComm(Shade 4): state value type must be bool, int, real, or string
PowerView Debug Updating shade 192.168.0.26:9307
PowerView Error exception in deviceStartComm(Shade 5): state value type must be bool, int, real, or string
PowerView Debug Updating shade 192.168.0.26:44329
PowerView Error exception in deviceStartComm(Shade 6): state value type must be bool, int, real, or string


All the other setup/config features work as expected.

All shade functions work perfectly through the Powerview App and Siri

Alan

Re: Powerview Plugin issue

PostPosted: Sat Jun 06, 2020 4:19 pm
by alang_94526
Never Mind. I figured out the issue. There is a case sensitivity in the API for scene ID.
sceneid should be sceneId.


Instead of:
def activateScene(self, hubHostname, sceneId):
activateSceneUrl = \
'http://%s/api/scenes?sceneid=%s' % (hubHostname, sceneId)

self.__GET(activateSceneUrl)

It should be:
def activateScene(self, hubHostname, sceneId):
activateSceneUrl = \
'http://%s/api/scenes?sceneId=%s' % (hubHostname, sceneId)

self.__GET(activateSceneUrl)


Works now.
I'm guessing the SW changed somewhere in the hub

Re: Powerview Plugin issue

PostPosted: Sun Sep 27, 2020 8:01 pm
by 7rdr7
Hi Allan,
How did you resolve the issue? I'm experiencing the same issue. Did you modify the code?
Thanks, Ron

Re: Powerview Plugin issue

PostPosted: Sun Sep 27, 2020 8:47 pm
by 7rdr7
Made the change in the plugin code. I could only find a single instance, but I still have the same issue. Is it still working for you?

Re: Powerview Plugin issue

PostPosted: Fri Oct 02, 2020 8:12 am
by 7rdr7
Thanks @chase, Appreciate the fix!

Re: Powerview Plugin issue

PostPosted: Fri Sep 17, 2021 12:47 am
by dawson1331
I believe that the PowerView plugin in the Indigo Plugin Store is an old version/link (2017). This version will not activate scenes. The latest version on GitHub (2018) works. Capitalization issue.

Bill

Re: Powerview Plugin issue

PostPosted: Fri Sep 17, 2021 12:04 pm
by jay (support)
Unfortunately, the developer never created a Github release for any updates. The only one there is from 12/2017 which is what's in the store. He'll need to create a new release in Github then update it in the store for the store to automatically pick up the later version.