3.x to 4.x upgrade retrospective

[robmac 173]

things to expect when you upgrade.

1. You get a new lua engine that behaves differently

. Calls are type sensitive and new calls possible. But you get better documentation on developer.fibaro.com Expect some code changes needed.

There are some bugs coming out but no show stoppers.

2. You get changes to z-wave engine and this has many impacts.

A. Some templates do not work any more/missing

B. Upgrade process reconfigures devices and may highlight issues from old engine. You will have to reconfigure and even remove and add. I found a lot of devices needed association required reset even though the interface showed good association.

C. Polling is not working so if you have a lot of devices that do not report association you are not going to like this.

D. As polling does not even run once you can not trust state on restart. Anything switched while controller lost

E. Some devices that need special handling are not supported

3. The changes to lua may impact block scenes. Certainly code generated from blocks on conversion to lua editing involves a bug I identified.

If you consider all this before you upgrade you will know what your risk is and work you will need.

As reported by others this release does a lot of things well but has a few bugs. Due to the big changes it does have a big upgrade impact so plan to have to make some effort.

[deanrparry 19]

I think step 3 was the cause of my headaches... Problem was I didn't know which scenes affected upgrade so could not get to delete them quick enough before ZWave engine crashed! So I second your findings and found this could not be fixed without SSH from Fibaro or having pen and paper documentation of each scene number and deleting them super duper quick as api is not accessible either after few seconds.

Thanks again for helping other users see the light

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

[alandee 79]

Great post and great advice .. Newb or not, this is all very worth considering .. Just a day late for me!

Frankly I would not have upgraded as the investment in time is not something that I have enjoyed this time around, nor has it come at an opportune time with illness in the family, hence my desire to get some night lighting happening, and mainly because I wasn't expecting to have to.

This is the sort of communication perhaps the manufacturer could convey rather than pushing a blinking light and also I think then if one must consider all of these things, and look it's maybe just me, but then maybe it should not be an upgrade to stable. For instance if you upgrade from a working 3.6 stable to a 4.03 stable .. Is there not the expectation that it will be .. Umm .. What's the word ... Oh yeah stable at the very least ?

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" /> !

However I did just notice :

Please login or register to see this link.

so company feedback may be a mute point.

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

I'm a bit negative on the whole thing though at the moment, so, I'll refrain from posting negatives for a few days, and once I can turn lights on again and have a working siren and change a few of my scripts, and get it all set up again, I'm sure it will be just in time for the next update and all will be well with the world.

Cheers,

Al.

[dw89 8]

I do agree with alandee 100%, it's really not on....I don't see any caveats to 'stable'.

I really wanted to update to get my long awaited non-working motion sensors working....but apparently even they have no parameters?! Keyfob2 also isn't working apparently and then there's code changes which no one seems to know, but they brave few who have had time to mess with it all, what they are and how they affect things. These are all things which should be explained and, in time (quick time I hope), fixed otherwise it's not an 'upgrade' is it?

Kudos to Robmac for giving us some advice. Perhaps it is worth downloading all scenes before an upgrade, deleting them in system, then upgrading and adding again one by one to see if any need changing? This would also show what effects if any it has on CPUs. Though advice on what needs changing would be more than helpful from Fibaro rather than just let us find out blind/by bricked HC2s.

I still love the HC2 but they do seem to want to test us! All this talk of using is stupid, that won't help solve anything it'll just put them under. Let's just try and get things fixed ASAP!!

KR, Dave;)

So that's Motion Sensors parameters missing (WTF, these are Fibaro products!!)

Door Sensor paramaters missing

Sceneactivation

Polling

Sleep to set timeout/recursive block bug issue

What else?