Reply to thread

Message

<blockquote data-quote="pavke" data-source="post: 1178639" data-attributes="member: 11916">Hi Rick,Today I had another go at it. First I uninstalled my Norton Internet Security (antivirus + firewall), then tried to connect to the bridge - alas with the same results. Btw, when first time trying Windows Firewall came up asking for permission for AtmoHue, which I granted - to no obvious avail. I then disabled the firewall completely, tried again - but again no joy.Things stay the same : not finding the bridge when 'Windows 8' is ticked (I guess that's the idea, although I'm on Windows 10 ?), but finding it without problem 'using standard discovery' when this is unticked.What I don't understand is that it DOES find the bridge (OK, using the 'older' method, but which should still do the job, no ?), but then can do nothing useful with it ?Anyway, I'm really at a loss why it doesn't work - especially so because (like I said before) the android app works absolutely flawless with it, on the same network...I'm including my settings file for your perusal. For whatever it's worth, because the only thing that's changed from the default settings would be the bridge's ip address, as it was found using 'standard method'.PS&nbsp; One bug I'd like to signal is that when during the very first run of Atmohue it fails to find the bridge, it is impossible to enter the program again (it starts, but shuts down immediately). Seemingly it cannot cope with a settings.xml file with an empty IP number ?To get it going again, one has to delete the settings file and start over again...</blockquote>

[QUOTE="pavke, post: 1178639, member: 11916"] Hi Rick, Today I had another go at it. First I uninstalled my Norton Internet Security (antivirus + firewall), then tried to connect to the bridge - alas with the same results. Btw, when first time trying Windows Firewall came up asking for permission for AtmoHue, which I granted - to no obvious avail. I then disabled the firewall completely, tried again - but again no joy. Things stay the same : not finding the bridge when 'Windows 8' is ticked (I guess that's the idea, although I'm on Windows 10 ?), but finding it without problem 'using standard discovery' when this is unticked. What I don't understand is that it DOES find the bridge (OK, using the 'older' method, but which should still do the job, no ?), but then can do nothing useful with it ? Anyway, I'm really at a loss why it doesn't work - especially so because (like I said before) the android app works absolutely flawless with it, on the same network... I'm including my settings file for your perusal. For whatever it's worth, because the only thing that's changed from the default settings would be the bridge's ip address, as it was found using 'standard method'. PS One bug I'd like to signal is that when during the very first run of Atmohue it fails to find the bridge, it is impossible to enter the program again (it starts, but shuts down immediately). Seemingly it cannot cope with a settings.xml file with an empty IP number ? To get it going again, one has to delete the settings file and start over again... [/QUOTE]

Verification