jeffreykog / artnet-hue-entertainment Goto Github PK

I think last Halloween I got this to run (I might of just stuck with Dmx-Hue), but I'm running into problems this year with a new install. Here are the steps so far.

1. git clone https://github.com/jeffreykog/artnet-hue-entertainment.git
2. cd artnet-hue-entertainment
3. npm install
4. node build/cli.js discover
5. node build/cli.js pair --ip 192.168.xx.xx
6. node build/cli.js list-rooms

This all works. I can see the Hue and show the entertainment room that I setup in the app. When I try to run node build/cli.js run it comes back with an error saying "Not all the lights in the Entertainment room have been configured".

If I comment that error out, the next step it has problems binding the IP address. "Bind host 172.24.184.16 does not match any network interface"

Im a newbie to all of this stuff so sorry for my dumbness :D

I created the entertainment group on my phone but how exactly do i run the software?
Im using Windows 10 and would like to control my hue lightbulbs via dmxcontrol2.

Thanks for your help

Hello everybody,
Thanks for all the job.
Just a question, it is possible to run artnet-hue without internet connexion?
Everythings works well. but it is very restrictive to need this connexion for the initial run.
Thanks

Lucas

Dependency should be updated to the newest version, but that's not possible currently due to an upstream issue. This issue exists to track the upstream issue. See peter-murray/node-hue-api#206 for more information.

We managed to set it up properly, but for some reason the lights are flickering on and off irregularly and very fast, like multiple times a second. What could cause this?

In newer versions of the Hue app it is no longer possible to create generic entertainment rooms. You either pair with a Hue Sync Box that creates the entertainment room by itself, or you use the Windows/Mac sync application which also creates the room by itself.

We should check if node-hue-api has API for this. It appears they don't, so we need to implement this on our own.

API documentation: https://developers.meethue.com/develop/hue-api-v2/api-reference/#resource_entertainment_configuration_post

Currently the Hue bridge is automatically put into Entertainment mode when this application is started. The goal is that this application can keep running permanently as a daemon on a machine, and only starts entertainment mode when you want to control your lights with ArtNet. In order to support this we should add an OSC interface, so we can command artnet-hue-entertainment to start/stop entertainment mode. This can then be controlled from something like Bitfocus Companion.

Hi, I have some trouble with getting this to run:

I have added the EntertainmentId and Lights to the "build\cli.js" file, but every time I try to run the software I get the following error:
Error: Not all lights in the entertainment room have been configured (lists all the lights IDs in that Entertainment room)

I have 2 entertainment rooms, so I tried to change the ID to the other room, but it still lists the lights from the first room, no matter what.

There must be something I have missed, but I don't know what?

This is how I installed it:

1. Downloaded the code and extracted it
2. Install Node.js on the computer (I already had the latest version)
3. Open Node.js command prompt and cd C:\path\to\where\you\extracted\the\code
4. npm install package.json
5. npm install minimist (it was missing for some reason?)
6. artnet-hue-entertainment discover
7. artnet-hue-entertainment pair --ip "ip.to.bridge"
8. artnet-hue-entertainment list-rooms
9. change "cli.js" file with Entertainment ID and Lights IDs
10. artnet-hue-entertainment run

Hi there,

I tried installing the package using "npm i artnet-hue-entertainment" and whenever I tried to call it afterwards in powershell I'd get an error message saying it's not recognized. (I'm running windows 10x64-bit if that info is relevant)

I also noticed that when I used this command to install that no files get installed locally in my npm directory, so I tried installing again using "npm install -g artnet-hue-entertainment", which does cause the package's files to get installed locally. However, then if I try to run artnet-hue-entertainment in powershell, I only get a response "Help" and immediately get put back to the original command line.

I've never had trouble installing and running nodejs packages before (hue-dmx for example), and am not quite sure what to do in order to get arenet-hue-entertainment up and running. Any help would be much appreciated, thanks!

I have built the app and configured it to successfully pair with my Hue Bridge. Upon 'artnet-hue-entertainment run', itsets the 3 configured bulbs off and acknowledges that it's in streaming mode with the Bridge. However, it doesn't seem to recognize any ArtNet messages that are sent, nor respond to ArtPoll messages. The bulbs just stay black.

I'm new to ArtNet, so any ideas are appreciated :)

Screenshots attached:

• Terminal showing ArtNet node successfully running
• Hue app showing Hue Sync is active
• DMX viewer showing DMX data is being sent
• Wireshark output showing DMX channel changes, and ArtPollReply to a different device, but failed Poll once that device was turned off.
• cli.js excerpt with bulb configuration

The ArtNet protocol mandates that every node replies to ArtPoll packets for discovery of nodes in the network. We don't currently do this, but in order to be compliant with the protocol, we need to implement this.

What an awesome project! I've been looking for a way to link my Hue lights to my dmx lighting software for a while.

However I'm having trouble setting this up. The bridge successfully connects to my Hue Bridge, but I can't find the ArtNet bridge in my DMX lighting software (I'm using Lightkey which supports Art-Net). I'm using two separate macs for Lightkey and artnet-hue-entertainment.

Here are the steps I took to set this up:

1. Cloned repo, installed dependencies
2. Changed the ip, username and password in the index.js file to match my Hue Bridge
3. In artnet.js I updated the entertainmentRoomId and lights to match the values on my Hue Bridge
4. I set the artNetBindIp to the IP address of my computer running artnet-hue-entertainment.

Here are the logs collected:

/usr/local/bin/node ./build/index.js
Binding broadcast address 192.168.1.255:6454
Binding unicast address 192.168.1.204:6454
Requesting streaming mode...
Streaming enabled: true
Sleeping for 3s to give the Hue bridge time to enable streaming mode
ArtPoll ArtPoll {opcode: 8192, protocolVersion: 14, sendPollReplyOnChange: true, sendDiagnostics: false, sendDiagnosticsUnicast: false, …}
Unknown packet type: 32768
ArtPoll ArtPoll {opcode: 8192, protocolVersion: 14, sendPollReplyOnChange: false, sendDiagnostics: false, sendDiagnosticsUnicast: false, …}
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12292, …}
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12292, …}
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12292, …}
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12292, …}
Unknown packet type: 32768
Performing streaming mode handshake...
Connected and ready to go!
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12548, …}
Unknown packet type: 32768
ArtPoll ArtPoll {opcode: 8192, protocolVersion: 14, sendPollReplyOnChange: true, sendDiagnostics: false, sendDiagnosticsUnicast: false, …}
Unknown packet type: 32768
ArtPoll ArtPoll {opcode: 8192, protocolVersion: 14, sendPollReplyOnChange: false, sendDiagnostics: false, sendDiagnosticsUnicast: false, …}
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12292, …}
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12292, …}
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12292, …}
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12292, …}
Unknown packet type: 32768
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12548, …}
Unknown packet type: 32768
Unknown packet type: 32768
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12548, …}
Unknown packet type: 32768
ArtPoll ArtPoll {opcode: 8192, protocolVersion: 14, sendPollReplyOnChange: true, sendDiagnostics: false, sendDiagnosticsUnicast: false, …}
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12548, …}
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12548, …}
ArtPoll ArtPoll {opcode: 8192, protocolVersion: 14, sendPollReplyOnChange: true, sendDiagnostics: false, sendDiagnosticsUnicast: false, …}
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12548, …}
ArtPollReply ArtPollReply {opcode: 8448, version: 0, netSwitch: 0, subSwitch: 0, oem: 12548, …}

