Echo Gen 2 not discovering emulated hue using habridge, phone and pc app can

[happyhammer]

Hi All, Before i brought the ECHO gen 2 i had set up Habridge to point to Domoticz devices. After setting up and performing device discovery it found all 3 habridge devices and Hive all seemed ok. I then added more devices to Habridge , performed new discovery and it did not find any new devices, forgot all devices and tried again, only found Hive. Went through various tests of habridge, seems to be set up ok. Using a Hue app on both phone and PC it finds all hue emulated devices but ECHO still does not. Looking at the habridge log file using the apps it initiates the discover process and at some point i see this in the log.
 Nov 22 11:02:43 debian java[12103]: 2017-11-22 11:02:43,617 [qtp1545494647-11] INFO  com.bwssystems.HABridge.hue.HueMulator - Traceupnp: hue api/:userid/config config requested             : nouser from 10.8.0.10
Nov 22 11:02:43 debian java[12103]: 2017-11-22 11:02:43,880 [qtp1545494647-13] INFO  com.bwssystems.HABridge.hue.HueMulator - Traceupnp: hue lights list requested: 1add5115e74e             4598b2d5261d04e3158d from 10.8.0.10
Nov 22 11:02:51 debian java[12103]: 2017-11-22 11:02:51,976 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: sendUpnpNotify notifyTemplate is <<<NOTIFY * HTT             P/1.1

But using ECHO I do get some logs
Nov 22 11:00:42 debian java[12103]: 2017-11-22 11:00:42,042 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: isSSDPDiscovery found message to be an M-SEARCH              message.
Nov 22 11:00:42 debian java[12103]: 2017-11-22 11:00:42,043 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: isSSDPDiscovery found message to be valid under              strict rules - strict: true
Nov 22 11:00:42 debian java[12103]: 2017-11-22 11:00:42,044 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: SSDP packet from 192.168.0.50:50000, body: M-SEA             RCH * HTTP/1.1

But it never gets the hue lights list requested: 1add5115e74e4598b2d5261d04e3158d.

I tried new habridge on pi, same things apps see devices, echo does not.
Not sure what else to try next, Upnp is enabled on router, habridge ok, apps finds devices but echo does not.
Any ideas ? Thanks Dave

[tuicemen]

You really should report this in the HA-Bridge issues.
Have you tried the latest RC build?
If not get it as it has several enhancements and fixes.

[happyhammer]

It is the latest habridge software. I initially thought it was habridge issue, but it worked initially, I only added a new device. Both the phone app and 2 PC apps on windows 10 find the devices. Homeassistant on another pi finds and controls the devices just not the echo. I can see the devices in the api habridge webserver/ pages, why do you think the issue is with Habridge when 3 other apps can find the devices on the emulated bridge ? Thanks Dave

[tuicemen]

The 2 PC apps you run use the HA-Bridge and  I suspect the pi apps too. Controlling devices from other apps which use the Bridge or using the bridge its self to control the devices has no bearing on Alexa discovering devices. Since you say you controlled prior but can't now, I suspect it is one of two things. Either you were controlling using a HA-Bridge version prior to v5 RC 7 and RC 7 has a bug or and most likely you updated Java and not updated your firewall rules for the new java version.

[happyhammer]

Hi Was using 4.5.5, have since tried 4.5.6 and just tried 4.0.0 ports 80 and 8081, the app on the phone finds the habridge all versions and then finds the switches. If it was a java issue on the linux machine hosting habridge how is it that the app can find the devices but echo can not ? Not sure what machine you mean by the firewall, host linux machine ? Router or windows pc ? Android phone has no firewall. PI instructions state oracle-java8-jdk and that is the version currently installed. Any ideas what to try next ? Thanks for your help Dave

[tuicemen]

Best to get one thing working at a time. If you remember the Bridge version everything worked with revert back to in on the Windows machine then open your windows firewall settings and look for inbound rules for java.
With the bridge not running on the windows machine, delete the java rules and close the firewall settings.
with that done click on the HA-Bridge .jar file this should throw up a windows popup asking to allow Java. Click yes.
then with your echo or Alexa app try to discover devices.
If Alexa finds devices then update to newest bridge and test again (I suggest the v5 RC 7 build)

