Announcement

Collapse
No announcement yet.

HA-Bridge - EU/UK direct control of devices

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Originally posted by reggs11 View Post
    Hi Jon, nope. I've only re-Discovered\re-scanned. I'll try that later.
    Tried it, all 60 odd devices discovered again but same error.
    This one truly has me flummoxed

    Comment


      Originally posted by reggs11 View Post
      Tried it, all 60 odd devices discovered again but same error.
      This one truly has me flummoxed
      Found the problem. You get this error if you uncheck Setup->Tools->Network(TAB)
      No Password Required for Local/Same Network Login (Web Browser/HSTouch)

      When checked it works fine

      Comment


        That's weird that testing your commands in a browser worked without a user and password with that unchecked.

        Comment


          Originally posted by integlikewhoa View Post
          That's weird that testing your commands in a browser worked without a user and password with that unchecked.
          I use Remote Desktop to connect to my Win10 box which is headless. You cannot connect from other machines on my LAN via browsers as I've purposely disabled the HS3 web server.
          In my router logs, I kept seeing some chancer trying to accesses my HS3 box from the WLAN so killed port forwarding and UPNP just to be safe.
          They had the IP address and web server port so this scared the cxxp out of me.

          Anyway, when I uncheck that box it immediately stops working.

          Comment


            I've been having issues with my internet recently and loosing voice control of my devices. Whilst researching solutions I came across this thread. Is this still working/a thing? or has it been superseded? (It doesn't seem to have been touched since 2017)

            Comment


              HA bridge still is going strong, you could also look into node red as that can do even more like TTS, etc.

              Comment


                I don't know what you mean by working. HA bridge still works. However, I stopped being able to use this for Google Home voice control a couple years ago. Phillips/Google made it so that you had to login to phillips cloud account to link instead of just finding the HA bridge phillips emulator. I now just use the Google Home interface built in to HS. However, that seem to have long streaks of issues. It will work for a while, it won't for a while. Then other times, it will work on-and-off during a day.
                - Tom

                HSPro/Insteon
                Web Site
                YouTube Channel

                Comment


                  Thanks All. I just wasn't sure if it was still being updates since this tread was so old

                  I've installed the bridge and that part seems to be working, but I can't get my echo's to discover any of the devices. No firewall or AV running on the server. All devices plugged into the same gigabit switched (unmanaged). Very odd.

                  Comment


                    Originally posted by MFULLER View Post
                    Thanks All. I just wasn't sure if it was still being updates since this tread was so old

                    I've installed the bridge and that part seems to be working, but I can't get my echo's to discover any of the devices. No firewall or AV running on the server. All devices plugged into the same gigabit switched (unmanaged). Very odd.
                    I still use it for my Echo's

                    https://github.com/bwssytems/ha-bridge/releases

                    And last update was in July. So don't go by this thread update for the HA-Bridge activity.

                    Comment


                      I think I know what my issue is. My internet firewall is a Fortigate. Fortigate's don't support upnp.

                      So, I assume I am buggered?

                      I thought because it works locally, that the router would not be an issue, but guessing it is. Although I'm not sure why upnp externally would effect it. My echo's are on the same internal IP network as my HA server and plugged into the same unmanaged switch.

                      Comment


                        Hmmm, interesting. I turned on upnp trace and I can see this in the logs when I ask Alexa to update.. so it does appear to be talking.

                        Not sure where it's getting the .90 address from. I don't have anything on my network with that IP.

                        Code:
                         
                        11-04-2019 14:45:41.769 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.68:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:42.420 INFO Traceupnp: send upnp discovery template 1 with response address: 172.16.5.10:90 to address: /172.16.5.68:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:43.070 INFO Traceupnp: send upnp discovery template 2 with response address: 172.16.5.10:90 to address: /172.16.5.68:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:43.721 INFO Traceupnp: send upnp discovery template 3 with response address: 172.16.5.10:90 to address: /172.16.5.68:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:43.721 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:44.372 INFO Traceupnp: send upnp discovery template 1 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:44.472 INFO Traceupnp: request of description.xml from: 172.16.5.63:90 filled in with address: 172.16.5.10:90 com.bwssystems.HABridge.upnp.UpnpSettingsResource
                        11-04-2019 14:45:45.022 INFO Traceupnp: send upnp discovery template 2 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:45.672 INFO Traceupnp: send upnp discovery template 3 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:45.672 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:46.324 INFO Traceupnp: send upnp discovery template 1 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:46.974 INFO Traceupnp: send upnp discovery template 2 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:47.624 INFO Traceupnp: send upnp discovery template 3 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:47.624 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:48.275 INFO Traceupnp: send upnp discovery template 1 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:48.926 INFO Traceupnp: send upnp discovery template 2 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:49.576 INFO Traceupnp: send upnp discovery template 3 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:49.576 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:50.229 INFO Traceupnp: send upnp discovery template 1 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:50.879 INFO Traceupnp: send upnp discovery template 2 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:51.529 INFO Traceupnp: send upnp discovery template 3 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:51.529 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:52.181 INFO Traceupnp: send upnp discovery template 1 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:52.832 INFO Traceupnp: send upnp discovery template 2 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:53.482 INFO Traceupnp: send upnp discovery template 3 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:53.482 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:54.134 INFO Traceupnp: send upnp discovery template 1 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:54.784 INFO Traceupnp: send upnp discovery template 2 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:55.434 INFO Traceupnp: send upnp discovery template 3 with response address: 172.16.5.10:90 to address: /172.16.5.63:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:55.434 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:56.085 INFO Traceupnp: send upnp discovery template 1 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:56.107 INFO Traceupnp: request of description.xml from: 172.16.5.54:90 filled in with address: 172.16.5.10:90 com.bwssystems.HABridge.upnp.UpnpSettingsResource
                        11-04-2019 14:45:56.736 INFO Traceupnp: send upnp discovery template 2 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:57.386 INFO Traceupnp: send upnp discovery template 3 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:57.386 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:58.038 INFO Traceupnp: send upnp discovery template 1 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:58.688 INFO Traceupnp: send upnp discovery template 2 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:59.338 INFO Traceupnp: send upnp discovery template 3 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:59.338 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:45:59.990 INFO Traceupnp: send upnp discovery template 1 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:00.640 INFO Traceupnp: send upnp discovery template 2 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:01.290 INFO Traceupnp: send upnp discovery template 3 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:01.290 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:01.942 INFO Traceupnp: send upnp discovery template 1 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:02.592 INFO Traceupnp: send upnp discovery template 2 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:03.242 INFO Traceupnp: send upnp discovery template 3 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:03.242 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:03.894 INFO Traceupnp: send upnp discovery template 1 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:04.545 INFO Traceupnp: send upnp discovery template 2 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:05.195 INFO Traceupnp: send upnp discovery template 3 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:05.195 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:05.846 INFO Traceupnp: send upnp discovery template 1 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:06.497 INFO Traceupnp: send upnp discovery template 2 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:07.147 INFO Traceupnp: send upnp discovery template 3 with response address: 172.16.5.10:90 to address: /172.16.5.54:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:14.353 INFO Traceupnp: hue api user create requested for device type: test_ha_bridge#172.16.5.108 and username: 6f936c77d20244e29b0acd7dfdf7b253 com.bwssystems.HABridge.hue.HueMulator
                        11-04-2019 14:46:31.271 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:31.922 INFO Traceupnp: send upnp discovery template 1 with response address: 172.16.5.10:90 to address: /172.16.5.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:32.573 INFO Traceupnp: send upnp discovery template 2 with response address: 172.16.5.10:90 to address: /172.16.5.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:33.223 INFO Traceupnp: send upnp discovery template 3 with response address: 172.16.5.10:90 to address: /172.16.5.70:50000 com.bwssystems.HABridge.upnp.UpnpListener
                        11-04-2019 14:46:33.223 INFO Traceupnp: SSDP M-SEARCH packet from 172.16.5.70:50000 com.bwssystems.HABridge.upnp.UpnpListener

                        Comment


                          I have installed ha-bridge and added a test device that I can turn on and off from the web interface (running on port 85).

                          Any time i work with Alexa it makes me feel stupid. I cannot get it to discover devices on the ha-bridge. Is there a "skill" i need to load? Would anyone happen to have a good procedure for getting this to work? Thanks!

                          Comment


                            grahamk

                            I had huge problems getting Alexa to discover my homeseer devices. With HS3 , and 4 , days I have spend trying to sort it out..... very very frustrating.

                            yesterday I installed HA-bridge ( which I had also running previously for my Vera's), working brilliantly! everything is discovered , why can't Homeseer do this not nativily.

                            Anyway, I initially had the same issue that Alexa did not want to discover the devices which I had setup on HA-bridge, but since it was working on my vera previously I knew it had to be a setting. 2 things which caused issues:
                            - webserver port was in my case 0.0.0.0 that I had to change in the correct one.
                            -I read somewhere HA-bridge only works with port 80. ( I had to change Homeseer to another port)

                            After these 2 changes it is working very well!

                            Cor

                            Comment


                              Thank you Corvl1, thanks to you my HA Bridge is back !
                              I've used it on port 85 for years and a couple of weeks ago the bridge stopped responding and discovering devices. I updated to the latest version 'ha-bridge-5.3.1RC2.jar' as there were a few people on the HA Bridge forums complaining that they had developed the same issue. Once again I tried everything including renaming the discovered device ID's but nothing worked.
                              I then spotted this post, swapped from port 85 (which had always worked previously) to port 80 and all devices came back!

                              Comment


                                Originally posted by Corvl1 View Post
                                grahamk

                                I had huge problems getting Alexa to discover my homeseer devices. With HS3 , and 4 , days I have spend trying to sort it out..... very very frustrating.

                                yesterday I installed HA-bridge ( which I had also running previously for my Vera's), working brilliantly! everything is discovered , why can't Homeseer do this not nativily.

                                Anyway, I initially had the same issue that Alexa did not want to discover the devices which I had setup on HA-bridge, but since it was working on my vera previously I knew it had to be a setting. 2 things which caused issues:
                                - webserver port was in my case 0.0.0.0 that I had to change in the correct one.
                                -I read somewhere HA-bridge only works with port 80. ( I had to change Homeseer to another port)

                                After these 2 changes it is working very well!

                                Cor
                                After migrating from HS3 Linux to HS4 Windows 10, the native Alexa skill can see the Homeseer devices. Can't explain it I'm afraid and could never explain why it didn't work previously <mystery>

                                Comment

                                Working...
                                X