AtmoHue - BETA - Philips Hue support for AtmoLight & AtmoWin (2 Viewers)

[killer8]

Did some testing with the new atmoHue and atmoLight and it seems a great improvement I've set atmolight to control atmohue power settings and configured atmolight to put on and off the bridge when going into and getting out of standby. It works just great. Well done!

One thing i'm wondering about, are you going to release the atmoHue as a mp1 plugin package like atmowin is?

 

[Rick164]

Thanks

Should be possible but would need a fixed install path I think to allow for upgrades, gotten used to the MPEI maker for AtmoLight now so should be easy to package it.
Gonna add a few more features soon like the individual light setups while keeping the lights in sync which is gonna be a tough one to do right, once that is completed I'll start bumping the version to 0.1 and release an MPEI as well.

 

[killer8]

Sounds good. Incase I find any bugs or have an idea about improvements I will tell you.

 

[TheBatfink]

Hi, finally got around to trying to set this up, as per usual it looks like I'm stupid..

How do you add LED's? How do I know what the ID of the bulb is? I'm curious why it didn't retrieve the bulbs from the Bridge (I've seen other windows based apps do this).

I've just added ID 1, 2 and 3 as I currently have 3 bulbs. I can see in atmohue that it has found the bridge and claims to be connected. Also during movie playback it claims in the log to be setting colours and then completed sending those colours yet I don't see the bulbs responding? The test tab doesn't work to set colours either. I have MePo and Atmohue set as trusted apps in Kaspersky and I've also tried disabling the software to see if the firewall is blocking it.. I can't imagine my router is blocking anything as it's working fine from the Philips apps.

I followed the instructions on the WIKI but I must be missing something (I noticed there are additional settings in some of the screens compared to the screen shots but I think I followed it OK).

I'm using MePo 1.10Pre and your latest release of AtmoLight and AtmoHue from yesterday.

Thanks!

 

[killer8]

Since nothing is working, did you press the button on your hue bridge when connecting?

The additional settings on the wiki are most likely removed/replaced in the newer version.

 

[TheBatfink]

Yes and it found the bridge. I'll redo the process again with debug on so the log is complete and post some screens of my settings.

So I cleared the settings.xml of Atmohue and restarted my PC. I have left my Atmolight configured the way I had originally with respect to the Wiki. Here are the Generic Settings and Hue tabs screenshots:



I then:
1) Loaded up Atmohue
2) Enabled the debug log and remote api log check boxes
3) Enabled the remote api checkbox (not sure if I need to do this)
4) Enabled the auto connect if bridge found check box
5) Clicked the locate and register hue bridge button
6) Pressed the button on my Hue then clicked OK button on the Atmohue messagebox prompt as instructed
7) Atmohue settings populate with IP address, app name and key etc.
8) Clicked the LEDS tab and input my three lights and gave them ID 1, 2 and 3 (my setup currently contains 3 Hue bulbs, 1 bridge and 1 Hue Tap)
9) Clicked the testing tab and clicked the colour test buttons one by one. Result: nothing happens and the lights remain in the off state
10) Clicked the Experimental table and clicked the colour test buttons one by one. Result: nothing happens and the lights remain in the off state
11) Clicked the Retrieve scenes and log button. Result: nothing appears to happen


I then fired up the lights with the Hue App and closed the Hue App. I repeated steps 9 through 11. Result: Lights remain on the colours I set with the Hue App and do not change. Nothing appears to happen when clicking the retrieve scenes button.

Here are my Atmohue settings screen shots and the debug log file / settings.xmk.



I then closed and re-opened Atmohue with the lights still in the on state. I see in the log: HUE has been initialized on startup. I repeat steps 9 through 11. Again I see no change in the colour of the lights but I do now see some new log entries in the app relating to scenes as per the below screen shot. I have many more scenes configured than this though?



I realise in the images that the config boxes are chopped off the bottom. The config screen is not resizable and when dialing into the machine with my laptop on remote desktop to take these images etc. my resolution can not display it all without hiding the taskbar. It would be nice if the form was resizable vertically and maybe anchor your log control so it resizes with the form Here is another screen shot with the taskbaer hidden where you can see the control on the bottom of the form is claiming it is Connected OK.



So basically it just doesn't seem to work (probably something I have configured wrong?). Any help would be much appreciated I hope this is all clear enough!

EDIT: Added a second debug log after my last test..

 

[Rick164]

How do you add LED's? How do I know what the ID of the bulb is? I'm curious why it didn't retrieve the bulbs from the Bridge (I've seen other windows based apps do this).

Will look into this, thought it wasn't possible as I didn't see any mention in the Q42 API.
The ids should be listed in the Philips Hue App as follows:

I realise in the images that the config boxes are chopped off the bottom. The config screen is not resizable and when dialing into the machine with my laptop on remote desktop to take these images etc. my resolution can not display it all without hiding the taskbar. It would be nice if the form was resizable vertically and maybe anchor your log control so it resizes with t
he form

Gonna see if that is possible as the tabbed layout does have some restrictions but should be able to anchor the output log to a groupbox.

So basically it just doesn't seem to work (probably something I have configured wrong?). Any help would be much appreciated I hope this is all clear enough!

