Where is in the app ? I dont see such an option
Hi, I tried to install your package via HPM with the URL you provided but it wants to install "null" which of course results in nothing showing up when installed even though it is installed. Can you advise on how to best install? Thanks for all your hard work on this, amazing.
EDIT: I think I got it figured out but it seems to be stuck on obtaining firmware version.
I've got a Gen3 Hub that I've now got working with your Gen3 App, and it seems to be working great. I've got a few automations built around it - and thus far, it's been able to handle everything I've asked it to do (next up is to move the scheduled events off of the Hunter Douglas App and into Hubitat).
I was poking around tonight though, and noticed that it seems my eventstream is continually connecting/disconnecting, so I set up a rule to create a log trigger on each of these events - and have noticed the following:
[app:382](http://hubitat/logs#)2024-12-14 10:22:39.014 PM[info](http://hubitat/logs#)Hunter Douglas Status has changed - 2024-12-14 & 10:22:38.861 PM To connected
[app:382](http://hubitat/logs#)2024-12-14 10:22:39.001 PM[info](http://hubitat/logs#)Triggered: Hunter Douglas PowerView Shade SSE Gen3 reported eventStreamStatus(connected) *changed*
[app:382](http://hubitat/logs#)2024-12-14 10:22:38.911 PM[info](http://hubitat/logs#)Event: Hunter Douglas PowerView Shade SSE Gen3 eventStreamStatus connected
[app:382](http://hubitat/logs#)2024-12-14 10:22:27.866 PM[info](http://hubitat/logs#)Hunter Douglas Status has changed - 2024-12-14 & 10:22:27.798 PM To disconnected
[app:382](http://hubitat/logs#)2024-12-14 10:22:27.851 PM[info](http://hubitat/logs#)Triggered: Hunter Douglas PowerView Shade SSE Gen3 reported eventStreamStatus(disconnected) *changed*
[app:382](http://hubitat/logs#)2024-12-14 10:22:27.830 PM[info](http://hubitat/logs#)Event: Hunter Douglas PowerView Shade SSE Gen3 eventStreamStatus disconnected
[app:382](http://hubitat/logs#)2024-12-14 10:22:19.795 PM[info](http://hubitat/logs#)Hunter Douglas Status has changed - 2024-12-14 & 10:22:19.726 PM To connected
[app:382](http://hubitat/logs#)2024-12-14 10:22:19.781 PM[info](http://hubitat/logs#)Triggered: Hunter Douglas PowerView Shade SSE Gen3 reported eventStreamStatus(connected) *changed*
[app:382](http://hubitat/logs#)2024-12-14 10:22:19.759 PM[info](http://hubitat/logs#)Event: Hunter Douglas PowerView Shade SSE Gen3 eventStreamStatus connected
[app:382](http://hubitat/logs#)2024-12-14 10:22:08.735 PM[info](http://hubitat/logs#)Hunter Douglas Status has changed - 2024-12-14 & 10:22:08.669 PM To disconnected
[app:382](http://hubitat/logs#)2024-12-14 10:22:08.722 PM[info](http://hubitat/logs#)Triggered: Hunter Douglas PowerView Shade SSE Gen3 reported eventStreamStatus(disconnected) *changed*
[app:382](http://hubitat/logs#)2024-12-14 10:22:08.700 PM[info](http://hubitat/logs#)Event: Hunter Douglas PowerView Shade SSE Gen3 eventStreamStatus disconnected
[app:382](http://hubitat/logs#)2024-12-14 10:22:00.689 PM[info](http://hubitat/logs#)Hunter Douglas Status has changed - 2024-12-14 & 10:22:00.607 PM To connected
[app:382](http://hubitat/logs#)2024-12-14 10:22:00.679 PM[info](http://hubitat/logs#)Triggered: Hunter Douglas PowerView Shade SSE Gen3 reported eventStreamStatus(connected) *changed*
[app:382](http://hubitat/logs#)2024-12-14 10:22:00.648 PM[info](http://hubitat/logs#)Event: Hunter Douglas PowerView Shade SSE Gen3 eventStreamStatus connected
What's curious is that when I went into the Device and enabled logging, it seemingly stablizied.
[dev:499](http://hubitat/logs#)2024-12-14 10:22:39.251 PM[debug](http://hubitat/logs#)parse: 100 HELO
[dev:499](http://hubitat/logs#)2024-12-14 10:22:39.163 PM[debug](http://hubitat/logs#)setEventStreamStatusToConnected()
[dev:499](http://hubitat/logs#)2024-12-14 10:22:39.152 PM[debug](http://hubitat/logs#)eventStreamStatus: START: EventStream Started
[dev:499](http://hubitat/logs#)2024-12-14 10:22:39.097 PM[debug](http://hubitat/logs#)eventStreamStatus: STOP: EventStream Stopped
[dev:499](http://hubitat/logs#)2024-12-14 10:22:38.897 PM[debug](http://hubitat/logs#)eventStreamStatus: STOP: EventStream Stopped
[dev:499](http://hubitat/logs#)2024-12-14 10:22:38.862 PM[debug](http://hubitat/logs#)doSendEvent(eventStreamStatus, connected)
[dev:499](http://hubitat/logs#)2024-12-14 10:22:38.845 PM[debug](http://hubitat/logs#)setEventStreamStatusToConnected()
[dev:499](http://hubitat/logs#)2024-12-14 10:22:38.840 PM[debug](http://hubitat/logs#)eventStreamStatus: START: EventStream Started
[dev:499](http://hubitat/logs#)2024-12-14 10:22:37.142 PM[debug](http://hubitat/logs#)Connecting to event stream at 'http://192.168.80.141:80/home/shades/events'
[dev:499](http://hubitat/logs#)2024-12-14 10:22:37.132 PM[debug](http://hubitat/logs#)connectEventStream()
[dev:499](http://hubitat/logs#)2024-12-14 10:22:37.079 PM[debug](http://hubitat/logs#)initialize()
[dev:499](http://hubitat/logs#)2024-12-14 10:22:37.075 PM[debug](http://hubitat/logs#)updated()
After the 15 minute time expired, and the logging was disabled - it has seemingly stayed stable. So the question is, is this expected? Was the fact that seemingly turned on logging did:
[dev:499](http://hubitat/logs#)2024-12-14 10:22:37.132 PM[debug](http://hubitat/logs#)connectEventStream()
[dev:499](http://hubitat/logs#)2024-12-14 10:22:37.079 PM[debug](http://hubitat/logs#)initialize()
Re-establish the connection? What should I do, from a debug/troubleshooting, if I see this again - or is it even a bad thing (although I would think multiple connections per minute on both the Hubitat and the PowerView Gen 3 Hub isn't ideal.
Any thoughts on this?
Thank you
As a follow up - since the connection was re-established, it has been "stable" with a reconnection event every hour or so. Is it possible to detect when the connection isn't stable and re-initialize to avoid the continued bouncing?
And the issue appeared again last night. I did connect directly to the URL on the PowerView hub from my browser and it seemed to work ok, but the Hubitat was in a vicious cycle of disconnecting and reconnecting.
Any thoughts? I'm open to additional ideas/debugs. After disconnecting and then reconnecting via the app, it seems stable for ~8hours again at this point.
So I have an interesting bug appearing. Granted, I'm doing a lot of this remotely for my parents.
A few months ago, their Master Bedroom shade would stop responding to Hubitat commands. For example, if the shade was open, I would close from Hubitat, it would show closed, but in fact the shade did nothing. If I hit "Refresh" then it would revert back and show the shade open. It does report the battery voltage.
Just yesterday, another shade started the same thing. It's Shade 6 of 6 in their living room. It responds to the Hunter Douglas button controller, but not anything from Hubitat. The other shades in the room do respond to Hubitat.
Any thoughts?
OK, I only just discovered this thread, thank you for your work.
Powerview Gen3 now works with Matter and initially I connected to it via HomeKit and then Hubitat. The shades appeared but I could not control them, I think because there was no suitable driver?
Is there any benefit to trying to bring Matter into this app? The app works fine by itself, although it did not pick up the blind names from the Powerview app, instead they were just numbered 1, 2, 3, 4 etc. No big deal.
And lastly a stupid question. Does this run locally? I'm thinking it might since it asked for the IP address of the Powerview hub.
TIA,
Steve