Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[bobbyds1]

when i enter the ip address for ha bridge 000.0.0.0:80 it responds.  but when i enter the ip for home genie 000.0.0.0:8080 it will open home genie.  Can some one help me with this all was good till i had the power go out.

Can someone please help

Thanks in advance

[Tuicemen]

sounds like HA-Bridge isn't running
If this is running on a Pi or linux type

Code: [Select]

sudo systemctl status ha-bridge.serviceIf it states it has stopped you can restart with

Code: [Select]

sudo systemctl start ha-bridge.service
If it is on Windows check your rules for java. Windows updates always mess this up and you'll need to remove any rules for java. Then restart HA-Bridge, a new security window will pop up to wish you click on the yes button.

[bobbyds1]

Thanks I will Try

[bobbyds1]

I tried what you said to do and this was the response.

And when i tried the start command nothing happened.

[Tuicemen]

Did you recently Update HA-Bridge to 5.4.0? If so did you load the right JAR file?
Have to tried a reboot?

[bobbyds1]

I didnt update anything would it update automatically? in any
 case how do i resolve the issue?

[Tuicemen]

Just to confirm HA-Bridge is on port 80 and HomeGenie is on port 8080?
I assume this is a PiX10Hub image correct?
I'd update to the latest HA-Bridge, it will not do it automatically.
http://forums.x10.com/index.php?topic=31419.msg186512#msg186512

[bobbyds1]

Can you point me in the direction of where to get putty.  I would appreciate it.

[Tuicemen]

Google really is your friend!
https://www.chiark.greenend.org.uk/~sgtatham/putty/

[bobbyds1]

Thank you

[bobbyds1]

I updated to ha-bridge 5.4.0 i can now access ha-bridge but alexa does not find any of my X10 lights when i run discovery.

Need some help!

[petera]

I updated to ha-bridge 5.4.0 i can now access ha-bridge but alexa does not find any of my X10 lights when i run discovery.

Need some help!

I don’t really want to get involved in this discussion but after “another Alexa firmware update” you’ll find a solution to your problem here. Prepare yourself for regular breaks in functionality of the HA Bridge and what you’ll need to do to resolve them. Keep this as a reference point for yourself https://github.com/bwssytems/ha-bridge/issues/1286

[Tuicemen]

HA-bridge uses the Philips Hue api to talk to Alexa, the notion that “another Alexa firmware update” will break your Alexa Isn't 100% accurate. However this seems to be what most people report as the issue. What does break Alexa connection from HA-Bridge is a Windows Update due to Java security certificates. Or users renumbering devices that have be discovered already. Or users changing the IP or port of HG.
Setting up IP reservations in ones router will help a lot

Most users here have moved to other alternatives to HA-Bridge/HomeGenie for Alexa. It is best to look at https://github.com/bwssytems/ha-bridge/issues as petera suggested. Chances are someone has ran into the same issues and posted there. bwssytems has a good handle on the software and can usually quickly get a issue sorted out.

[bobbyds1]

I can now have alexa discover my devices but now alexa tells me device not responding please check the network connection and try again.
does any one know how to correct this. Attached is a copy of my log

[Tuicemen]

What I found early on using HA-Bridge was you need a reliably quick network. Any slow down will cause Alexa to fail.
 Play with the "UPNP send delay" setting in the HA-Bridge config page. The default setting works most of the time but I found without ajusting this at my offgrid place Alexa would fail to activate a device even after successfully adding it. I also had to readjust this setting this summer when my DSL connection speed was increased. Interestingly our city broadband connection speed just increased (after a yearly squabble with our ISP) and I didn't need to addjust this. However Alexa responces are faster now.
 I still strongly suggest you read throught the issues at the HA-Bridge github, look through both the current and resolved issues.