« Reply #74 on: February 08, 2011, 10:44:01 am »
This was a known issue of this release. Due to the stability issue complaints and the pressure from users to hurry, MCV decided to let 1.1.1183 out with the heal network issue.
JOD.
That's actually pretty low on my list, I don't actually know what benefit their is to running a "Heal" since the first/last time I ran it I lost so much time trying to fix the heal.
I really don't expect these guys to walk on water and they really do have a nice product but it would be SUPER cool if they'd let people know how to actually use it. Mine has been pretty stable lately and it does most things I want it to do but it sure would be nice to know what it's capable of and how to achieve it.
I guess I feel pretty let down by this "upgrade". We were told "it's coming, it's coming, be patient, it's going to be great" by the beta testers for a long time but here it is and I don't see any advantages.
Again, I don't want MCV or the beta tester to take this as a slam on the product or their work, I would just like something that explains it to me. I would like to see the things promised, such as The Puck support that we've been hearing so much about, the "and/if" control everyone is asking for.
You likely feel this way because you weren't blighted by many of the serious issues some users had! I was also lucky in that mine has been pretty stable and therefore wouldn't have seen a major difference unless I know what went into getting it working for some folks.

Logged
Kwickset locks, HA01C, HA14C, HA02C, HA03C, HA05C, HA04C, HA07C, HA09C, Aeon HEM, GE 45604, 45606, 45609, ZDP100, VRF01-1LZ, WDTC-20, HA18WD, WDHA-12R, HRDS1, HM-TS001, AC1-ZW, TV-IP110, BL-C210A, LUUP control- EtherRain8, DSC Alarm, HDMI matrix, HR24-200, Panasonic TV, SQblaster