Accessing Wiser

Hi All, I have been trying to access a Wiser Gateway, however every time I get to the log on page, it verifies the connection then gives me the "unable to access Wiser" message. I have tried resetting the unit by isolating power, holding the reset button, reconnecting power & holding the button for 10 secs, all to no avail. I had previously connected to this unit with no issues!!
Do you have any ideas what I'm doing wrong.

 

Hi Ray,

The message suggests that the Wiser user interface loaded from the webpage, eg: http://192.168.2.1, is not able to access the Wiser service on the unit. This typically happens when there has been an IP address change. Resetting the unit will only reset its IP address to 192.168.2.1. The other commonly seen problem is that if one upgraded the firmware on the Wiser, one must also update the PICED project on the unit so that it is in-sync.

You'll also want to make sure all the IP address settings are consistent. That is, the IP for the Wiser, the IP for the CNI, and the IP addresses specified in the PICED project are all in sync.

Hope that helps.

 

Wiser

Thanks kjayakumar.
I eventually discovered that to fully reset the unit, I needed to disconnect C-Bus power from it as well. As soon as I did that I could then access the unit using the standard IP address. This is my 1st Wiser & I need to get more up to speed on IP as well, It's going to be a steep learning curve!!

 

Option B configuration ....

Option B config:

The installation instructions for Wiser are a little vague - particularly if you are using the 'Option B' network model which I'm guessing a lot of people are, so I thought I'd just mention a couple of points here.

The Wiser is preconfigured to startup at address 192.168.2.1 and the CNI is preconfigured for 192.168.2.2. If this doesn't match your existing network subnet, as it likely wont, then you wont be able to talk to the Wiser web page frontend from your Browser. In my case my network was 192.168.1.x so I had this issue. In option B the WAN port is not used, only connect to the LAN network ports. . If your PC is setup to use DHCP then by connecting directly to the Wiser using one of the LAN ports or the Wifi then your PC will be setup correctly using DHCP (assuming the Wiser is now the only accessible DHCP server).

If however you use static IP's then you must temporarily reconfigure your PC to operate on the same subnet as the Wiser i.e. 192.168.2.x where x is an unused address. The subnet mask should be 255.255.255.0 and you will need to alter the gateway address too to say 192.168.2.1. Now you should be able to access the Wiser and router config pages. (remember the existing PC's settings as you will be changing them back later).

Important...See [edit] at end of this post.

There are two addresses in the Wiser you need to change - the Wiser (router) itself and the CNI. You change the router address using the setup tab (Basic Setup) of the web interface - Network Setup > Router IP > Local IP address and subnet mask. Change it to an address/subnet that is suitable for your main network. The internet connection type at the top should be left at automatic (this is for WAN - it is not used in an option B model). Follow the supplied instructions for any other config options - inparticular enabling or disabling the DHCP server at the bottom of this page. You must not have two DHCP servers on your network.

Once you reboot the Wiser you will lose web access to it and you now have to revert the changes you made to your PC's IP address back to as they were before and then you will be able to access the Wiser again using your original network configuration. You will it seems now get the 'authentication / unable to access Wiser' message mentioned above. You will still be able to access the router pages directly however (using the recent page history dropdown)

You need now to change the CNI address, this is not configurable from the Wiser web interface and instead you should use the C-Bus IP utility to do this. This is not mentioned in the install documentation at all ! Again set the address to an unused one on your network , having it one number higher than the Wiser is tidy. The utility is quite clever as it will operate across subnets to change addresses.

The project loaded into the Wiser is configured in PICED to know at which address the associated CNI is located. From the Wiser tab of the router configuration under CNI information you can see this current setting and at this stage it will show the old 192.168.2.2 address. So you will now need to create a new Wiser project using PICED and set the CNI address within that project to match the new CNI address you setup using the C-Bus IP utility.. You should also setup the DNS IP addresses and the gateway address appropriate for your network within PICED. Once you have done this and loaded it into the Wiser then all will be well and your Wiser will be fully functional on your existing network, it will also time synch it seems.

Just one additional clarification - the Wiser is accessible and loads its projects from PICED directly using its own address (the same address as the router) - it does not use the CNI for this purpose. It only uses the CNI for onward connectivity to your C-Bus network. Also you can 'borrow' the CNI for use by other applications eg C-Bus Toolkit which you configure to access the CNI via the Wiser's IP address (not the CNI address). Whilst borrowed in this way the CNI will not be available to Wiser and so your Wiser web interface will not update C-Bus.

K

CIS guys .. if I've got anything wrong or it's misleading let me know and I'll edit it.

