Neil,
How am I best defining the blind IDs?
Looking at the documentation, the app shows the Blind ID as "xxx.yyy-nn" already formatted, whereas the plugin currently asks for xxx, yyy and nn as separate values.
Should I just ask for the Blind ID as a single string?
Peter
Identifying blind ID/Code
Re: Identifying blind ID/Code
Peter,
I see no reason why the blind or room ID’s can’t be specified as a single string.
I am unable to recall why I split them, but probably as. result of me being a “Python novice”!!
I really appreciate your efforts - totally unexpected when I made my initial post.
Neil
Sent from my iPad using Tapatalk
I see no reason why the blind or room ID’s can’t be specified as a single string.
I am unable to recall why I split them, but probably as. result of me being a “Python novice”!!
I really appreciate your efforts - totally unexpected when I made my initial post.
Neil
Sent from my iPad using Tapatalk
Re: Identifying blind ID/Code
I’ve just (5 minutes ago) uploaded v1.0.6 which includes this.
Petet
Sent from my iPhone using Tapatalk Pro
Petet
Sent from my iPhone using Tapatalk Pro
Identifying blind ID/Code
Away from home for the next day or so - will try on my return, Thanks again!
Sent from my iPad using Tapatalk
Sent from my iPad using Tapatalk
Re: Identifying blind ID/Code
Hi Peter,
Have had a chance now to configure all my blinds, and all good.
I did get a bit of a fright, however, as when configuring the blinds, I entered the blind code as instructed in the config dialogue, using decimal points between the digits. No blinds responded! It turns out that the controller wants a hyphen between the second and third set of digits, so a change to the instructions would seem in order (see attachment).
I have also limited my testing to Up, Down and Stop, as we don't use Favourites at this stage.
Thanks again for whipping up this plug in!
Neil
Have had a chance now to configure all my blinds, and all good.
I did get a bit of a fright, however, as when configuring the blinds, I entered the blind code as instructed in the config dialogue, using decimal points between the digits. No blinds responded! It turns out that the controller wants a hyphen between the second and third set of digits, so a change to the instructions would seem in order (see attachment).
I have also limited my testing to Up, Down and Stop, as we don't use Favourites at this stage.
Thanks again for whipping up this plug in!
Neil
- Attachments
-
- Screenshot 2020-04-23 at 3.30.55 pm.png (46.19 KiB) Viewed 4439 times
Re: Identifying blind ID/Code
Ah, good catch - that’s a typo as I know it’s supposed to be a hyphen.
Will sort it.
Sent from my iPhone using Tapatalk Pro
Will sort it.
Sent from my iPhone using Tapatalk Pro
Re: Identifying blind ID/Code
Hi Peter!
I note from your other posts that y are VERY busy with other plugins, but was wondering if you’d have time to update the Neo plugin to correct the typo identified in my previous post?
And if it’s OK with you, I’d like to notify Neo of its integration with Indigo to go along with their other integrations.
Thanks, Neil
Sent from my iPad using Tapatalk
I note from your other posts that y are VERY busy with other plugins, but was wondering if you’d have time to update the Neo plugin to correct the typo identified in my previous post?
And if it’s OK with you, I’d like to notify Neo of its integration with Indigo to go along with their other integrations.
Thanks, Neil
Sent from my iPad using Tapatalk
Re: Identifying blind ID/Code
Many thanks!
Sent from my iPad using Tapatalk
Sent from my iPad using Tapatalk