So the light group work as intended now? No issue with getting the three entities from the hue device and all parts working as expected?
Right now the implementation only supports creating a battery sensor when creating the deconz event for switches.
Ill check with upstream for naming conventions
Haven’t tested all of it, i am doing it now but i have problems. Many of my lights doesn’t show up as entities for some reason. They are reachable but has not been added to HASS, did a restart of HASS but still not there. However i did upgrade to deConz 2.04.89 today. It does work in my module without changes. I wonder what the problem might be.
Right now the implementation only supports creating a battery sensor when creating the deconz event for switches.
Yes i was afraid that would be the case 
The only thing i can thing of is that the group i can’t see is called “Køkken spots” so maybe because of the danish Ø letter ? On the other side i have lights with danish letters that gets into hass fine.
Here is the group :
"8": {
"action": {
"bri": 255,
"colormode": "ct",
"ct": 500,
"effect": "none",
"hue": 0,
"on": true,
"sat": 127,
"xy": [
0,
0
]
},
"class": "Other",
"devicemembership": [],
"etag": "2ccae63b72b7261e548ae513607b62bf",
"hidden": false,
"id": "8",
"lights": [
"17",
"21",
"13",
"19",
"12",
"20",
"14",
"15",
"18",
"16"
],
"lightsequence": [
"12",
"13",
"14",
"15",
"16",
"17",
"20",
"18",
"19",
"21"
],
"multideviceids": [],
"name": "Køkken spots",
"scenes": [],
"state": {
"any_on": true
},
"type": "LightGroup"
},
Here is a light which doesn’t show up :
{
"ctmax": 454,
"ctmin": 250,
"etag": "733ce87b0f0f23c36b115a11953c6457",
"hascolor": true,
"manufacturername": "IKEA of Sweden",
"modelid": "TRADFRI bulb GU10 WS 400lm",
"name": "Køkken Spot 6",
"state": {
"alert": "none",
"bri": 254,
"colormode": "ct",
"ct": 454,
"on": true,
"reachable": true
},
"swversion": "1.2.217",
"type": "Color temperature light",
"uniqueid": "00:0b:57:ff:fe:37:d5:9c-01"
}
```Language specific signs shouldn’t matter. Enable debug, you should see what happens and more data to understand
For some reason they came up thrid time i did a restart of HASS docker container.
Regarding the group state, it still doesn’t work :
Here is what Hass says after turn on light that has lowered in brightness before turn off :
ight.kkken_spots on brightness: 255
color_temp: 500
min_mireds: 154
max_mireds: 500
friendly_name: Køkken spots
supported_features: 47
and here is the state in deconz
{
"action": {
"bri": 136,
"colormode": "ct",
"ct": 500,
"effect": "none",
"hue": 0,
"on": true,
"sat": 127,
"xy": [
0,
0
]
},
"class": "Other",
"devicemembership": [],
"etag": "1da69cc1f40c4ea2e22243b61735b92d",
"hidden": false,
"id": "8",
"lights": [
"17",
"21",
"13",
"19",
"12",
"20",
"14",
"15",
"18",
"16"
],
"lightsequence": [
"12",
"13",
"14",
"15",
"16",
"17",
"20",
"18",
"19",
"21"
],
"multideviceids": [],
"name": "Køkken spots",
"scenes": [],
"state": {
"any_on": true
},
"type": "LightGroup"
}
As you can see the bri is not consistent
And here is some more feedback :
Here is the group in deconz
{
"action": {
"bri": 127,
"colormode": "hs",
"ct": 0,
"effect": "none",
"hue": 0,
"on": false,
"sat": 127,
"xy": [
0,
0
]
},
"class": "Other",
"devicemembership": [],
"etag": "35e35c06a4d4d43fa8bb7c41c03d91d5",
"hidden": false,
"id": "10",
"lights": [
"22"
],
"lightsequence": [],
"multideviceids": [],
"name": "Bedlampe",
"scenes": [],
"state": {
"any_on": true
},
"type": "LightGroup"
}
I’m looking in to this with brightness and groups.
It seems that groups doesn’t keep any own state in deconz, which means I’d have to save them myself.
So the only behaviour with group will be statically set values from when groups have been changed by the user, is that what you’re expecting?
These are now fixed. Try them out to see if it gets any better.
So the only behavior with group will be statically set values from when groups have been changed by the user, is that what you’re expecting?
I am not sure i understand what you mean but what i want is following (assuming the group is off and at 100% bri) :
I tried latest version and all units seems correct now but have you done any attempt to solve above ? I still can’t get it to work but i guess that’s the case if you haven’t done any attempt 
Great description, this clarifies what you’re after.
It might be some issues with the group functionality, I will delve deeper into this tonight.
Great, look forward to that. I will move more that i have to the new component to test further…
I’d love to give this a try, what’s the easiest way to dig out all the bits needed? I’ve got HA in a virtualenv at the moment. I noticed talk above about pulling the deconz.py files and sticking them in a custom_component? Is there an easy way to do that and keep up to date with your ongoing changes?
Not at the moment unless you have access to components folder in site-packages which i don’t or it’s to big a hassle to do so i just pull changes, copy the files, change the from homeassistant.components.deconz import to from custom_components.deconz import in sensor/deconz.py , light/deconz.py and binary_sensor/deconz.py and leave custom_components/deconz.py without any changes. @Robban is ironing hopefully some of the last things before (hopefully) get’s into next release.
You could do symlinks to the files as well, then you won’t have to do the copy part.
@donnib suggestion is the easiest way since Im still fixing a last few things before official handover and if a few people can verify that all parts work as expected I can sleep better at night ;). So in your virtual-env find your site-packages/home-assistant/components and put the files in to that folder structure.
Yeah but now since this is only something i do rare i am ok, it takes few minutes and i have the latest changes 
Interesting discussion on github btw 
Yes. But it was based on a misunderstanding. Will leave it as it is until Balloob says otherwise
Yes i agree and it’s inline what we have spoken about. I am satisfied at least