home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
HTPC Projects
Hardware
Ambient Lighting System
AtmoHue - BETA - Philips Hue support for AtmoLight & AtmoWin
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="TheBatfink" data-source="post: 1110088" data-attributes="member: 52265"><p>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 <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> 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.</p><p></p><p>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?</p><p></p><p>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).</p><p></p><p>I'm trying your test version now. Thanks!</p><p></p><p>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.</p><p></p><p>[ATTACH]157607[/ATTACH] [ATTACH]157608[/ATTACH]</p><p></p><p>I've also include a shot of the Hue app. The bulbs do appear as 1,2 and 3.</p><p></p><p>[ATTACH]157609[/ATTACH]</p><p></p><p>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 <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown :(" loading="lazy" data-shortname=":(" /></p></blockquote><p></p>
[QUOTE="TheBatfink, post: 1110088, member: 52265"] 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. [ATTACH]157607[/ATTACH] [ATTACH]157608[/ATTACH] I've also include a shot of the Hue app. The bulbs do appear as 1,2 and 3. [ATTACH]157609[/ATTACH] 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 :( [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Hardware
Ambient Lighting System
AtmoHue - BETA - Philips Hue support for AtmoLight & AtmoWin
Contact us
RSS
Top
Bottom