[edit] Based on later posts in this thread (particularly if your Wiser is firmware v 1.4) I would strongly recommend whilst you have access to the factory default Wiser project using the 192.168.2.1 address you click on the toolbox/config icon and in the 'remote access' section you will see an option that is titled 'Project Update Enabled' - make sure this option is enabled, (in my case I enabled all options on this page). The 'Project Remote Update' option allows for the Wiser project to be updated by PICED from a different subnet to the one that the Wiser is located on. As you will be changing the Wiser subnet later in this post , and as the subnet info is retained in the loaded project this is essential or you will not be able to download a new project from PICED to the Wiser.

 

Kevin,

At first glance, what you've written looks pretty accurate. It is a reminder to Clipsal that this area of TCP/IP configuration could use a pretty good shakeup and that it is as much of a priority as adding new features and touchpoints.

 

I have the same problem. i have tried resetting with c-bus disconnected, but i can only find the wiser on 192.168.1.100. it just says "unable to access wiser"
I have seen the mode switch on the back and the WPS on the top, what are both switches for?

Thanks
Ben

 

The mode switch and the WPS button are disabled and aren't currently recommended for use. The "unable to access Wiser" indicates that there is a configuration issue. You'll need to check that the Wiser's IP, CNI's IP, and other relevant parameters match the values that were set in the project created in PICED.

 

I can't get access via PICED or web browser. wiser looks to be on 192.168.1.100 and CNI is 192.168.2.2.
I have tired a full reset but wiser is still on 192.168.1.100. I have even tried connecting to wiser with out the cni pluged in.
192.168.1.100 connects to wiser but then says "unable to connect to wiser"

I don't understand why it will not reset.

 

I don't understand what you want to do . Do you want to change your Wiser's IP or your CNI's IP? I assume it is the CNI's IP. From your post, the only data is that:
- your CNI is on 192.168.2.2
- your Wiser is on 192.168.1.100

My assumptions:
- I presume the PC you are running PICED on is on an .1.x subnet since you mentioned you are able to connect to the Wiser. So, say your PC is on 192.168.1.10.
- You want to use your Wiser as a LAN device and not as a router.

Okay, now all we need to do is:
a) change CNI IP to 192.168.1.2. Use the C-Bus IP setup utility to do this. Did you have any problems with this?
b) upload PICED project with all the right settings in Project Details. Make sure it says Wiser IP is 192.168.1.100 and that your CNI is 192.168.1.2. Check the tab about connections and setup the gateway address and DNS info accordingly.

and that should be it.

Hope that helps.

 

Also please consider reading the following post. http://www.cbusforums.com/forums/showpost.php?p=26187&postcount=5 . If you still have trouble with the configuration, please be more detailed about your setup, firmware version, PICED version and such. One last hint, you can get to the Wiser's web configuration page by doing http://192.168.1.100/index_i.htm .

 

Hi Ben,

From what you've posted you still need to set the CNI IP address using the C-Bus IP Utility (this is the bit not mentioned anywhere in the docs) and you need to create and download a new project from PICED with the correct IP settings to get it all in synch. Have a good read through my previous post earlier in this topic.

If you're still having difficulty - ring me and arrange to drop around with the Wiser and I'll get you going...


Kevin

 

Thanks for your step by step Kevin - i thought i was going mad missing something obvious in the setup guide !!

One thing i did notice is that i couldnt change the CNI address until i had removed the busbar connection on the back and connected power and lan straight into the CNI, even though Wiser was set at 192.168.1.x and CNI was 192.168.2.x the Wiser was somehow denying access ??

The CNI showed up fine in the IP Utility and i could change the address accordingly - but until after reboot - the IP Utility couldnt find it, and then address hadnt changed.

This might help someone else if they get stuck too


Dean.

 

I'm stuck too...

Chaps, I *do* know my way around IP, having been in the IT industry for over 20 years... but I'm still not able to get all this readdressing completed following the instructions in the previous posts...

My network address is 192.168.145.0/255.255.255.0

I have successfully changed the ROUTER address from its default 192.168.2.1 to an address on my subnet: 192.168.145.245. I can connect my browser to this address & access the router setup pages etc... so far so good...

I have then run the IP Utility, which has found the CNI on my network and shows it having the following properties:
IP Address: 192.168.2.2
Netmask: 255.255.255.0
Gateway: 192.168.2.1
Which are all as expected.

Where it falls down is when I try to edit those settings to change them to:
IP Address: 192.168.145.246
Netmask: 255.255.255.0
Gateway: 192.168.145.245

Which I believe should be the correct settings, - the gateway I've specified is the IP that the wiser router is now on, same netmask, and the CNI IP is 1 higher than the router IP to keep it tidy..