Note: every time I run Art-Net bridge discovery in Lightkey, I get the following warning in the log Unknown packet type: 32768.

The recent suggested update to use a configuration file looks like a really good idea. If you do implement this, would it be possible to add the ArtNet Universe to the configuration file as well? This would solve the problem I mentioned before of my Hue lights responding to commands sent to control my DMX lights which are on a different universe. I use a 3 Showtec Net 2-3 interfaces on different Artnet universes. It seems it would be quite straight forward to implement by someone that knows what they are doing, unfortunately I don't have the skills to know how to do this correctly. I have just hacked the module called controller.js to ignore anything that isn't destined for Artnet universe 0. This works for my setup, but I know this isn't the correct way of implementing this. In case it helps, this is the change I made to the onSocketMessage method in controller.js

onSocketMessage(socketType, msg, rinfo) {
    const packet = protocol_1.decode(msg);
    if (!packet) {
        return;
    }
    if (packet instanceof protocol_1.ArtDmx) {
    if (packet.universe == 0) {		//GTB
          this.emit("dmx", packet);
    }					//GTB
    else {				//GTB
	return;				//GTB
    }
    }
    else if (packet instanceof protocol_1.ArtPoll) {
        this.sendArtPollReply();
    }
    else if (packet instanceof protocol_1.ArtPollReply) {
    }
    else {
        console.log(packet.toString());
    }
}

It would be great if this came from the proposed configuration file and was implemented by someone who knows how to do this correctly.

Thanks.

UPDATE: After days of trying to understand what was going on and an hour after posting the message below, I finally figured out what was happening. I think it is just a matter of you not having got around to parsing the universe network yet. As you say, it's a work in progress. I've found a place to insert a couple of lines of code to make it ignore DMX data that's not for ArtNet universe 0. Everything is working as expected now. You've created a great project.

Thanks.

I think my problem is probably just because this project is still a work in progress, rather than a bug. But I thought I'd raise it anyway, just in case.

I've got 10 hue lights in my entertainment group and so far, they all seem to be working fine with my DMX software via the artnet-hue-entertainment script. The problems occur when I try and add proper DMX lights to another ArtNet universe. The artnet-hue-entertainment script appears to be listening to the data on all ArtNet Universes rather than just one.

My DMX lights are connected via an external Ethernet ArtNet to DMX interface. I've set a unicast IP address in my software for the interface and for the hue-entertainment controller, but this hasn't helped.

I've also tried moving my two DMX lights to different DMX addresses so they don't overlap with hue lights, even though they are on a different ArtNet universe. That helps a bit as it seems to stop data for the DMX lights going to the hue lights, but they are still affected by other data my control software sends out. If I completely disable the output to the ArtNet universe the DMX lights are attached to, then the hue lights work fine.

The hue lights respond no matter what universe I tell my controller they are on.

I don't know Javascript, but it looks as if at the higher level functions of the code an ArtNet network number isn't being configured, though at the lower levels it seems to be aware of the network parameter. I feel that by hard coding a line that says IF UNIVERSE == x THEN ... I'd get a temporary work around. Though I really don't know where to insert it without it potentially messing something else up.

As I said, I think this is most likely just something you haven't got around to implement yet.

Great piece of work, well done. It's been something I've been looking for ever since I found I wanted to expand my light system beyond what hue was capable to doing. Thanks for your efforts.

Gavin

Just briefly, I got hit by this issue - peter-murray/node-hue-api#221 (comment)

Solution was to update discovery.nupnpSearch() to discovery.mdnsSearch(). It was all good after that.

Ps. Just wanted to say thanks so much for working on this. It was on the "I wish the existed" list for the longest time - I'm just experimenting with it now :)