1.042 update

[davedotnet 0]

I had a quirky moment last night when I upgraded to 1.042 from 1.041, but the dialogue box that pops up said it was installing 1.041. It did install 1.042 though. Clear as mud.

[Krikroff 199]

further proof of the lack of seriousness in the development...I want a v3.xx stable and non buggy with a clear documentation of all functionalities in details !

it seems that in some cases even the fibaro developer seems discover the operation of the box

Please login or register to see this image.

/emoticons/default_icon_rolleyes.gif" alt=":roll:" />

[A.Socha 133]

davedotnet, before every update you must clear cache by ctrl+f5 then you see all ok

[gestel73 0]

davedotnet, before every update you must clear cache by ctrl+f5 then you see all ok

and again the question of Krikroff is ignored.

Please login or register to see this image.

/emoticons/default_icon_cry.gif" alt=":cry:" />

can you please give a answer to the question. when can we expect the v3 update with the needed documentation and support.

[Guest fab971]

davedotnet, before every update you must clear cache by ctrl+f5 then you see all ok

and again the question of Krikroff is ignored.

Please login or register to see this image.

/emoticons/default_icon_cry.gif" alt=":cry:" />

can you please give a answer to the question. when can we expect the v3 update with the needed documentation and support.

+1. When???

[davedotnet 0]

More quirkiness.

I have a phantom device that doesn't exist and no way of deleting it. It has a Node Id of -1. I think it appears when I add my Aeotec Motion Sensor, but deleting that Aeotec Motion Sensor doesn't delete this phantom device. Any thoughts about how to delete such things ? (yes, I've clicked the 'X').

This is a 1.042 feature.

[Krikroff 199]

Please login or register to see this image.

/emoticons/default_icon_arrow.gif" alt=":arrow:" />

Please login or register to see this link.

Users with the same problem have resolved like that: recovery to version 1.040, delete the phantom device and update to 1.041 and 1.042 ...

I hope help you...

All the best.

[davedotnet 0]

@Krikroff Thanks, but I've had to do this so many times, that I'm now moving the devices to a 'room' called "Orphaned", resetting the device and including it again.

That said, I've spent quite some time today with my Fibaro installation and I can confirm that it's mostly in a mess due to the last couple of releases. All of my Vitrum devices are now recognised as "Unknown" (they were fine before). Any GroupIDs/Associations on any device have not only been deleted, but for all my Vitrum (now 'Unknown') switches the means to add them back has gone. Why HC2 felt the need somewhere along the way to reconfigure devices that required no tampering I'm not sure.

It just leads me to believe that the entire device management software is flawed. How can something that returns a ManufacturerID of "Think Simple srl" (0x010A) then end up as a manufacturerID of "Fibargroup" (0x010F), and, then be confused about what EndPoints it has. EndPoints are hardwired to the ManufacturerID and ProductID, but Fibaro logic gets confused and attaches Think Simple endpoints to Fibaro manufacturer. I'm at a lost with the whole thing.

Is there any regression testing in any of this? any source code control ? any discipline at all in the software development process?

[davedotnet 0]

Well, a week on and I think my system is just a mess. The performance is dreadful. I can't delete any of my devices "Failure to enter learn mode". The "X" on any device entry won't work. The countdown on my delete devices screen decrements at a rate of about 3 to 4 a second and enters negative territory! and when it's finished counting down, it starts again and goes into a vicious loop.

I'm going to have to muster up the enthusiasm for a complete rebuild of 30 devices (reset them all, add them all, configure them all).