I suspect Version 5.0.0 of the bridge to be released any day now as there have been not issues reported with it in since RC7 was available (almost a week).

[happyhammer]

Hi I'm running Habridge on linux machine not windows, however to help investigate i will try to set up on windows using V5 and let you know. Cheers Dave

[tuicemen]

Ok, I assumed since you were running 2 windows apps you had ha-bridge running on it.

[StevenR]

I see you are using Home Assistant, this has its own emulated Hue bridge (the emulated_hue component) have you tried using that instead of habridge?

[asianrocker]

Ok sorry to hijack your thread but ha bridge still need an actual hue bridge and hub correct? That's what I get from reading about it.

Just bought a starter kit but needs to be exchanged.

[tuicemen]

It only needs a hue hub for hue lights I believe.
I have no Hub of any sort and control things with it.
I also have no Hue bulbs

[asianrocker]

Ok so ha bridge is working as a hub without a physical hub? What lights can you control with this? Not hue, but any light? Any smart bulb except hue bulbs? You can also control any TV with this? Like my Samsung smart TV?

I need to read more about this. From what I read before you need an AWS account? That's what made me not do it.

[tuicemen]

Ok so ha bridge is working as a hub without a physical hub?

(in my situation yes)

What lights can you control with this? Not hue, but any light? Any smart bulb except hue bulbs?

I control mostly X10 lighting but any smart bulb that doesn't require a hub probably could be used

You can also control any TV with this? Like my Samsung smart TV?

I control (poweron/off) my TV, cablebox, Blueray player however my setup is a bit complicated. Controling a smart TV should be easy

I need to read more about this. From what I read before you need an AWS account? That's what made me not do it.

You don't need a AWS account

[asianrocker]

Thank you, tuicemen I will definitely explore this ha bridge then. Too bad I gave in to hue starter kit but I think I got a good deal. And now I have voice activated lights. Woot.

[happyhammer]

Hi, i have home assistant on another pi2 and emualted hue, pi1 is the original linux machine running domoticz and habridge. pi2 can see domoticz devices and pi1 habridge can import pi2 home assistant devices. I still can not get Alexa to see either pi1 habridge devices or pi2 homeassitant via emulated hue devices. Tried new version 5 still Alex see's no devices.
Started from scratch with just pi1 running domoticz and habridge, when habridge has no devices added, i get Alexa to discover devices it seem to be complete process, from logs i can see this,
Nov 23 14:05:01 debian java[7774]: 2017-11-23 14:05:01,748 [qtp2134582552-111] INFO  com.bwssystems.HABridge.hue.HueMulator - Traceupnp: hue lights list requested: 73e2f2b2d41c4aeda6e4420d36b9e32f from 192.168.0.50
Nov 23 14:05:06 debian java[7774]: 2017-11-23 14:05:06,942 [qtp2134582552-106] INFO  com.bwssystems.HABridge.hue.HueMulator - Traceupnp: hue lights list requested: 73e2f2b2d41c4aeda6e4420d36b9e32f from 192.168.0.50
Nov 23 14:05:10 debian java[7774]: 2017-11-23 14:05:10,410 [qtp2134582552-113] INFO  com.bwssystems.HABridge.hue.HueMulator - Traceupnp: hue lights list requested: fc57d0ba41274112ad7204cc01671c36 from 192.168.0.49

192.168.0.50 is the Alexa and 192,168.0.49 is the other pi running home assistant. Now if i add a device to habridge either using the Domoitcz built in process, or just adding a manual switch, home assistant pciks up the switch no problem and i can control it from the other pi2 running home assistant no problem, now i do another discovery on Alexa, no switch found. looking at log i do not see com.bwssystems.HABridge.hue.HueMulator - Traceupnp: hue lights list requested: 73e2f2b2d41c4aeda6e4420d36b9e32f from 192.168.0.50 from Alexa but i do see it from pi2 home assistant
INFO  com.bwssystems.HABridge.hue.HueMulator - Traceupnp: hue lights list requested: fc57d0ba41274112ad7204cc01671c36 from 192.168.0.49

I've tried running habridge on 2 pi's, different versions same issues, Alexa seems to successful   request if habridge has no devices. Strange thing is the very first time i set up Alexa it found them, not sure where to go from here ? will also post on habridge to see if anyone else has had this issue. Thanks