Sounds like a good idea, although I would suggest that the goal should be to integrate into core Home Assistant rather than living on its own in HACS to avoid further fragmentation.
My only must have feature wise is having an option to only send values on value change, so that it’s possible to share control with other DMX controllers if necessary.
I’m interested in adding an Artnet listener too as suspect that would be possible to get a two way state, but I have no time to commit for the foreseeable future.
Happy to add someone as a maintainer to my repo (but there are certainly more complete/better designed components out there) or to mark it as archived and point people elsewhere!
3 Likes
Sounds like a good idea, although I would suggest that the goal should be to integrate into core Home Assistant rather than living on its own in HACS to avoid further fragmentation.
Definitely I would like that as well and wil make an effort to get it in there. I use HACS as a stepping stone until it’s in a good state.
My only must have feature wise is having an option to only send values on value change, so that it’s possible to share control with other DMX controllers if necessary.
I’ve read your comment stating this as a hard requirement, so I’ve already been looking into this. Since currently, the transitions are built into the PyArtNet library, I might have to re-implement them anyway to support KiNet and a e1.31 sACN. I’ll make sure it doesn’t send unnecessarily. 
1 Like
@jnimmo Correct me if I’m wrong, but it looks like merging alternative DMX sources is already properly implemented through using only the lowest channels through Art-Net and having your DMX master only control the higher channels (rounded upwards to the nearest even channel number).
I would like to update Home Assistant through getting DMX universes, but I don’t think I’ll do it at 40 FPS and I don’t think before every send as it might impact performance. The annoying thing is that I’m now committed to maintaining 3 DMX interfaces, rather than only Art-Net.
I don’t know where to make the configuration for Dmx - home assistant can anyone help and Can i use my light bulbs in a program like QLC+
Doesn’t need to be a hard requirement as there may not be anyone else needing it, but if it’s simple enough to have as an option would be fantastic.
No it’s not quite met currently - the situation is we have wall switches/dimmers which control the same lights lights over DMX as we’re controlling from Home Assistant.
The current switches only send the DMX frames on change, so if Home Assistant does the same then the lights can successfully just be controlled by whatever device was used to control them last.
I am testing both integrations, and have a few questions.
I have this issue for a another light-integration, but have a bit different issues for the hass-dmx dimmers:
The dmx-integration can remember the dim level if it’s turned on at reboot, but not if it´s turned off. If its turned off, and then switched on after reboot the dim level is set to 100%.
The artnet_led-integration remember the dim level even if it was turned off at restart, but instead it always turns the lights on to that level after restart, even if it was turned off before the restart.
I saw that it was a few commits ahead. I change to that repository instead, and then it worked! Thanks.
I will just add my post here, maybe someone can help because I am an absolute beginner…
Hi Everyone
I am farly new to HA and currently implementing my streaming studio and living space in HA. Everything is going great but now I hit a problem and I am banging my head at a wall for days now.
I want to implement my Godox TL60 lights (Godox TL60 RGB Tube Light Instruction Manual) into HA. Goal is to implement it to routines to switch on/off and also implement it in my streaming alerts.
For that I need to somehow access it via HA. I tried first to reverse engineer the bluethooth protocoll like discrebed in this Video:
But sadly it looks like the communication is encrypted and hard to reverse engineer.
My second solution would be to integrate the lights via DMX, But the lights have Ethernet DMX ports and I am really struggeling to find hardware to connect it to my HA (I am running HA on a Syntology NAS).
Does anyone here have a solution for one of the 2 options or any idea how I could implemnt the lights?
From what I read so far it should be possible with a
Enttec Open DMX USB Interface and a the sssnake CAT5 - XLR5M adapter (sorry cant attach more then 2 links).
Is that correct?
Thanks for the help in advance.
Best Regards
Sandro
If you’re running on a Synology NAS and want to avoid USB troubles, I suggest you use something like this: Showtec NET-2/3 Pocket – Thomann België . I’m using this for over a year now and never had any troubles with it.
I’m not too familiar with DMX cable conventions, but I guess DMX over ethernet cable is just another standard. DMX all goes over XLR connectors in my setup. Just make sure you’re not plugging those ethernet versions into your LAN switch panel then 
To broaden merjin’s post, I’d say that Artnet (DMX over IP) is a fairly established protocol with quite a number of implementations of the ethernet (IP) → DMX (XLR-Type) kind of device.
I use a Chauvet DJ AN2, which has been pretty painless. Others have reported robust results with eKing devices.
I’m no pro on the cable connectors (my DMX is all hard-wired), but I would expect the solution to be straightforward
Good luck!
That’s true, but I think, in this case, an RJ45 connector is “abused”, maybe to save some space on the device or to be able to use existing cables. I don’t think artnet is “going in that device” but regular DMX, just not with XLR connectors.
Thanks for your fast reply, really appreciate it.
Thanks for the device you linked, I was hoping to find a bit a cheaper solution since I only need it for my 2 TL60… but I guess its either that or buying different light’s that support native smarthome connections.
The Showtec almost costs as much as 1 of those lights 
Yes, agreed re: abuse of RJ-45 in the case of being a DMX input/output; however, these ‘abuses’ are everywhere.
Also note that the RJ-45 abuse is not wild-west: there is dominant/standard pin assignment (I forget the name), and as I understand it, there is no danger of electrical damage to equipment (i.e. if you get it wrong, it won’t work, but at least it won’t fry your gear).
Ironically, the use of XLR3 for DMX is NOT this case. I forget which combo causes damage, but if you plug audio equipment to DMX using XLR3, you could end up with serious hassle and a big bill…
Thanks for the help guys!
One last question beofre I order the hardware:
I read the manual and it seems like the light uses a bit a weird kind of DMX controll:
From my understanding I have to send signals over 6 channels to set different colors/FX.
My idea now was to set 4 channels all as dimmer (I dont need RGBW), and create automations for the different colors/FX I want. But this seems to be a bit overcomplicated, maybe there is an easier way to do it.
My Idea:
config:
Action:
I added the disered value in % from 255 → set brightness 66% = 168 is this assumption correct?
Sorry for the maybe stupid questions but never worked with DMX before and I want to get this right before I order Hardware just to realize that it doesnt work the way I intended
Dont be sorry for asking questions. We’ve all been there and there’s no shame in it.
If you don’t want RGBW, why not go with CCT mode then? You’d need one dimmer for brightness adjustment and one for color temperature. If you’re not planning on changing the color temperature, I’d use a channel of type ‘fixed’ for that. Those never change values, not even when you call a service in HA to turn off all lights.
If you do want RGBW, I think you better use a dimmer type for brightness and an rgbw type for the next 4 channels. You assign the first RGB channel (=n+1) to the entity and it will use the next three as well. I don’t have any RGB(W) devices myself though, so I can’t speak from experience.
I dont need RGBW because I will use the HSI for colors (less channels used then). The idea with the RGB for the last three is very good thanks, so I only need to set values in one entity instead of all of them. Thanks I lot I will report back when I got the hardware.
Hi maznaz. So sorry for the super late reply.
I had these controllers in testing mode for quite a while and only last week decided to put them to use for the whole house.
I got 16-bit resolution working and compared with the gledopto controllers I had earlier, these controllers make the lights even brighter and the control respons is really fast.
About light flickering that does still occur which is a little bit annoying but I decided to live with it for now. Im not sure if there are any settings I could adjust to have a smoother fade.
Give me a reply if you need any assist in setup.
Im having some issues with restoring brightness and color_temp with the corb3000/ha-artnet-led integrations.
Every time I restart home-assistant, all lights from artnet_led integrations return to off and to default color temp 261,5 (middle value between cold and warm light)
I tried experimenting with parameter “refresh_every:” but that didnt do anything.
I re-downloaded files for the integrations via HACS. Checked files in file editor to verify they match with the files in the github repo.
I also tested with files in mvandenabeele/ha-artnet-led integration but that just renders all entities unavailable
Home Assistant 2022.8.5
Supervisor 2022.08.3
Operating System 8.4
on a rpi 4
lights.yaml:
Light before restart:
Light after restart:
mvandenabeele/ha-artnet-led:
Hi @methosmen
I haven’t updated to 2022.8.x yet, but I remember having issues with switching between the corb3000 branch and my own because of the incompatible way we generate unique id’s for the devices. If I’m not mistaken, a second set of devices get added to the list of entities (names ending with _1). I’ll update my Home Assistant this weekend if I can find the time, and fix my branch if needed. I’ve still not decided if I would jump on the branch @Breina created, but his and my branch are compatible at the configuration level (last time I checked anyway)
Merijn