But Gen2 hub isn’t using this integration, is it?
I understood there is just one HD/Luxaflex Powerview integration. Gen-2 was there from the beginning, gen-3 is recently added. (Someone correct me if I’m wrong)
Thank you Kingy444 (Todd King)! I will be hitting you with a coffee
For those who’ve read through this very helpful thread
-
I already had the PowerView integration for my gen2 hub and (18) shades
-
I went to PowerView app to make sure all FW had been applied and to get the IP of the Gen3 gateway
-
Pressed ADD ENTRY on the integration page in HA and entered the gateway IP from the PowerView app. The GW added and the (2) blinds I have were visible and operated as expected.
I am not using the HomeKit integration at all for this GW.
Thank you for all the work you put into this Hunter Douglas Gen3 integration!
Further to my earlier post, it might have been a problem on my end so I will report back on the errors I was getting on the gateway.
I had not cleaned up my previous integrations and automations with the Works With Google integration and the Powerview app even though I had added the new home assistant integration. I think there might have been some collisions and conflicts between them. It’s now set so that only home assistant controls the blinds, including through the Nabu Casa Google voice integration.
@nugget and and @mperone apologies for the delay. Think I have found the issue and will try to get that pushed out ASAP.
The issue is once one shade fails to load they all go kapoot unfortunately.
To query the shade strength, it was a design decision as this didnt offer a great deal of use, but was also easy to include.
1 Like
@wimjanse @harryfine You are correct that this is the same integration. There were historic reports of hubs freezing and tracked under Powerview Polling causing timeout errors · Issue #73900 · home-assistant/core · GitHub
I am hopeful that the PR tagged there resolves most of those, I am not sure it has made release code yet or not
thank you for digging into this - apologies for not being helpful, i was away from home and just came back today.
I was excited to test drive this integration so I gave it a shot. It worked for a little while and then stopped. I have a PowerView Gen 3 gateway and it just seems to be unreliable. I’ve returned it for a new gateway several times, but always have the same issue.
What happens?
The initial gateway setup completes successfully, I see my shades, and it shows an IP address as shown below.
I can even add the device in Home Assistant and interact with the device / entities. It seems to work for a little while (minutes to an hour) and then all of the sudden becomes unresponsive. I can still ping the gateway, but the app shows no IP address and the entities all become unavailable in Home Assistant.
Is anyone else experiencing this behavior? Any ideas if I’m doing something wrong?
No, I have a gen 3 gateway and haven’t noticed any connectivity problems. If you are having issues with the app, then it is likely your wifi settings or perhaps wifi strength.
I use it within HA, I wouldn’t say a lot, there is only some much up and down with blinds one can do in a day, but haven’t noticed it going away. Sometimes where the shade location is takes a bit to sync. I can certainly having it running for the next time I update HA, so a week or so.
I am looking to get Hunter Douglas shades with powerview Gen 3. Do they use local control and any issues with HA. I don’t want to spend 20k on shades to have something shut down in the future!! What is your experience, would you do anything different?
I don’t want to influence you just based on my experience. But for me, it works but about 20 percent of the time on of the shades does not open/close with automation and has to be done manually from a dashboard. I don’t know if it is a timing issue, I have tried 30 second “wait” commands on automation between each but it doesn’t seem to change the outcome. Tried putting them into helper groups but still occasionally 3 living room blinds will open based on sun position and one will remain open. Easy enough to close the remaining one using the slider on a dashboard but for me, not perfect.
Wifi coverage is excellent everywhere, my gateway is not wired ethernet, it is wifi only.
Prior to using this new integration, I was of course using the PowerView app, and when using scenes with the app based on time of day or sunset, this problem did not exist.
I would love to hear the experience of others.
I did the original development for the Gen 3 before the HA guys just did their own version about a year later. You have a local gateway that HA talks to. Shouldn’t need the internet for it to work, but you will need to buy a gateway and centrally locate it. Seems to have pretty good range as it handles all my 10 windows on my second floor. There might be more updates for the remotes and shades then you would expect from say a remote and a shade. Hopefully that’s because I was early on the Gen 3 and not the norm.
I haven’t had any issues with it so far. But again, it isn’t like I’m rapid firing shades up and down. Seems to work whenever I want it to, from HA or from Powerview App.
Battery sensor updates don’t work for me though. There are 3 levels, always reads 100% and I’ve had to charge mine. I put as much time into figure that out as I did just writing this now though. Probably should take a look. I don’t know as of this writing if HA or the gateway is the issue.
@alindner are you using your custom component or have you moved to the ha core version?
The ha core version should be reading battery levels per the swagger api doco.
I don’t have any gen3 to test against but am in the process of some gen2 being replaced and can test it out once I get a gateway.
They are definitely not the cheapest but they do offer one thing many products are not, a local API.
You do need the Gateway for that to function which is an additional purchase but this means that it should just “stop working”
Dependant on the size of your home you may need more than one of those to act as a repeater. There is also a wifi and an Ethernet version (pro)
Gen1, 2 & 3 should all be fully functional in the current HA core integration.
I switched to HA core version as soon as it was available.
I haven’t ever seen the API return anything but a 3, which means 100%. I don’t see a difference in the PowerView App vs. HA, so no reason at this point the battery reading has anything to do with HA reporting.
I see the same thing here. I have 47 gen 3 shades at various levels of battery and all showing batteryStatus: 3 in the local gateway API. Except one which is dead and showing batteryStatus: null currently.
All my blinds are using the newer rechargeable battery wand (powerType: 0) although most of them were configured as powerType: 2 by the installer. If I set them to 0 it has seemingly no effect on the batteryStatus reporting.
The 100% power bug seems to be in the hub, not the integration.
Coffee … on its way. I can’t pull off this sort of stuff. But I sure do appreciate those that can, and do.
I am installed and tinkering with UI. The fact that that is possible is a huge blessing. Thanks @Kingy444
@mchammer I now started my efforts to do a pure BLE based local control (without the gateway) of the HD shades. Just drop me a message if you are interested. Will take for sure quite some time to complete it.
1 Like
@patman I would definitely be interested in a local control. What would you be using for the the BLE gateway? ESPhome device? How much of it would be leverageable into local BLE control for a Tuya shutter? I have a Tuya BLE gateway also that controls some shutter motors. Thanks.