The config screenshots look ok and you detailed the steps nice and clear, the initialize mention does mean it was able to connect to the Hue Bridge.
You might try to let it register again to make sure it has registered correctly the first time, since the scenes retrieval worked it probably is already registered though.

Currently there's no debug option after we send colors as I dropped the callback function of the bridge (slowed down color changes), will see if there's a function to check command status more reliably without slowing down color changes.
It might be because they're bulbs as they have different color settings but they should at least turn on, are they the Bulb Lux or Bulb Color?

Btw what I did notice about your settings.xml is that it doesn't list the LED ids which probably means AtmoHue hasn't restarted yet or something went wrong during save, could you upload a new copy of your settings.xml?
Currently rewriting the save/load parts and cleaning up the code so should have new version this weekend, gonna see if I can include an auto-discover led devices as well as some more debug functions.

/EDIT: attached a test version that has a "Get LED IDs" button in the experimental tab which will output all found devices in the log window.
Also found a partial device type list so based on that I could automatically add them to the LED id list but needs some more testing.

 

[TheBatfink]

Rick, check out Winhue 2 / 3. I think it has a lot of features you may like if Atmohue goes further along than just mimicking Atmos It's open source and on sourceforge. It is a bit broken right now but he's active and a new RC for Winhue 3 is coming shortly.

Without touching anything other than rebooting the machine, I am noticing shortly after launching MePo, whilst WinHue is being auto loaded and I see the log message Hue has been initialized on startup, a context menu is appearing inside MePo from Atmolight that Hue connection has been lost. Maybe this is a symptom of my issue? It says in MePo log it's been refused? Could this be firewall activity then?

Anyhow.. attached is my current settings.xml - in Winhue itself I see the ID numbers and names of the bulbs so it must be reading them from somewhere? Also for info these are the coloured bulbs. The are the standard Edison screw type (not the GU10 spots or the Lux).

I'm trying your test version now. Thanks!

EDIT: Tested the new version. I completely deleted the old files and restarted Winhue before proceeding after it found the hub. After hitting the new button a messagebox is displayed asking to check the log window for the ids. The window does not have any messages other than the initialize at startup entry and neither does the debug log. For info I closed Kaspersky before doing this test.



I've also include a shot of the Hue app. The bulbs do appear as 1,2 and 3.



EDIT 2: Just to be doubly sure I have set IP reservation for the Hue on my router so the IP will remain constant and setup a service and port forward rule that everything on the port indicated in Winhue goes to this IP. Still won't work

 

[Rick164]

Rick, check out Winhue 2 / 3. I think it has a lot of features you may like if Atmohue goes further along than just mimicking Atmos It's open source and on sourceforge. It is a bit broken right now but he's active and a new RC for Winhue 3 is coming shortly.

Checked out their source and while its approach is much better than AtmoHue it has a pretty large codebase to look thru and is using its own Hue library which means adoption the code isn't directly possible, AtmoHue relies on the Q42 API which has most of the functionality in it just without any sort of documentation which is making it harder to find out how each function is supposed to work but slowly getting there.

The initial purpose of AtmoHue was to be more of a helper app for AtmoLight and AtmoWin (basically forward average color to Hue) but along the way it became a bit more, once they release a working version of WinHue 3 I'll definitely start mimicking some of its functionality though

EDIT: Tested the new version. I completely deleted the old files and restarted Winhue before proceeding after it found the hub. After hitting the new button a messagebox is displayed asking to check the log window for the ids. The window does not have any messages other than the initialize at startup entry and neither does the debug log. For info I closed Kaspersky before doing this test.

Very odd, sounds like the AtmoHue connection is being blocked somehow by a firewall and believe Killer8 had the same problem in the beginning.
Could you maybe check on another machine to see if it's working there?

Also the connection status bar has to be taken with a grain of salt, it isn't actively monitoring the connection (only on register / init ) at the moment but have found a way to improve that so that will be added in the next version.

Btw for it work in Mediaportal the Remote API box must be checked in AtmoHue so that error is expected , the documentation for enabling it for use in AtmoLight is located here:

https://github.com/ambilight-4-mediaportal/AtmoLight/wiki/Hue-setup-guide

Anyhow.. attached is my current settings.xml - in Winhue itself I see the ID numbers and names of the bulbs so it must be reading them from somewhere? Also for info these are the coloured bulbs. The are the standard Edison screw type (not the GU10 spots or the Lux).

Yeah there should be a complete list out there with product IDs and gonna pull that out the WinHue source, colored bulbs would mean it should work the same as the blooms so that's good news.

 

[killer8]

Very odd, sounds like the AtmoHue connection is being blocked somehow by a firewall and believe Killer8 had the same problem in the beginning.
Could you maybe check on another machine to see if it's working there?

I always had the error in my mediaportal-error log when it couldn't connect. But somehow it works fine now even after an upgrade.

@TheBatfink One thing I noticed in your screenshots, I have Running Windows 8.* checked, as far as I know this gives another methode to detect the lights.

Apart from that, you also have to check "remote api" to use it with atmoLight.

Another thing that's different from me, in my setup the port is added to the ip address automatically(most likely because I checked, Running Windows 8.*)