Philips Dynalite - official component - updating states

uzelac · July 13, 2020, 6:28pm

Hi

I have an issue which started with transition to official component. Before it worked OK.
Issue is that component and with it HA is showing wrong light states.
It looks to be easily confused, after some time and few dimming/switching it will show wrong state.
Mostly, it shows on or ~60% dimmed (even though i use my light On/Off so 0 or 100%, nothing in between) when they are off.
Now when i think about it, some lights are worse than others, mostly one of them is very often showed like 90% even though that one is 0 or 100% allways.

Where to look, what log file can show what is happening ?

Thanks

ziv · July 13, 2020, 8:29pm

if you have in the logger configuration in configuration.yaml the ‘dynalite_devices_lib: debug’ line and give me the homeassistant log file (potentially grep dynalite_devices_lib so it doesn’t show your full setup), I can perhaps better understand what is happening. This doesn’t happen in my setup

uzelac · July 18, 2020, 11:41am

I’ve uploaded it, it is raw, problems are still happening so would be grateful if you solve it.
Thanks

ziv · July 20, 2020, 1:00pm

I looked in the logs. It seems that you have a few Dynet codes that it does not handle: FADE_CHANNEL_AREA_TO_PRESET, PRESET_OFFSET, RAMP_ALL_CHANNELS, START_FADING_FAST, and TURN_ALL_AREAS_ON.
FADE_CHANNEL_AREA_TO_PRESET is handled in the newest version, which hopefully will make it back to the main stream soon. I can make you a custom component if you want to see if it solves the issue. The problem with the other Dynet codes is that they do not happen in my environment, so implementing them would be purely from theory with no way to test it. Are you familiar with these codes?
PRESET_OFFSET is the only one that doesn’t seem straightforward. In any case, would love to have you try it with the FADE_CHANNEL_AREA_TO_PRESET handled, either with a custom component or the production one when it will be in the mainstream, probably a few weeks from now.

uzelac · July 20, 2020, 7:36pm

I’m familiar with task commands, what i dont know is explained in manual so can take a look :).
PRESSET_OFFSET is command which will shift presets by some offset.
At my home, after 21h some presets are shifted to +10, so whenever some keypad/device sets preset 1, it will really set preset 11.

If I can be out of any other help, let me know.

ziv · August 6, 2020, 7:21am

I have a new version that also sends events on every packet, so you can monitor the network. if you install Ha on a venv, you can create a temporary HA for this with a private version.

In your separate venv (don’t use the production…), simply install HA from my branch:
pip3 install --upgrade git+git://github.com/ziv1234/home-assistant.git@dyn_events

then we can work together on adding any functionality. I just don’t want to add code that just runs “in the dark”

uzelac · August 13, 2020, 10:10pm

I have one and only HA :).
Can add another one over weekend to see how it goes with new branch.
Will let you know.

Thanks!

thedezza · August 17, 2020, 5:49am

Hi,
Very new to HA (Started yesterday)
Trying to connect my Dynalite PDEG to HA
Have tried all sorts and whilst the integration seems fine and shows up in integrations the lights in any dashboard show as unavailable. Have used the following very simple for now in my configuration.yaml:

dynalite:
  bridges:
    - host: 192.168.86.121
      port: 80
      area:
        '2':
          name: Kitchen
          channel:
            '1': 
              name: Cupboards
            '2': 
              name: Hob
        '3':
          name: Living
          channel:
            '1':
              name: TV Wall
            '2':
              name: Mirror Wall
      preset:
        '1':
          name: 'On'
          fade: 0
        '4':
          name: 'Off'
          fade: 0

I am using a PDEG with v.3.44 firmware. I can reach it with CGI commands with the IP and port to areas 2 & 3, get the following in the logs:
Logger: dynalite_devices_lib
Source: /usr/local/lib/python3.8/site-packages/dynalite_devices_lib/dynalite.py:58
First occurred: 7:00:34 (858 occurrences)
Last logged: 7:45:17

Could not connect to Dynet ([Errno 110] Connect call failed (‘192.168.86.121’, 80))
Could not connect to Dynet ([Errno 113] Connect call failed (‘192.168.86.121’, 80))

Perhaps it is something very stupid, hoping one of you can help?

Thanks

thedezza · August 17, 2020, 10:56pm

The integration does show up in the “Integrations” page including devices/entities. In the UI they switch between on/off and do nothing

uzelac · August 19, 2020, 2:27am

Try without any manual config.
Just add it in integrations and see if discovery is working.

thedezza · August 19, 2020, 12:12pm

@uzelac unfortunately not, not got the autodiscover to work and show any channels.

I did the original to work though, a lot of resetting of the gateway and now on port 12345. Great to have this working!

uzelac · December 27, 2020, 9:59pm

Hi

Sorry to get back to you just now, life was … complicated… few past months.
I have some time for HA now and have been updating version and config.
Hope dynalite component will be better but unfortunately found out that nothing changed with my issue

If i can help with this or whatever else related to Dynalite let me know.

Thanks

