Setting up #3
Comments
|
Ok I was able to start the services next is the device editor, what ip do I put there when I use the 115 like in the set up it shows my example devices please help |
|
The reason you don’t see a “.config” after the file name is that in Windows Explorer you have the “Hide extensions for known file types” turned on. You can see that because the NanoHuesBridgeService doesn’t have a “.exe” after it, but the file type is listed as Application. [cid:[email protected]] You are going to have to rename the file otherwise its real name will be NanoVeraHuesBridgeService.exe.config.config and the service application wont be able to find its configuration. From: eli167 [mailto:[email protected]] Ok been trying for a few days now, this is my problem first I downloaded ll your files ran the setup.exe the file name NanoVeraHuesBridgeService.exe did not have a config after it then I added it to it this is the set up I try to start the service and get this error do not know where the 10.10.1.26 came from, any help will be great — |
|
You need to know the IP of your machine. From: eli167 [mailto:[email protected]] Ok I was able to start the services next is the device editor, what ip do I put there when I use the 115 like in the set up it shows my example devices please help — |
|
do not think this is right can not get any information from Vera log |
|
Need to see a full log and you’ll want to turn up the log level. To turn up the log level: Capture a clean log: Be helpful to provide the following info too: From: eli167 [mailto:[email protected]] do not think this is right can not get any information from Vera log — |
|
log and reply sent waiting for your reply |
|
Dont see a log file. Was supposed to be attached? From: eli167 [mailto:[email protected]] log and reply sent waiting for your reply — |
|
Was emailed yesterday I can forwarded if you need
|
|
see below |
|
Got this log. However the log file wasn’t the whole log file (if it were, the log file would indicate that the system was starting up, but the first message in the file is a uPNP message). Based on what’s there the app seems to be working. It’s seeing uPNP messages. But the it’s not seeing an Echo discovery packet (it will contain the phrase “M-SEARCH * HTTP/1.1” ). Or, at least, it didn’t in the portion of the log I received. You did tell Echo to “discover new devices” right? What was IP address of echo? From: eli167 [mailto:[email protected]] see below log.txthttps://github.com/nanowebcoder/NanoVeraHuesBridge/files/290004/log.txt — |
|
I did tell it to discover but it didn't find anything do you know how to On Mon, May 30, 2016 at 5:31 PM, nanowebcoder [email protected]
|
|
Easiest way is to look in your DHCP server. If you cant identify it in your devices, look in the Alexa app under settings and you can lookup the MAC address of the Echo. Then look in your DHCP for a matching MAC address. With wireshark, you’d have to be looking for the right packets and then echo would have to be transmitting… bit more challenging. From: eli167 [mailto:[email protected]] I did tell it to discover but it didn't find anything do you know how to On Mon, May 30, 2016 at 5:31 PM, nanowebcoder <[email protected]mailto:[email protected]>
— |
|
ok more testing by me, I know the ip address of the echo now, 192.168.1.19 the echo from my Phips bridge. yet each time I do to discover, I don't see any log entries. just so you know my Echo is connected to a secondary AP my machine that has your software is plugged in to my switch, with the hue you need to press the botton in order to pair it, do we need to do anything like that |
|
Is the secondary AP acting as a router? If so it won't pass the UDP packets If you run wire shark (on the same network segment as the machine) do you see traffic from echo? If you don't, there's no way the bridge software will see it either No Need to press a button. The bridge software is always listening unlike the hues bridge which will only listen when the button has been pressed. On Jun 2, 2016, at 8:49 AM, eli167 <[email protected]mailto:[email protected]> wrote: ok more testing by me, I know the ip address of the echo now, 192.168.1.19 the echo from my Phips bridge. yet each time I do to discover, I don't see any log entries. just so you know my Echo is connected to a secondary AP my machine that has your software is plugged in to my switch, with the hue you need to press the botton in order to pair it, do we need to do anything like that You are receiving this because you commented. |
|
The access point is not a router it's just a Cisco ap so I need to see the
|
|
Most APs can be configured to function as routers—Cisco too. If the AP is configured to work as gateway (as opposed to a bridge), then it wont pass UDP packets beyond its gateway. From: eli167 [mailto:[email protected]] The access point is not a router it's just a Cisco ap so I need to see the
— |
|
its a cisco 1130AG On Thu, Jun 2, 2016 at 9:42 AM nanowebcoder [email protected]
|
|
please advise if there are any other tests I can do, I made sure of the IP address |
|
You could try plugging the Echo into the same switch as the pc. You could also run wireshark on the pc and see if you can see the uPNP broadcast messages coming from the Echo. I wouldn’t normally suggest someone to run wireshark, but you seem familiar with it and it’s a great diagnostic tool. From: eli167 [mailto:[email protected]] please advise if there are any other tests I can do, I made sure of the IP address — |
Ok been trying for a few days now, this is my problem first I downloaded ll your files ran the setup.exe
the file name NanoVeraHuesBridgeService.exe did not have a config after it then I added it to it
next what IP do I use, I tried a unused one on my network and it didn't work. then I read a reply from you to another user and changed the ip to this local box
this is the set up
I try to start the service and get this error
do not know where the 10.10.1.26 came from, any help will be great
The text was updated successfully, but these errors were encountered: