Well, sort of...
I still think I'm on the right track here... but it's not as simple as I thought.
I am getting the wizard started, but it only starts the wiz on the core, not all md's
Also, trying to 'set' devicedata as the wiki suggests doesn't seem to work...
I'm banging my head against it.. been hammering all day...
Will keep you posted...
Regards,
Dan
Dan,
The lighting Wizard always runs on the Core... or probably more precisely it runs on the machine that has the z-wave/insteaon interface attached. At the moment as far as I know the lighting Wizard is very tightly coupled to Z-wave and also specifically 'lighting' eg if you have for example a z-wave PIR it does not configure that. I was working with Eugen at Pluto (the original Dev who was responsible for the Z-wave) to make the Lighting Wizard become the 'Z-wave Wizard' so that it would be able to configure/manage all types of Z-wave devices. Now a logical extrapolation of that would be to say that the 'Lighting Wizard' should really become the 'Home Control Wizard' (Hmmm... maybe we need a nicer name for it ;-) ). The HC Wizard would be triggered once a control interface was detected eg z-wave/insteon etc etc etc and then would proceed to assist the user in configuring all of the supported devices for that interface.. The Lighting Wizard actually works very well as a model for how to do setup/congig in the real world... I have done literally 100's of z-wave install/setups with it now and with it I can do a setup for say 10 devices in about 10 mins. Previously without the Wizard it took me about 90 mins for the same number of devices! (and making adjustments/changes later was a total pain in the !%se)