Freman · February 9, 2021, 4:28am

I’m afraid I’m also having issues with updating states in HA.

This is a pair of messages from my Antumbra to my dining room light

{ // Turn light off
    "event_type": "dynalite_packet",
    "data": {
        "host": "10.0.0.190",
        "packet": [
            28,
            6,
            0,
            107,
            3,
            100,
            255,
            13
        ]
    },
    "origin": "LOCAL",
    "time_fired": "2021-02-09T04:07:43.716024+00:00",
    "context": {
        "id": "c2f2ccde6fea26e33aa8b658deac8611",
        "parent_id": null,
        "user_id": null
    }
}
{ // Turn light on
    "event_type": "dynalite_packet",
    "data": {
        "host": "10.0.0.190",
        "packet": [
            28,
            6,
            0,
            107,
            0,
            100,
            255,
            16
        ]
    },
    "origin": "LOCAL",
    "time_fired": "2021-02-09T04:07:36.630239+00:00",
    "context": {
        "id": "6bc2568e839c586cd5c950431a1eb693",
        "parent_id": null,
        "user_id": null
    }
}

Home assistant doesn’t update or see these as preset changes, but it does see the packets (As evidenced by the packets here in front of you :D)

(edit: spelling)

Edit: I’ve figured it out, don’t mix template: room with channels if you actually want to receive device updates.

Edit: still hit and miss… I guess I’m writing my own.

jonaskul · May 20, 2021, 7:01am

I have the same issues. State dont update from Dynalite.
This is my config.

# Philips Dynalite
dynalite:
  bridges:
    - host: 192.168.10.52
      port: 50000
      active: on
      autodiscover: false
      polltimer: 2.0
      area:
        '3':
          name: Kjøkken
          template: room
          channel:
            '1':
              name: Pendel
              type: light
              fade: 2.0
        '5':
          name: TV-stue
          template: room
          channel:
            '1':
              name: Pendel
              type: light
              fade: 2.0
        '6':
          name: Utelys
          template: room
          channel:
            '1':
              name: Inngang
              type: light
              fade: 2.0
        '15':
          name: Nisje
          template: room
          channel:
            '1':
              name: Varme
              type: switch
              fade: 0.0
        '16':
          name: VVB
          template: room
          channel:
            '1':
              name: VVB
              type: switch
              fade: 0.0
        '19':
          name: Grov
          template: room
          channel:
            '2':
              name: Varme
              type: switch
              fade: 0.0
      template:
        room:
          room_on: 1
          room_off: 4

os.habitats.tech · January 5, 2022, 5:54am

This is for Ziv and anyone else who wants to get the Dynalite integration right.

Have used a simple setup DDLE801 (already configured by someone else) and an IP/RS485 gateway.

As of Jan 2022 / core-2021.12.7 / supervisor-2021.12.2 / Home Assistant OS 7.1

Autodiscover does not work
Active does not work
Philips Dynalite: Request area preset, runs with no errors, but does not return anything
Philips Dynalite: Request channel level, runs with no errors, but does not return anything
If you get 3 or 4 wrong and you get an error only way to recover is to restart the HAcore
Setting the channels manually in the config.yaml works for both switch on/off and dimming
The HA light entity works for the channels configured manually (on/off/dim), but as others reported it does not update when the change at the Dynalite side.

My question is if others experience same issues and if either a workaround is known or someone is working on a fix.

Ziv, I assume everyone would appreciate an update and if there is something I can personally do to help with testing, etc.

I can also assist in the documentation where a couple more examples and walkthroughs might be valuable to people trying this for the first time.

Ziv, please let me know how I can assist. If this requires posting somewhere else please let me know as well.

adirburke · July 4, 2022, 10:56pm

Was this fixed for you ?

shairo2004 · May 24, 2024, 10:21am

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 based on this condition, you can get the accurate channel level value using the call service on automation to be triggered by any changed in state or any attributes and it will automatically have a correct state of the individual channels.
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.

shlomiw · June 25, 2024, 6:58pm

Hi Shairo,
I have the unsynchrnoized brightness issue as well, could you please explain more how you solved it? can you show an example?
Many thanks

shlomiw · June 30, 2024, 9:20pm

Ok, so far what I came up with:

alias: Office Ceiling Request Channel Level
description: ""
trigger:
  - platform: state
    entity_id:
      - light.office_ceiling
condition: []
action:
  - delay: "00:00:02"
  - service: dynalite.request_channel_level
    metadata: {}
    data:
      area: 16
      channel: 1
  # below part to set default value when turning on to 100%, in this case set to 60%
  - delay: "00:00:01"
  - condition: state
    entity_id: light.office_ceiling
    state: "on"
  - condition: template
    value_template: "{{ state_attr('light.office_ceiling', 'brightness') | int > 250 }}" # max is 254
  - service: light.turn_on
    target:
      entity_id: light.office_ceiling
    data:
      brightness_pct: 60
mode: single

It’s not the best, since when you turn on, it has a delay until it dims to the default brightness. But it’s good enough for me.

Hope it helps anyone