Not Seeing Shades

[GTench]

Just installed this. Thanks! I have 8 shades and 2 gateways. All I see in the AC is just the HunterDouglas node with status of True. Just wondering why I don't see any shades.

Gary

[sjenkins]

hi, @GTench, did you add to the configuration with gatewayip and the ip of your gateway eg 10.0.1.150 ?

have not had good luck with default powerview-g3.local working on the eisy.

Just noticed you have two gateways (like me) per the instructions you can put an array for the gatewayip config variable which contains the ip's of the two gateways.  One will be master but it can change with outages, etc.  Below is what is in mine, please note the ip's are in quotes :

gatewayip     ['10.0.1.150', '10.0.1.151']

Let me know if this doesn't work for you.  A copy of the logs helps even more.

I am soon to put up a new version which will use a feature of the gateways in which I will only have to update on the long poll which the gateway will push more 'as they happen' updates.

 

Edited February 5 by sjenkins

[GTench]

Yes I did.  I added  the gatewayip key with a value of ['192.168.2.239','192.168.2.233']

[sjenkins]

just to verify, those are version 3 gateways?

can you goto each from a browser and hit them with http://192.168.2.239/home

one should give you a large array and the other a message saying it is not primary.

 

[GTench]

Not sure what version the gateways are but I have had them for a number of years. I get 

{"message":"Not Found","error":{}}

for http://192.168.2.239/home. I am not getting a response for the other one

[sjenkins]

@GTench, so sorry it looks like you have a v2 (or v1) powerview.  It's why I put the little 'legal' statement in the instructions that v2 was out of scope.  I love these blinds & I do believe you can buy and "drop-in" the v3 gateways as I had the option of either version about two years ago.

From what I know the api is a fair bit different.  There in an Indigo plug-in which I used to get started & it services both.  I have since moved to using features which do not exist in v2.

If there is a demand I could eventually come back and at least put in the basics for v2.

here is the link to the indigo plug-in which services both. -- obviously it would need to be converted for polyglot.

https://github.com/sdf-cnicorp/indigo-powerview

 

[GTench]

OK thanks. I will look into the V3

[GTench]

FYI... Got this reply from Hunter Douglas

If you currently have PowerView Gen2 shades, hub and repeaters they are not compatible with PowerView Gen3 Gateways.  

PowerView Gen3 is Bluetooth operated and the motors run on a BLE signal.
The only way to use PowerView Gen3 Gateways is to purchase new PowerView Gen3 shades.

PowerView Gen2 shades cannot be converted to PowerView Gen3 operation as the internal components are also not compatible unfortunately.


 

[sjenkins]

@GTench thanks so much for getting the definitive answer. My installer/dealer was not very tech savvy. I installed the gateways for him. So looks like I got faulty info from him about v2/v3 but it does make sense what you say. Let me take another look at the Indego and HA plugins and see if some basic v2 functionality is possible. Pretty sure the way I do fast updates is only v3 but even if I could do commands would that be of interest to you?

[GTench]

@sjenkins thanks. I have 8 shades so not worth it to replace everything with gen 3. I am using network resources for some limited functionality (open/close) now based on info from another poster a few years ago. Although this generally works, it is not totally reliable. Recently I added some zwave smartwings shades which wife likes and have worked pretty reliably

[sjenkins]

Found the api for v2, which may be of use to you in your network resources:

https://github.com/sejgit/indigo-powerview/blob/master/PowerView API.md

the links and json strings are different as well as how positions are done from v3

Also, as I mentioned above there are no sse streams for events, which means that polling is the only way to get data on scenes and shades.   I use polling as a secondary way to get position, scene activation.

 

[sjenkins]

new version 0.1.2 incorporates PowerView G2, I don't have one so there may need to be some refinement.

[GTench]

@sjenkins Wow thank you very much! I was not expecting this. I updated to 0.1.2. I get a message saying "start up". Not sure what it means. I rebooted eisy but I still do not see any shades under HunterDouglas in the AC. I attached a log file. Please let me know if there is anything else you would like me to do

Gary

hunterdouglas_2-25-2024_120645_PM.zip

[sjenkins]

