LinuxMCE Forums
General => Users => Topic started by: hari on April 13, 2012, 12:23:11 am
-
what stick do you use? Does it affect all nodes or just specific ones?
-
:)
Hi.
Firstly: /me Drools at four floors of Zwave........
Secondly: Do you happen to have a thermostat in your installation?
If so, was it added during the intelligent mesh layout, i.e. starting at the core and working out geographically?
If not, when was it added, and how far is it from the core?
I added a knock off version of the Wayne Dalton version, but, I added it at the end of my chain. As I did not want to unlearn and relearn all of my devices. It worked well for some time, however I started getting messages like what you are, and my timed scenarios stopped firing. Like at sunset, turn on perimeter lighting, and such.
What I had to do was in fact delete my zwave devices, reset my Aeon Labs stick, and start from scratch, capturing the thermostat geographically from my core.
If you don't have a thermostat, then disregard this mad raving, and go back to the Firstly point, and ignore me :D
Hope you figure it out.
Best Regards,
Seth
-
I use a MCV Vera as my primary controller. The Vera handles running a mesh network "heal" on a regular basis. I have a second Aeon Labs stick for LinuxMCE, for it to act a a secondary controller.
What is supposed to happen with z-wave is that the primary controller has the devices ping one another so that the mesh network can be hashed out, in terms of what devices talk to which neighbors, for routing commands. If you move, delete, or add devices, the controller is supposed to re-hash the network. The more devices, the better the mesh, the more likely signals will reach their destination, etc.
In the event that you get the kind of mesh network problems indicated above, and cannot successfully initiate a mesh network "heal," you almost have to rebuild the z-wave network by deleting everything and starting over. It sucks, but that's the way it is sometimes. But before you go to that extreme, look in theLinuxMCE web admin panel to see what z-wave admin options are there. If there's a network heal option, try that. I really haven't looked at what z-wave options are in the web panel, since my setup only requires that LinuxMCE can talk to the primary controller through the secondary Aeon Labs stick.
-
no we don't have a hail/heal in LMCE. Domodude, would you mind to test what happens when you do a *soft* reset (search if you don't know how). If that does not help, unplug the stick, shut down the core, plug it back in and then startup again? I suspect that the firmware of the stick crashed. We've seen some occurrences of this.
ps: don't do a regular reset, that will erase all network info. The soft reset is something different. It will just "reboot" the zensys chip
-
@ hari
Is the firmware crash associated with any particular controller stick hardware? If so, what hardware?
-
the vera stick works fine.
-
How did you program the Vera stick (do you have one?)?
I have the Vera acting as the primary controller, and do all inclusions through it's Aeon Labs stick. My LinuxMCE core has a second Aeon Labs stick that acts as secondary controller. The hardware detect wizard brought up the "Sarah" interface automatically. All I had to do was to set the Vera to copy the setup to that secondary controller, much like you would do if you had a z-wave enabled remote controller.
I do not think I can have two SUC/SIS controllers, is that correct?
One must be primary, and all inclusion and exclusion must be done through that one. The other will be a glorified remote control.
And the Vera does not really want to accept the setup from the Tricklestar minimote... I am at a loss here, any hints?
Make your Vera primary, and make the tricklestar the secondary attached to your LinuxMCE core. I have my Vera running as the external network Gateway, and everything internal talks to my LinuxMCE core through a Linksys router that has DHCP turned off (using LinuxMCE as the internal DHCP provider).
Vera always wants to be the primary controller for a z-wave network, by default at least. LinuxMCE will accept a role as a secondary controller without putting up much of a fuss. The reason I work my system out this way is that the Vera supplies a free internet connectivity service. If I wanted to do that through LinuxMCE, I would need to sign up with a static IP address service. That would represent another point of failure for controlling the system, and I already have a working Vera system (don't fix what ain't broke). Of course, I give up the ability to control LinuxMCE through the net, but I was only interested in doing home automation and surveillance remotely.
-
... so I am not sure if the network is ok now.
do you have any issues?
-
if it is a sleeping device you need to either send a node info frame (e.g. triple press on the merten remote switches) or wait for it to wake up (if the wake up configuration is set properly)