The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: Re: cbus Wiser config agony



Paul

I feel your pain !!

I'm at exactly the same point as you - finally managed to change the IP
address via the IP config program etc. Clipsals argument that IP addressing
is too varied for them to give you correct info is b*ll*cks.

I'm assuming you as myself can open PICED create a project with correct
details but when you ask it to connect to device it says check IP address ?
And when I select auto IP it finds HOME@xxxxxxxxxxxxx but then still will
not connect.

I pride myself on being pretty IT literate but this things is just
cobblers.
As you say, perhaps there's yet another undocumented setting that needs
changing.

I've been a long time Cbus fan/installer and after many years of good
products and poor UK support (except when Phil was there) they still manage
to frustrate the hell out of me.

Hopefully someone will answer the post on cbusforums - or hopefully Kevin
will be along soon to offer advice as I believe he has his up and running.

Oh and it damn embarrasing when SWMBO keeps asking why the outside lights
don't work on a timer anymore, since removal of the old PAC unit...


Dean.

-----Original Message-----
From: ukha_d@xxxxxxx [mailto:ukha_d@xxxxxxx] On Behalf Of
Paul Gordon
Sent: 14 February 2010 22:50
To: ukha_d@xxxxxxx
Subject: RE: [ukha_d] Re: cbus Wiser config agony

Can I ask you for a little help with setup please? - cos I'm about to throw
myself under a bus in frustration... - it's all down to the *tortuous* IP
re-addressing palaver...

In essence, as I want to use "option B" connection model, I've
readdressed
my units as follows:

Readdressed Wiser router to 192.168.145.245/24 (via wiser's web admin UI)
Readdressed the CNI unit to 192.168.145.246/24 (vie CBUS IP utility)

I've confirmed both of these, and I can connect to both units on these
addresses (I've used toolkit for several hours connected to the CNI IP)

As is expected, according to the Wiser's UI, it still believes the CNI is
on
the original default addres of 2.2, so I understand I need to upload a
PICED
project to update that... - I Seem utterly unable to get this last part to
work... - PICED just constantly fails/refuses to connect... so I can't
upload the project to update it's knowledge onf the CNI, so I cannot access
the wiser UI, not can I connect to the CNI through wiser, as I believe I'm
supposed to be able to...

I've been at this for almost the whole of this weekend, - SWMBO isn't best
pleased - says I'm neglecting her on valentine's day... :-( - I'm fed up,
and I just want it to work... I *believe* I've done everything specified in
the instructions, but either I've got a duffer, (which I doubt), or there's
still some other (presumably un or poorly documented) config setting
somewhere that I haven't set...

TIA for any pointers...

Paul G.





-----Original Message-----
From: ukha_d@xxxxxxx [mailto:ukha_d@xxxxxxx] On Behalf Of
wiserhomecontrol
Sent: 20 January 2010 08:54
To: ukha_d@xxxxxxx
Subject: [ukha_d] Re: cbus Wiser appears to be in UK stockist

Hi Kevin, and UKHA members,

This is my first post to the list. I work on various bits of the Wiser
software, but my comments here are completely my own and aren't on behalf
of
the company so don't assume anything I say is official.

--- In ukha_d@xxxxxxx, Kevin Hawkins <yahoogroupskh@...> wrote:
>
> I'm guessing that means multiple application users rather than the CNI

Yes, you are correct. The current Wiser supports up to 6 simultaneously
connected devices. These devices each run an independent Wiser user
interface application. That could mean 6 iPhones or any mix of constantly
connected or sporadically connected Media Centers, iPhones, PCs/laptops,
and
a partridge and a pear tree. You get the idea. Currently, the list of
devices with released applications is:
- iPhone/iTouch (released yesterday)
- Microsoft Media Centre (Vista only at the moment)
- any device capable of running Adobe Flash 9 and above (this means almost
any PC or Intel/AMD/x86 CPU based platform). Linux, Windows, MacOS, etc
through browser plugins or native apps. This category tends to be the big
one as it includes web tablets, in-wall stuff, deskmount stuff and others.
- devices with FlashLite 3.0 with XML support. This covers devices like
Nokia Symbian phones. N95 works. I think some of the others which have
touchscreens aren't quite fully supported yet.
- other devices with Adobe Flash capabilities. Turns out Playstation 3
works
fine as well as a user interface for Wiser.

> sure the CNI will be single owner only.    We'll see once someone has
one.

Indeed. When you want to configure or commission something, you connect
toolkit to the Wiser's IP address (or external DNS name/etc if you've
enabled remote programming and dyndns/etc) and it will pass that
communication through to its CNI. In that mode, that is, the mode of
toolkit
programming, naturally, you won't be able to use any of the Wiser's user
interfaces. Once you disconnect toolkit, the user interfaces reconnect and
are able to share access to the Wiser as before.

By the way, there's a youtube video of the Wiser iphone app here,
http://www.youtube.com/watch?v=aHsjTdTPVnU
. Some Russian guys have also
posted this video of an interesting setup,
http://rutube.ru/tracks/2288889.html
(I don't know why but I had to click
past the initial clip of something else before I could see the actual
video)
showing Wiser with media centre, various screens, logic integration, email
and such things. Good luck and please do provide feedback. Post videos of
your setups if you can. We do enjoy watching.




------------------------------------



UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.