When I try to apply those changes, the IP utility tells me:
"The Network Mask you have given will not allow the device to communicate with this PC" -- WTF? ? ? ? - the PC I'm running this from is on 192.468.145.20/255.255.255.0 - So every device *IS* on the same subnet... Why is the IP utility telling me (wrongly) that it isn't?...

I have a choice of ignore or cancel, so I select ignore to try to make it change anyway, it then prompts me to set a unit password, which I enter, and it then comes back with the error: "Device did not respond when saving"
and no matter how many times I retry, it will not accept those settings...

This is PANTS!!

Note that all the above was with the CNI connected to wiser & busbar in place... I then went & seperated them, connecting ONLY the CNI to the network & repeating the IP utility process, and this time the utility has performed the readdressing that I wanted, and after rebooting the CNI it rescans in the IP utility just fine...

Until... I reconnect the units together & reattach the busbar... Now, NEITHER of the units are visible on the LAN!!! ***AAARRRGGGHHH!!!!****

I can't ping either the 192.168.145.245 OR 192.168.145.246 addresses, the cbus IP utility scans & apparently sees the CNI but shows its status as offline, and I Can' access the router admin pages from my browser.

I am 10 minutes away from sending this back and keeping my old PAC & PCI units... - at this price, I shouldn't have to deal with this CR**P!

Can anyone from Clipsal tell me what is wrong with this???

TIA

Paul G.

 

Sort of progress, but still not right..

I've seperated the router & CNI again, & connected up only the CNI...

It is FULLY WORKING as a CNI on the address I assigned to it earler with the IP utility, - i.e. 192.168.145.246 I have connected to it, and successfully opened & scanned my network in toolkit, so the CNI part is definately operating on the IP I asigned it...

As soon as I hook the router & CNI togethter though, everything appears to stop working, neither unit is pingable, or acesssable...

All in all, so far I'm distinctly underwhelmed by this whole Wiser thing...

 

Tried a few other things, STILL CANNOT CONNECT

If I didn't already have a "number 1 all over" I'd have torn out most of my hair by now... - I think I figured out that previously, when I hooked all the units back together, I think I must have plugged the Ethernet cable into the wrong port on the Wiser, - I suspect I plugged into the busbar port, which I believe is passed through only to the WAN port on the router yes? - thus neither units could be seen on the LAN... - that makes sense... I've just reassembled the 3 bits, and made sure to connect the network cable into one of the 3 LAN ports that are left accessable after the busbar is plugged in, and having done so, I can PING both units on their respective addresses, and I can connect toolkit to the unit to view/configure the CBUS network. - That at least is a start...

However, I *STILL* cannot get a browser to access the wiser UI - just constantly get the "unable to connect to wiser" message. Also, I can't get PICED to transfer a test project to it. - I've run PICED 4.7.2.0 and created a new project based on a wiser template. I've created a couple of locations & function groups, & added a couple of CBUS groups in, - just for testing purposes.

In PICED if I then select "connect to unit" the wizard start up, I Select local connection... under search method iis defaults ti Fixed IP, with the factory default IP address (192.168.2.1) pre-entered. If I change this to my actual wiser IP (192.168.145.245) as soo as I hit OK it immediate just says "Please check the IP address" and absolutely will not deviate from this behaviour. So, I change to "Auto search" - it appears to find my wiser on 192.168.145.245, since it displays one in the Wiser Transfer utility window: "[email protected]" (shown with a red dot on the icon if that means anything)...
But if I click on that item, it immediately says "unable to connect to wiser at address 192.168.145.245", and if I click on it again, it usually comes back with: "Socket Error # 10054 Connection reset by peer"

I'm just about at my wits end with this, PLEASE can anybody suggest a resolution to this hell, because right now, I've spent nearly 24 hours fannying around with this trying to get it to do the most basic function that it is supposed to fullfill, and frankly, I'm beginning to seriously regret buying it...

TIA

Paul G.

 

Harumph! - I think you're being overly generous there Kevin, - I'd describe the connection & IP configuration documentation as absolute sh**te... Further, I'd suggest that the *majority* of installations will use the option B model... - certainly my first reaction was along the lines of: "re-address my entire network, and junk my existing (enterprise grade) router just to bring another network service online, - not BL**DY likely!"

So, I have readressed the wiser router, using it's web interface, - that has worked just fine, and I'm now accessing it on the address I want...

