I seem to struggle every time I try do something new with my Vera… hopefully it will get easier over time. I just installed a Hue starter kit (bridge + 2 lights) and want to connect the bridge to the Vera.
I have followed what seemed like a pretty standard process: devices/add device/dimmers and lights/Philips Hue → pairing. I have checked the ‘accept…’ tick box, pressed the button on the bridge, and clicked ‘install’. That seems to go ok. I then get the ‘connectivity’ screen (screenshot 9, with ‘use this one’ unchecked). I lose it here.
I’ve tried leaving ‘use this one’ unchecked and clicking ‘pair with bridge’ (pressing the button on the bridge first).
I’ve tried checking ‘use this one’ and clicking ‘pair with bridge’.
I’ve tried entering the ip address and clicking on ‘save ip address’.
I get a pop up that says ‘success’ at the top and ‘Bridge pairing in process, please wait…’ in the body and then it goes back to the same screen, so I click finish and get taken back to the devices page where Philips Hue is switched to off and there is a message ‘Can’t detect device’ (screenshot 12).
If I try to toggle the switch to on I get a spinning circle and it says ‘sending command’. The message goes but it is still switched to off. toggling again does nothing. If I click through in to the app it says ‘can’t detect device’.
I’ve also tried pressing the Hue button after ‘pair with bridge’, and have uninstalled and reinstalled the app several times trying different methods.
I tried installing AltHue (with the Vera Hue app uninstalled) and had pretty much the same problem.
I tried AltHue as well and gave up after the first couple of attempts were the same. The problem is that I can’t get the Vera unit to connect/detect the Bridge so I’m doubtful it would make a difference. If I get time I’ll try again with ALTHue but hopefully someone can identify why it won’t connect.
I’ve just tried again with ALTHue. No joy. I get to the same point. With ALTHue the only place I can enter an ip address is in the params tab of the advance section in the app, which doesn’t do anything, and no pairing button anywhere. I don’t get a screen that looks anything like section 4 of chapitre 2 of the guide - the standard app is closer to that.
I just installed the ALTHue plugin on a Veras Edge with the latest firmware. Everything worked perfectly, with no issues at all.
What you MUST remember is: After you install a plugin (ANY plugin), allow the Luup Engine to finish reloading, and REFRESH YOUR BROWSER (Use CTRL-F5).
The browser UI does NOT automatically refresh after plugin installation, and missing UI components (eg: the "pair"button) is a sure sign that, although the plugin has installed, the UI has not loaded the installed files properly.
so:
Install plugin.
Wait for Luup reload to finish.
Refresh your Browser (CTRL-F5).
Go to the settings page. Enter the IP address (or press “Discovery Meethue.com” button, and select from the detected address(es)). Click on “save”.
Allow Luup engine to reload.
Go to the settings page. Press the button on the Hue Bridge. Click on the “pair” button. Once the status changes to “paired”, click on the “save” button again.
[quote=“cybrmage, post:5, topic:199451”]I just installed the ALTHue plugin on a Veras Edge with the latest firmware. Everything worked perfectly, with no issues at all.
What you MUST remember is: After you install a plugin (ANY plugin), allow the Luup Engine to finish reloading, and REFRESH YOUR BROWSER (Use CTRL-F5).
The browser UI does NOT automatically refresh after plugin installation, and missing UI components (eg: the "pair"button) is a sure sign that, although the plugin has installed, the UI has not loaded the installed files properly.[/quote]
This might be helpful… I now have a screen like the one in the instructions (almost - I have save instead of submit). How long should the reload take? I get a pop up saying it’s reloading, but nothing to indicate that it’s happened, and just an unsuccessful message pop up when I click pair. I also haven’t refreshed the browser.
So is it:
reload
refresh
pair?
And hopefully the refresh will fix the problem I’m having with pairing.
The reload take as long as it takes… It depends entirely on the number of devices and plugins that you have installed.
Recent firmware versions have disabled the “status bar” the used to be displayed at the top of the page when the luup engine was reloading or plugins needed to display status information (enable it at “Users & Account Info”/“Notification settings”/“Notifications Header (Additional diagnostic and operational messages displayed)”)… So unless you explicitly enable the status bar, you just have to wait… Unless there is a significant error that causes a Luup reload loop, the reload should be done in under 3 minutes.
The unsuccessful message happens if you click the “pair” button BEFORE you press the control button on the Hue Bridge. You MUST press the button on the Hue Bridge BEFORE you click on the “pair” button.
It’s possible I hadn’t waited long enough for the reload. I only have one other plug in (apart from the 2 defaults) for Netatmo. I’ve definitely been hitting the pair button first. Between enabling the status bar and refreshing the browser hopefully I’ll be able to get it working. I won’t have a chance until some time tomorrow, but I’ll post an update after.
In the last post I meant I had been pressing the bridge pair button first, not ‘pair’ in vera.
I had a quick go this morning but no dice. I will try uninstalling and reinstalling fresh later. I logged a call with support and all they have done is tell me to follow the instructions I’ve been following.
Oh, I still didn’t get an indicator on the status of the reload with the notification header setting set to on, but I did wait a full 3 minutes.
I’ll post again later with how I go and whether there is any change with a fresh reinstall.
This is absurd… I now have a message saying can’t reach Hue Bridge because of missing ip address in attributes, on the same screen showing the ip address. The ip address was also present in the parameters tab.
I paired 2 new bulbs to the bridge earlier.
Any ideas?
Edit: I have done the save for the ip address before trying to pair and getting this message.
That slash should probably be a 1.9 based on the error message.[quote=“tomtcom”]Get rid of the / in front of the 9. Alsoake sure no spaces before or after the IP.
Interesting… the bridge IP is from the meethue site.
I just checked all of my other devices through the google wifi app and they are on .86.xx, except one of the TV’s. That TV is connected to one of the google pucks and works fine. It has a .1.xx similar to the bridge. The Vera unit itself doesn’t show up on the list of google wifi devices. The only thing I have it connected to so far is Netatmo, and I can’t see the IP for that.
I have a modem/router with a switch plugged in to it that everything else runs off (google wifi, NAS, Hue, Vera). When I set up my Vera I had heaps of problems, and tried it in both the switch and the modem. Is it possible it picked up an IP address while plugged in to the modem (that IP is .1.xx) and that’s the issue? I don’t have any static IPs.
I am super reluctant to set up from scratch again. I power cycled all of the units simultaneously a couple of days ago due to connectivity issues.
That is because the Vera is NOT on the same network as the google connected devices…
If I understand correctly… The Vera is connected to your Mouter (Modem/Router - Your primary internet device)… Your Google wifi puck(s) are also connected to your Mouter… Everything else is connected to your Google puck(s)… Because the Google puck(s) act as their own router and firewall, anything connected to them is not accessible to the Vera, as any traffic to these devices is blocked by the Google puck(s).
You need to either move the Vera to the same network as the other devices, or move the devices you want to control with the Vera onto the same network as the Vera.
You don’t need the local IP for the netatmo device because the netatmo plugin(s) use a cloud connection… They talk directly to the Netatmo cloud servers, and the netatmo server talk to your netatmo station.
You need to have some static IP addresses… Well, you need to at least have IP reservations.
Most Vera plugins that talk to local devices do not deal well with devices that change IP addresses… You need to fix their address to ensure there are no problems down the road.
Set an IP reservation for your IP connected home automation devices in the router that they are directly attached to (ignoring any switches - switches are transparent)… As you describe your current setup, the Vera’s IP address would be reserved in your Mouter, while the Hue Bridge would be reserved in the Google Wifi.
[quote=“cybrmage, post:16, topic:199451”]If I understand correctly… The Vera is connected to your Mouter (Modem/Router - Your primary internet device)… Your Google wifi puck(s) are also connected to your Mouter… Everything else is connected to your Google puck(s)… Because the Google puck(s) act as their own router and firewall, anything connected to them is not accessible to the Vera, as any traffic to these devices is blocked by the Google puck(s).
You need to either move the Vera to the same network as the other devices, or move the devices you want to control with the Vera onto the same network as the Vera.[/quote]
The Vera is plugged in to the switch, which is plugged in to google (which is plugged in to the mouter). I thought that would put everything on the same network. So my question now is, how do I get the Vera on to the same network as the rest?
Wow - I feel really stupid now… I checked all of the cables again and the Vera wasn’t connected to the switch after all. Moved it over, power cycled, and all is well.
Thank you so much to everyone who pitched in to help.
Best Home Automation shopping experience. Shop at Ezlo!