can you please start a new thread about this? this one is getting quite long.
when you open it, can you please describe the scenario that you see that reproduces it, and i am sure we will be able to understand it
1 Like
All right thanks again for your patience. Will do so
Hi
Well, few issues:
- not really good at capturing states, often light is on 100% and HA shows 60% or off. Worked OK with unofficial component.
- canât move more than one cover. If I order 4 of them to close HA will do it one in a time. Goes to move next when previous is finished. Automation will move them all together, but from Lovelace it is like this, one by one.
Config is a bit different, so it took some time and trying to make it work but that looks Ok now. It is not as in documentation where " no changes needed when going to official. Not that big deal, but worth mentioning.
thanks. Can you please open the first issue in a new topic? This one is getting long. If you can reproduce and send me the logs with dynalite_devices_lib set to debug, would be great. There is another similar thread that i am working on a similar topic but not sure if it is the same.
For the second issue, is it happening when you move them to a position or simply up / down? if it is by setting the position, i believe i know where the problem is and can fix it. In my setup i use mostly up/down and i can certainly move them in parallel.
The issue with the component is that i found several bugs and pretty much had to rewrite the library to make it stable. will get the missing features / broken functionality fixed quickly
1st issue.
Started new topic:
2nd issue
Yes, i mostly use set cover position, and not up down. But what confuses me is that in automations it mostly works (not allway) and from lovelace it never works, always one at the time.
It is great if you know what it can be 
Regards
Ok if I create a custom component for you with that functionality to test it until it gets absorbed in the mainline code?
Great, let me know 
Hey all, Iâm a Dynalite programmer but new to HASS.
RE: issues with feedback from your Dyanlite network ie you press a physical switch but the channels arenât updated in HASS - Iâm using a PDEG which auto configs the port to Dynet 2 and wasnât getting feedback. I configured a new TCP server port using Dynet 1 and it is now working.
Cheers
1 Like
Thanks. Good to hear. If you are a Dynalite programmer, any chance that you have the binary protocol for dynet 2? i couldnât find it online so the component only supports dynet 1
The Dynet-2 protocol is proprietary so you wonât find it anywhere unfortunately, only Dynet-1 is open.
Thanks. So unless someone from Phillips decides to integrate it, will only support dynet 1âŚ
BTW, do you know how to setup a PDEG so it uses dynet 1 and not dynet 2? I had people having problems
I doubt they ever will tbhâŚ
Yes, you need to change the port settings for the one setup to integrate with HA
Hello Flinn,
Iâm dealing with the same problem.
Where did you set up the new TCP server port using Dynet 1? I couldnât find where to make these settings. I would be glad if you help.
Thank you.
Hi,
Using System Builder/Envision Project Dynalite software. Itâs under the PDEG in Port settings.
Hi Flinn,
You saved me from a big trouble. It is working now. Thank you so much.
Can I ask you one more question?
I have 1 area with 1 channel.
area:
'2':
name: MasterBed
template: room
nodefault: true
room_on: 1
room_off: 4
channel:
'1':
name: Spot
type: light
fade: 2.0
When I turn the Area on and off, the Channel data also changes.
But when I turn the Channel on and off, Area data does not change.
What could be the reason for this?
Hi mate,
This is just how Dynalite works - sending Presets will change the state of Channels within the Area, however changing Channel levels wonât affect the current Preset. Ie if you have an Area with 3 x Channels in it, sending a Preset 1 may turn on all 3 x Channels - you can individually turn all 3 x Channels off and the Area will still be in Preset 1.
The only way to get Presets to follow Channels is using conditional tasking in a device which will keep track of channel status and change the preset once they are all off - its a bit of work.
Hope this helps
Flinn
Hi Flinn,
I understand it clearly. Thanks a lot.
To solve this issue, I created light group in HASS using this guide:
I added the channel lights to the group and named it âAll Lightsâ. Now I have virtual dimmable Area Entity in HASS. So, I can use it in cards as a light.
When I change âAll Lightsâ, the channel lights under it get that value. Also, if I change the channel lights separately, âAll Lightsâ takes their average. Itâs very useful.
Thank you.