I've also readressed the CNI using the IP utility, and that's worked too (eventually, - but it absolutely wouldn't do it if it was connected to the wiser at the time, so I had to split them to do it). I've been using toolkit all day to connect to the cbus network... - Note that I have to use the CNI's IP address in toolkit, - toolkit will NOT connect through the wisers's IP for me...

Copy that. Yup, at this point the wiser indeed shows the CNI IP address as the old ...2.2 factory default... I've created a new project in PICED, and I've set the details as follows: select menu - Project > Project Details... switch to the Properties tab, and set the Wiser & CNI address in each of the properties boxes. Note that the "open" button for each of them does indeed open the web interface for each device - (although the wiser webpage just says "unable to connect to wiser" after prompting for login...) Then switch to the connection tab, and set the following:
under "permit access to wiser home control" I've enabled (ticked) all 3 options, and in the remote wiser properties I've entered the LAN IP ipaddress of the wiser unit (I have no desire at this point to access from outside the LAN). I've enabled (ticked) the "Allow Access from Wiser LAN ports" option and filled in the LAN properties with the gateway address for my network (i.e. my existing WAN router), and 2 available DNS services.

I then select form the menu: Transfer > Transfer project to unit... and then in the transfer dialog select transfer current project. The Wiser Connection wizar dthen appears, and from this point it all goes downhill... thus far, NO combination of connection method or search type will successfully connect to the unit. - and I believe after all this time I've tried every possibel combination... Nothing works, it just keeps failing to connect & comes back with the either "please check address" or "unable to connect to wiser at address..."

Not so for me... Toolkit WILL connect if I set the network to the IP of the CNI unit, it will NOT connect if I set it to the IP of the Wiser unit... - since the Wiser still seems to insist that the CNI is still on the old factory default ....2.2 address, that's not altogether surprising...

So, it would seem:

I *have* readdressed my wiser router to 192.168.145.245/24
I *have* readressed the CNI to 192.168.145.246/24
I *have* created a PICED project that *should* update the Wiser's knowledge of the CNI's new address, but I seem to be unable to upload this...

Can anyone see what I might have overlooked, missed out, not understood correctly? - because I've just about had it with this...

FYI, here's what comes up when I click the "open" button to open the CNI in a browser:

Part name: WISERCNI
C-Bus status: Ready for client connection
Network voltage: 31.2V, measured 5 seconds ago
IP Address: 192.168.145.246
Netmask: 255.255.255.0
Gateway: 192.168.145.245
TCP Port: 10001
Unit Address: 255
MAC Address: 00:17D:01:02:56
Serial Number: 001005570780
C-Bus Firmware: 5.4.00
Ethernet Firmware: 1.0.0
Hardware variant: Inline

 

Hi there,

It looks like you're 99% of the way there. The remaining task is, as you've pointed out, to get the PICED project on to the Wiser.

Now, your Wiser is on 192.168.145.245 and I presume your PC on which you're running PICED is also on that network. Say 192.168.145.20. Now, check that you can access the Wiser's status page in a web browser. This will be http://192.168.145.245/clipsal/main.htm and then check on what the Wiser thinks its current state is. Mine says:

Firmware Version Kona_1.12.0
Project Size 319207 / 524272 : 60 percent full
Project Information OFFICE
CNI Information 192.168.100.124:10001
User Interface Version CBC - 3.7.0,UI - 3.9.0
Time Source NTP Master at 12/02/2010 17:48:24
Miscellaneous HG-LAN Enabled, Schedules Enabled

Now, start PICED , open your project and then check the project details, especially the Wiser's LAN settings. If you're using your Wiser as a LAN device, then make sure you've filled in the IP address of the actual gateway and the DNS settings in the connection details tab. Okay, now transfer the project to Wiser. It should go cleanly and automatically reboot. Once that happens, all should be well. If Wiser doesn't let you transfer your project, then that indicates that some other configuration is bjorked. In that case, please post the status tab's text like above and lets have a go at getting it solved.

Sorry that all of the configuration steps are so complex. It is an area that could be vastly improved.

 

I shared your frustrations Paul, and I know many others have too

I've sent you an offlist email that maybe might help - if it does do let us know what the issue was....

As mentioned above it's just that final PICED download that we need to get completed...

K

 

Thanks for the help guys. - It's *SOOO* frustrating to be so near, yet so far...

FYI, I just power cycled the whole kit & that hasn't helped... here's some screengrabs that show the info you've suggested I look at, - I can't see anything that is obviously wrong... (good guess on my PC IP BTW! - exactly the right address)... My actual router is 192.168.145.254 - so that's the gateway I have specified in the project settings. I've also tried setting that as the gateway set in the CNI by the IP utility, (so I've tried both the Wiser IP and my LAN router as the CNI gateway) - and that's made no difference.
I an ping both the wiser's and the CNI's IP's and I can get a browser interface to view them both...

TIA

Paul G.