X10 Community Forum
📱🖥️PiX10Hub => 🏥Help and Trouble Shooting => ⛑HA-Bridge help => Topic started by: bobbyds1 on February 17, 2021, 07:04:24 AM
-
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
-
sounds like HA-Bridge isn't running
If this is running on a Pi or linux type sudo systemctl status ha-bridge.serviceIf it states it has stopped you can restart with 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.
-
Thanks I will Try
-
I tried what you said to do and this was the response.
And when i tried the start command nothing happened.
-
Did you recently Update HA-Bridge to 5.4.0? If so did you load the right JAR file?
Have to tried a reboot?
-
I didnt update anything would it update automatically? in any
case how do i resolve the issue?
-
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
-
Can you point me in the direction of where to get putty. I would appreciate it.
-
Google really is your friend!
https://www.chiark.greenend.org.uk/~sgtatham/putty/
-
Thank you
-
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 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
-
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.
-
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
-
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.
-
did you increase or decrease the time
-
I don't remember exactly and each location would be different in any case. My city setting is 650 so I think my off grid place is lower maybe 450. ::) :'
-
even from within ha-bridge i cannot get my lights to turn off and on using the test on and test off buttons. but HG works ok. if you lower the
650 number to 500 should it respond quicker or longer. as i have gig speed internet. if that matters.
I also get this error in the log when i try to test on or off on a device.
-
If you can't control devices from HA-Bridge using the test buttons then that is your problem and not likely the delay setting.
Be sure your HomeGenie helper in HA-Bridge is set correctly proper port, IP, user name and password (if HG has been set with one).
Set the Other Types (opt) to Switch then update then save.
once HA-Bridge returns to the device page try a test again.
Note: Proper IP of HG is not 0.0.0.0 even if it is on the same device as HA-bridge
-
how do i change the ip address in the HG helper in ha-bridge when i try to highlight it i cant change it. also the 0.0.0.0.0 should be the ip address of what the pi unit or the pc i am accessing it from or what.
-
The IP should be device that HG is running from.
You don't need to high light the IP box just click on it and type in the ip (appears like it was never setup).
Since you have HG devices in HA-Bridge already how did you add them? Manually or old HA-Bridge using its helper?
-
old ha bridge. what should web sere be address of.
-
That stays the same. 0.0.0.0
Lets just get X10 working from the HA-Bridge device page using testing.
-
i changed the ip in hg for the ha-bridge ip to the correct ip. and now i cant get ha bridge to open in my browser i rebooted pi still cant access Ha-bridge ran the sudo command to check status of ha bridge and got this message
-
i changed the ip in hg for the ha-bridge ip to the correct ip. and now i cant get ha bridge to open in my browser i rebooted pi still cant access Ha-bridge ran the sudo command to check status of ha bridge and got this message
Now I'm total confused, ??? I never asked you to change anything in HG just HA-Bridge.
what ever you did undo it
-
Please refer to this link http://forums.x10.com/index.php?topic=30664.0
It should help setting up HA-Bridge.
-
I restored hg from a back up. but I still cant access ha-bridge do i need to reinstall
-
I restored hg from a back up. but I still cant access ha-bridge do i need to reinstall
Did you reboot? Try that first.
-
I rebooted a few times but still cannot access ha-bridge. also i even reinstalled ha-bridge 5.4.0 thinking that might help but no luck.
any suggestions
-
What port is HG set to?
Stop the HA-Bridge.service then
Go into the Ha-Bridge data folder and delete or rename the habridge.config file.
then restart HA-Bridge.
-
i did what you said and now I can access ha-bridge on my pc and alexa has found all devices and every thing is working.
Thank you so much Tuicemen I really appreciate all your Help.
-
Ok lets try opening the file to see what the settings are.
from the ha-bridge/data folder type nano habridge.config and paste the contents here
-
Ok lets try opening the file to see what the settings are.
from the ha-bridge/data folder type nano habridge.config and paste the contents here
Surely it would have been easier to point the OP to the source of your solution instead of transcribing the lot here. Users then might be able to understand a little more about the whole HA Bridge concept and how it works and how all these temporary workarounds come about https://github.com/bwssytems/ha-bridge/issues/1277
-
Surely it would have been easier to point the OP to the source of your solution instead of transcribing the lot here. Users then might be able to understand a little more about the whole HA Bridge concept and how it works and how all these temporary workarounds come about https://github.com/bwssytems/ha-bridge/issues/1277
I did point them to ha-bridge/issues!
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.
Obviously what was posted there either didn't help, or they never looked. ::) :'
-
Surely it would have been easier to point the OP to the source of your solution instead of transcribing the lot here. Users then might be able to understand a little more about the whole HA Bridge concept and how it works and how all these temporary workarounds come about https://github.com/bwssytems/ha-bridge/issues/1277
I did point them to ha-bridge/issues!
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.
Obviously what was posted there either didn't help, or they never looked. ::) :'
It might be a little more productive to encourage users to go to the sources of the information you supply for them. Besides the benefit of gaining a little more knowledge about the environment they are working in it also highlights the efforts others put in to provide these solutions and give them the due credit they deserve.
I’m still puzzled as to why the HA Bridge is still being used. HomeGenie provides all the tools necessary to create your own local Alexa service via UPnP. Once the SSDP is set up correctly, the UDP port and your Endpoints are defined you have the makings of a local Alexa service. Most of that work has already been done in HomeGenie and all you need to do is to adjust the above headings to reflect the current state of Alexa. Not a lot of work involved in that and the bonus of dispensing with a 3rd party service.
-
I’m still puzzled as to why the HA Bridge is still being used. HomeGenie provides all the tools necessary to create your own local Alexa service via UPnP. Once the SSDP is set up correctly, the UDP port and your Endpoints are defined you have the makings of a local Alexa service. Most of that work has already been done in HomeGenie and all you need to do is to adjust the above headings to reflect the current state of Alexa. Not a lot of work involved in that and the bonus of dispensing with a 3rd party service.
By all means take over and explain to the bobbyds1 and ayone else who may wish this knowlege.
This was to be a community effort but I only see a few contributing while others question why things aren't done a particular way. ::) :'
It also may be helpful if users spent some time and learned to only quote what is relavent. It realy does help things be less confussing. ;)
-
HomeGenie provides all the tools necessary to create your own local Alexa service via UPnP. Once the SSDP is set up correctly, the UDP port and your Endpoints are defined you have the makings of a local Alexa service. Most of that work has already been done in HomeGenie and all you need to do is to adjust the above headings to reflect the current state of Alexa.
@petera, I know this makes perfect sense to you and a number of others - but to 99+% of the world that sentence may have well been written in ancient Sanskrit. UPnP, SSDP, UDP, is as meaningful to most as MIC-KEY-MOUSE (at least they understand that one). Not to mention that most folks, sadly, can't even follow a short page of step-by-step instructions. We see it all the time here. We ask someone to do A, B & C to test something and maybe, we get 2 out of the three with some other counter-productive step added.
-
A simple pointer to the solution source saves all the typing. Speeds things up too.
Believe me I’ve given the solution so many times and the users ignore it by tagging the response with your name demanding your attention when there’s a problem. In case the guys here haven’t noticed this is a Linux environment when it comes to the Raspberry Pi, and believe me I know Linux. I don’t need to Google the answers.
I generally wouldn’t attempt to answer Windows related issues. That’s your domain. If the membership here feel you’re the only you that can answer their queries I won’t waste my time responding but hell, the queries go on for pages and many are resolved by the user themselves without even realising it.
If you feel you can run the entire gig yourself, by all means go ahead, it’s your forum not X10’s as I thought when I signed up. I know all about community effort, I participate in enough of them. One of the most annoying aspect of some of the participants are the ones who choose not to link to a source for the answer but for some reason choose to transcribe the answer verbatim without mentioning the source. I wonder why. No sources, no context and that’s where the problem lies.
-
HomeGenie provides all the tools necessary to create your own local Alexa service via UPnP. Once the SSDP is set up correctly, the UDP port and your Endpoints are defined you have the makings of a local Alexa service. Most of that work has already been done in HomeGenie and all you need to do is to adjust the above headings to reflect the current state of Alexa.
@petera, I know this makes perfect sense to you and a number of others - but to 99+% of the world that sentence may have well been written in ancient Sanskrit. UPnP, SSDP, UDP, is as meaningful to most as MIC-KEY-MOUSE (at least they understand that one). Not to mention that most folks, sadly, can't even follow a short page of step-by-step instructions. We see it all the time here. We ask someone to do A, B & C to test something and maybe, we get 2 out of the three with some other counter-productive step added.
Maybe you’re not asking the correct questions or maybe you’re not giving the users the credit they they deserve.
My reference to SSDP, UDP and Endpoints was clearly targeted at Mr T who mentioned a while back that he was going to get the Alexa bridge service with HomeGenie working a while back. So far nothing has happened and as a result users are having to spend unnecessarily on additional equipment like the Smartenit hub which frankly appears to be more trouble than its worth if recent postings are anything to go by.
As has been mentioned here before by a number of users, the purchase of a HomeSeer HomeTroller rrp $129.00 and half that at discount price would solve all these issues in one go. https://shop.homeseer.com/collections/smart-home-hubs/controller-level_advanced The typical user here is looking for a plug’n’go solution along the lines of AHP and that’s exactly what they get with that unit, and a dedicated technical backup when needed instead of messing around with sticking plaster solutions.
-
Yep, That's my point. Packaged Plug 'n Play solutions!
-
I'm sorry i didn't explain the solution thanks to Tuiceman for helping and pointing me to different things to try, Id be up ****s creek. So to get everything working i had to remove the habridge. config file as it had gotten corrupted. after i deleted it and rebooted pi, iwas able to access ha-bridge. From there i had to renumber all my devices in ha-bridge and then point the home genie reference under bridge control to the correct ip of home genie. After doing all that ask alexa to find all devices it found all my x-10 devices and everything works fine..
Again, Thank you Tuiceman for all your help and patience it is greatly appreciated..
regards,
Bobbyds1
-
My reference to SSDP, UDP and Endpoints was clearly targeted at Mr T who mentioned a while back that he was going to get the Alexa bridge service with HomeGenie working a while back.
I did not say I would get the echo bridge working! I said I may look at it.
Since clearly petera, you have it working or know how to, there is need to look at it.
I have currently 3 or 4 different ways to use Alexa with X10 (if I wished) I don't need a 5th. >!
-
I'm sorry i didn't explain the solution
No need to apologize, I'm just glad to see your up and running. :)% >!
-
I have a similiar issue. After a rebuild, I HA Bridge is not being discovered by Alexa. Any help would be appreciated.