Hey,
I have followed the post #22 here, It seems to work for the feedback, Other issue raised which is if you control it via HA then the switch it self do not update it means if you turn it on via HA then physically you have to turn it off by taping twice
@BinGraiban I’m getting the correct state via your above method of areas but added in task to the switch set the preset to 1 or 4 after the fade time delay…its basically the double press but you don’t have to physically press it
I will give it a try thanks a bunch 
Hello Sir,
How are you?
Was this issue solved? If it was, can you share to me because I have same issue with my HA states updates.
Hello Dears, @ziv @HoundDog @BinGraiban .
This may help a lot.
I used ramp up/ramp down channel button option in my antumbra keypad. Its working fine now. I can get directly the actual feedback or state of the circuit i operated.
I have attached the reply of the Philios dynalite expert.
If we can use the on one touch messages will be very helpful.
Are you using the latest version? it should support 0x6b (fade channel to preset)
also, can you please try to run with log level debug for the dynalite components, push the switch, and see the output?
yes post # 22 in this thread solved my issue
I’ve recently set up the Dynalite integration and most functionality is working for me (even using OneTouch ramp function from Antumbra display) correctly reports state. However, I have a number of buttons that run tasks that execute multiple actions. These “tasks” do not correctly reflect the state in HA.
Task4()
{
Name="Evening"
Preset(A=3, P=2, F=3.00)
Delay(0.10)
Preset(A=4, P=2, F=3.00)
Delay(.10)
Preset(A=5, P=2, F=3.00)
Delay(0.10)
Preset(A=2, P=2, F=3.00)
Delay(0.10)
If I use the button to trigger Task4 none of the Areas update their states correctly in HA. Is there a workaround or an alternative option to set this up?
Finally, I think found a way around to automatically update the state of channels level by creating automation. So basically, if you trigger area preset on (preset1), off (preset4), scenes (other preset#) and dimming it does not send request channel level to update the individual channels levels. So, by creating automation based on this condition, you can get the accurate channel level value using the call service (request channel level on) via automation to be triggered by any changed in state or any attributes and it will automatically have a correct state and update of the individual channel’s levels.
Same also if you trigger an individual channels level to sync feedback with (preset1), off (preset4), create an automation with individual channel as our trigger and then do test confirm brightness if 0 then action send area to off (preset4), if brightness is 254 then action send area to on (preset1).
Let me know if this works for you.
Hi Guys, i am a Dynalite newbie, but a long time HASS lover. I have created a few libraries which you may find useful, unfortunately, i really prefer to have my integrations run on MQTT, so all my dynalite stuff runs on that, that said, i have faithfully replicated the DYNET bus on MQTT, which is simple, but i have also added full descriptions, including field parameters and the XML of the entire library of Dynalite commands. My bridge also has the benefit of supporting both DYNET1 and DYNET2 packets. I was thinking to recreate a lighting bridge for Dynalite and MQTT which auto creates HA entities, however, i think this integration does the job well. Dynalite channel levels commands do not set area presets, and visa versa. I had the benefit of coding my system, so i stuck exclusively to area presets, and i have a long list. I also created a little integration that combines the standard 4 presets (off=4,10%=3,70%=2, 100%=1 preset) from this integration into a entity that supports brightness commands (obviously with the settings as per the presets) for a given area. Lots of stuff here, if you are interested DM me or check out my github: Nerih (nerih82) · GitHub or dockerhub: https://hub.docker.com/repositories/nerih82
So, I am relatively new to HAAS but a very experienced Dynalite system designer/engineer. I am working with a home that has an old Dynalite installation (15+ years old). The system still works great.
I have the Dynalite Integration installed on a Home Assistant Yellow and using a Dynalite PDEB to integrate the two systems. I am able to control the lights from within HA. However, HA does not track the state of lights if they are switched from one of the Dynalite User Interfaces (in this case they happen to be DR2P switches) or within System Builder. This is the case if a single channel is switched on or off (Dynet code: 1C,07,02,6B,03,64,FF,0A) or if an entire area is switched on or off (Dynet code: 1C,07,64,03,00,00,FF,77). Even if I resend a packet that was generated via the HA Dynalite Integration the associated button in HA does not reflect the correct state.
I have reviewed this and other threads but it is not completely clear whether state tracking works or not. If it does, I am not sure why it does not work corrrectly for my particular configuration which I believe is fairly generic.