@GTench thanks so much for giving this a try.  I’m on my phone at my daughter’s hockey game right now so I’ll have to get into depth later. But a Quick Look is good news!! it found your controller and verified it was G2 ; it just didn’t dissect the data into shades and scenes like it does on G3.

It is likely just a JSON mismatch ; if you don’t mind being my guinnea pig & a bit patient I am sure we can get there. Hard to debug at home without the hardware since I never do anything right the first time. 😜
With your feedback it will be good. 
 

btw: startup notice just means it launched and is setting up. That goes away at the first longPoll 

Edited February 25 by sjenkins

[GTench]

@sjenkins Thank you for doing this. I am no hurry and would be happy to help anyway i can. Enjoy your hockey game.

[sjenkins]

@GTench so first, your logs were extremely helpful for a few reasons.  It allowed me to see what the G2 gives back for data REALLY in the wild as opposed to the api document (not written by HD).  There were some differences.

The issue which crapped out my program is G2 only sends the position parameters the shade needs.  The G3 sends back all of them whether required by the shade or not.  You know what they say about assumptions.

So this meant more than you would like that to mean for the program. Should make it more solid.

I tested G3 and nothing seems broken by my changes.  I may eventually need to write a test program.

I did not put out a new version, just a bug fix.

I would suggest you delete and re-install the plugin.

I expect two-steps forward and one-back ; send me the logs ; thanks again for your help.

 

[GTench]

@sjenkins ok did as you suggested.  I still don't see shades in the AC. I rebooted eisy after deleting and again after reinstalling. I have attached the log file.

hunterdouglas_2-26-2024_105227_AM.zip

[sjenkins]

@GTench Thanks for sticking with me & for the logs, they are invaluable.

G3 & G2 have different ways of communicating their JSON data.

G3 uses a different label for room id, versus shade id, versus scene id

while G2 uses 'id' for all of them.

I thought I got all the spots where I was referencing them.  I didn't.

if you are ready for another try I just testing G3 and didn't break anything.

You will want to delete and reinstall the plugin to keep it clean.

 

[GTench]

Wow... Nice - thanks, looks like everything is there in the AC. Just need to spend some time today figuring out exactly what I am seeing and doing a bit of testing. If you need me to do anything else please let me know. I have attached new log file and a screen shot from AC

hunterdouglas_2-27-2024_115158_AM.zip

[GTench]

I notice that full names show up in the debug log but are truncated in the AC. I assume this is a limit of the AC. I attached one more screen shot.

[GTench]

@sjenkins I tried sending open and close commands as well as trying to activate scenes but none worked. I see some error messages in the attached log file

hunterdouglas_2-27-2024_24141_PM.zip

[sjenkins]

3 hours ago, GTench said:

I notice that full names show up in the debug log but are truncated in the AC. I assume this is a limit of the AC. I attached one more screen shot.

Well we are up and running!

You are right the names are truncated by the AC side of things.  What I could do is limit the room text to something smaller so you are more likely to get more of your shade/scene name.  A more complicated version would have the shades / scenes nested under rooms.  I have never done that so I would suggest we start with A and put B on the todo list.

You also could be a bit less verbose in your naming 🤪

Once I get done my meetings I can take a good look at the logs and figure out why you have pretty pictures but nothing moves when you tell it to.

Once again, thanks for going on the G2 journey with me.

btw: :  in parallel I have been working on some other improvements to the discover routine.  Basically, from others I am incorporating best practices from other plugins.  Because of that the next debug cycle may have a version change unrelated to this debug cycle.

 

 

Edited February 27 by sjenkins

[GTench]

@sjenkins No, thank you for doing the journey. I much appreciate it.

I agree with you about the names. Looks like a concatenation of different items that I created in the cell phone app. I will likely rename them at some point but for now I can see the full names in the PG3 nodes list; so, I can link to the AC name for clarification.

[sjenkins]

@GTench I put up a new version as there have been some developments for both G3/2

I think I found the bug in the update routine.

I also cleaned up the Logger.debug a bit to clear out the noise.

thanks again

 

[GTench]

@sjenkins just tried the new version but shades and scenes still not responding to comm ands from AC. I have attached latest log file.

hunterdouglas_2-28-2024_111502_AM.zip