I got the scenes working fairly reliably in Homeseer.
I created virtual devices for each room and added buttons for each scene in the rooms. I set up events to run when "has its value set to" for each scene. The events run single script command:
I also unchecked "Do not update device last change time
if device value does not change:" This is in case the shades are not in sync when scene button is pushed to reflect the change.
PowerView hub has a weak RF signal and despite having a repeater, reliability is sometimes spotty. To counter this, I added wait sec and repeated the URLACTION. I ended up doing three total commands for reliability with one sec pause. I read where some folks did up to ten tries for reliability. Not sure if longer pauses would be better.
You have to figure out what your scene ids are through the api. You can also get a list of scenes, rooms, shades. Names are in base64
- PowerView Scenes - http://(Your IP)/api/scenes?
- PowerView Rooms - http://(Your IP)/api/rooms?
- PowerView Shades - http://(Your IP)/api/shades?
To issue scene command use this
http://(Your IP)/api/scenes?sceneid=(scene id)
Controling individual shades is more complicated. I have it working using Postman sending JSON commands, but I haven't got it going with HS3 scripting.
I created virtual devices for each room and added buttons for each scene in the rooms. I set up events to run when "has its value set to" for each scene. The events run single script command:
Code:
hs.URLACTION("(Your IP)/api/scenes?sceneid=(scene id)","GET", "","")
if device value does not change:" This is in case the shades are not in sync when scene button is pushed to reflect the change.
PowerView hub has a weak RF signal and despite having a repeater, reliability is sometimes spotty. To counter this, I added wait sec and repeated the URLACTION. I ended up doing three total commands for reliability with one sec pause. I read where some folks did up to ten tries for reliability. Not sure if longer pauses would be better.
You have to figure out what your scene ids are through the api. You can also get a list of scenes, rooms, shades. Names are in base64
- PowerView Scenes - http://(Your IP)/api/scenes?
- PowerView Rooms - http://(Your IP)/api/rooms?
- PowerView Shades - http://(Your IP)/api/shades?
To issue scene command use this
http://(Your IP)/api/scenes?sceneid=(scene id)
Controling individual shades is more complicated. I have it working using Postman sending JSON commands, but I haven't got it going with HS3 scripting.
Comment