Not upgraded to 4.42? Worried? Don't be, read on....

[dw89 8]

Hi All,

 

Over the last few months we've seen all the problems associated with v4[n]. Fibaro have, rightly so, been given some stick. Due to all this I, for one, with a large system (@70 physical devices, 200+ in total and 30 scenes) was very worried about upgrading, and yet, I have been dying to upgrade to sort out things like the motion sensors changing type and other features like https, the intercom etc.

 

All I can say is, IMHO, you shouldn't be worried about upgrading,,,cautious sure but don't let it stop you. I, first of all, backed up everything, disabled all scenes etc and my system was working as well as 3.590 could have done. So, I started the upgrade at @1pm yesterday and within half an hour (mainly due to having lunch!) I was on 4.42 and, more or less, everything seemed fine!!

 

Immediately there will be things you need to address i.e. Motion Sensors (Fibaro) will have extra children (i.e. the Seismometer), which you can add. Apart from that I was pleasantly surprised that not much of what I had was broken at all. I have also found a lot of things that 'work' but don't have templates i.e. Popp Power, Popp Dimmers, TKB Z88s, Vision CO Sensor, Vision Powered Alarm, Qubino Dimmer. I don't really know why this is (they're all quite common) and I don't know whether to try a soft config on them (read TKB issue below) but they do, at least in general, all still work. Once everything was verified working I went through and started to check my scenes and re-enable them one by one. By 8pm all was working 'almost' as good as 3.590 (but with some caveats - see below).

 

The Bad:

1) A lot of 3rd Party templates not there e.g. Popp Power, Popp Dimmers, TKB Z88s, Vision CO Sensor, Vision Powered Alarm, Qubino Dimmer

2) Apart from Greenwave Powernode Energy Metering is not working AT ALL. Big big big problem...it all worked fine in 3.590...what's going on Fibaro??

3) I tried to soft-config a TKB.....and I got x3 extra children from nowhere and power metering still not working for me. Surely someone else must have come across this (I believe Raj has). This is bad. I have 15+ of these plus @10 Popps.

4) Based on above I had to take all Power related code out of my scenes....again really NOT good.

5) Another BAD I'm afraid. I have some Fibaro 2x1.5kW relays in ceilings which control LED spotlights. In 3.590 you can set controlled device in advanced tab as 'Lighting' and it showed up in iOS App as lighting. In 4.42 this doesn't work...only shown as switch. This is a serious pain for turning on/off my lights as they're not where a) we're used to...in Lighting and b) my wife's 100% confused as to what's going on. PLEASE fix this asap. 

6) RAM usage....odd one. Overnight was @40%....this morning @40%....then now 98% and nothing's changed other than I have the HC2 open on windows! Only 2 scenes running (which are on all the time)....so I don't know what's going on here.

7) Plugins not available yet for devlopers

 

The Good:

1) Upgrade for me was pretty flawless. Had to refresh screen constantly to see progress but it took minutes really. Took more time to get to 3.6 first than it did to get to 4.42. Well done Fibaro:)

2) I LOVE the intercom. It works flawlessly as far as I can see and is one of the main reasons I upgraded as I need it for my house. I can't say how great this is...it just works and seamlessly goes between main app and intercom. 110% Fibaro...LOVE IT! Hurry up with the outside Intercom please otherwise I will have to buy Mobotix!

3) Fix to Motion Sensors....GREAT!

4) HTTPS...great

 

So, the ONLY reasons I would say are still big issues for ME (coming from 3.590) are Power Metering, relays not showing up as lights, 3rd Party templates. I do hope these are fixed...especially Power Metering (big big issue), otherwise I think though it's taken time, Fibaro are definitely getting there. Well done guys!

 

Dave:)

 

PS If any of these issues are easy fixes please let me know!

[deanrparry 19]

If your popp power entering are in extensions they can play up! Just a little something I recall when I had some! If they are in extensions try to use only one and make sure its closet to the mains cable end

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" />

[dw89 8]

Cheers Dean, see your still about!

 

Nah, they're not in extensions....and still no joy (well they work but no power metering at all)! Still, bit of messing about to try yet. All the best, Dave:)

[kmeta 2]

Dw89

What type of intercom are you using ?

[dw89 8]

Hi, I'm not.....just the Fibaro software Intercom via iOS (look in AppStore) which works with v4.

 

I'd like the Fibaro hardware Intercom if they hurry up and bring it out....otherwise I will go with a Mobotix T25 which also works well with it apparently.

[deanrparry 19]

Nip in forum still... Nothing special plus still have box at work! Just not at home due to marriage

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" />

[boomx 43]

Hi & wb Dean

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" />

[Guest fat]

I find this version to be far less stable than v3.6

I have scenes that don't trigger sometimes. RGBW and Roller Shutter v2 become non responsive sometimes, and also have long delays (45 sec delay between using iPad to open blinds and the blinds starting to open). My system is only small consisting of 2 Fibaro motion, 2 dimmer, 2 door sensor, 3 roller shutter v2, 2 Lockwood door locks, and 2 Aeon multi sensors

[dw89 8]

Hi fat,

 

Obviously can't really comment on your system but, was it all working 100% before you upgraded? What's your RAM like? From what I;ve read weird things can happen (or not!) if RAM gets high i.e. things don't work or odd things happen without being asked.

 

I have things that blatantly don't work at the moment, however those that do do work and work as good as before pretty much. Slight delay maybe but I'm putting that down to change and, at the minute, 4.042 is still not classed as 100% stable so they're still working on it.

 

I'm just saying it's not the complete disaster I was expecting shall we say...and there are lots of good bits worth upgrading for. At the end of the day they'll want to get it right in the end.

 

Dave:)

[Guest fat]

My system was rock solid on v3.6. Not a single issue with it ever. Since upgrading I have been looking at RAM as a few people have commented about it being an issue, but my RAM usage has always stayed quite stable and never gone about the 50's

[alex88 71]

dw89

 

i am glad to hear you are enjoying v4, but i think you should caution those thinking of upgrading a little more. 

 

There are lots of great features in v4 but there are also still lots of pitfalls... these are just a few that I have found:

 

1) Fibaro RGBW modules 

- cannot be associated to other modules (only tried other RGBW's at the moment)

- cannot change parameters (they will not stick, just go back to defaults)

- on reboot of HC2 random modules appear as ON despite being OFF

 

2) Relay

- S2 cannot be associated; only tried to associate it to another Relay

- Trying to associated screws the Relays up in that parameter changes do not stick

- The only fix I can find is to delete and re-added the Relay

- Parameter changes on Relay do not stick unless updated and saved several times

 

3) Heating 

- Cannot change temp/time in Tablet/Android App; or if it us not greyed out and does allow a change it does not stick

 

4) Shutter not configured error

- Appears during use

 

5) Changing device parameters

- Sometimes need to hit F5 (refresh screen) for parameters to appear updated / to update

 

6) Android Mobile app

- Occasionally it does not find the HC2 ie does not connect – very annoying

- Intermittent lags between request and action; up to 10 seconds

 

7) Android Tablet app

- Intermittent lags between request and action; up to 10 seconds

 

8) Scenes

- Scenes that ran fine just seem to stop working

- Clicking on save seems to reset the scene as Active

 

Also, people should really look at bugzilla and check in case something critical to them is not working in v4. I know it's very hard to find the bugs and sift through them, but it's worth going through it first rather than suffering later.

 

That said, it is getting better. For me personally if half of the above bugs (1,2,3,6 and 7) were sorted I'd find it hard to not actually be a happy customer for a change. Fingers crossed by the end of the year the main bugs will be resolved and we can look forward to an exciting 2016!

 

What do you mean by: "4) HTTPS...great"?

[A.Socha 133]

ad 1) we are ending fixing problem with RGB so will be soon fixed (maybe even next version)

ad 2) that is not a bug (on 3.590 that was impossible too) but I'm not saying that we not gonna change this. parameters for relay please look on top logs and say is there a info about received parameter what you was send?

ad 3) more details like andoid tablet can't set up new value for horstamn thermostat ..... because saying that is not working is not helping because on tested scenarios by us it is working (move or print-screen are welcome)

ad 4) it will soon be changed from not configured to not calibrated. set up parameter 29 on 1 to start process of calibration

ad 5) still working on it but it will be impossible to fix all because for battery how long we should wait? to next wakeup (1h -2h) and block till then interface? sending something to battery device gonna need f5

ad 6) more details Is you got that lag on controlling from page too? you are sure that smartphone got local wifi (when not finding HC)

ad 7) like above

ad 8) with what error? lua block magic? what scene doing more details

[alex88 71]

ad 1) we are ending fixing problem with RGB so will be soon fixed (maybe even next version)

ad 2) that is not a bug (on 3.590 that was impossible too) but I'm not saying that we not gonna change this. parameters for relay please look on top logs and say is there a info about received parameter what you was send?

ad 3) more details like andoid tablet can't set up new value for horstamn thermostat ..... because saying that is not working is not helping because on tested scenarios by us it is working (move or print-screen are welcome)

ad 4) it will soon be changed from not configured to not calibrated. set up parameter 29 on 1 to start process of calibration

ad 5) still working on it but it will be impossible to fix all because for battery how long we should wait? to next wakeup (1h -2h) and block till then interface? sending something to battery device gonna need f5

ad 6) more details Is you got that lag on controlling from page too? you are sure that smartphone got local wifi (when not finding HC)

ad 7) like above

ad 8) with what error? lua block magic? what scene doing more details

 

1) glad to hear it. can't wait!

2) didn't realise that. looking forward to the update

3) Sure A.Socha. I have provided all these details previously in emails and in part in bugzilla’s, however in the interest of getting it fixed I have just re-tested on v4.042:

 

In the Android tablet – from the thermometer icon:

  a) click on the thermometer icon (3rd from the left) in the top bar

  b) for any thermostat (mine are mainly setup using linked devices made up of fibaro relays and fibaro temp sensors from the fibaro motion sensor module) click on the plus sign of the temp until you have set the temp above the setpoint

  c) click on the plus sign of the timer

 

The actual behaviour is completely erratic:

Setting the set point temperature:

  a) Sometimes performing b) above the set point temperature ie the temp on the top not the bottom:

    -- goes up from the current set point temp (let's say 20C) in 1C increments

    -- goes up from the current set point temp (let's say 20C) to immediately above the actual temp (let's say 23C) to 24C and then goes up in 1C increments

    -- disappears completely so that only current temp (let's say 23C) is showing, clicking again a second time it appears again at 1C above the current temp e.g. 24C

    -- goes up from the current set point temp to above the current temp and then disappears within less than a second

    -- goes up from the current set point temp in 1C increments but keeps immediately resetting itself to the set point temp

 

Setting the time for the override

b) Sometimes performing c) above the timer:

    -- goes up to 15 minutes, then 30 minutes and so on

    -- goes up to 15 minutes, disappears, then clicking again it goes to 30 minutes, 45 minutes and so on

    -- does either of the two above and then disappears completely immediately after

 

In all cases the set point temp and timer will ultimately reset themselves (in the VDU) so that the set point goes back to the default (ie setup in the heating panel) and the timer disappears. Now, it looks like some progress has been made here. I checked the heating panel and in fact sometimes the set point and timer increase are actually being received. This is progress! But in some cases they just do not ever get communicated.

 

In the Android tablet – from within a room:

a)    Click on the thermometer on the left hand side column (second from the top, under the light bulb)

By default the word heating is highlighted in red in the panel at the bottom (to the left hand side) of the screen. It does not matter what I press whether it be the + or – signs where it says “OFF Heating Mode” or “- Time to finish”, nothing works. Likewise I do not know how to activate ventilation despite having means of ventilation in some rooms (ie air filters). Quite simply this part of the Android app does not and has never been anything other than a fixed image for me with no user changeable functionality.

 

In the Android phone – from the climate shortcut:

As I stated above, I have retested this and I am glad I did so rather than just write down the problem as it existed in previous versions:

a)    Click on the climate shortcut

b)    Click on a room with a thermostat

c)    Click on the top + sign to increase the set point temp

d)    Click on the bottom + sign to increase the override time

Things have moved along. The temp and timer changes stick and work as expected ie 1C and 15 min increments/decrements. The changes ARE communicated to the HC2, however when I leave the screen and go back to the same room it does not show me the set point temp and time remaining. Instead it just shows the heating panel set point temp and no time details ie “-“ when the time should be displayed. This is progress, but it’s still not where it was back in an older version of the Android phone app when it worked as expected.

 

4) ok

 

5) if you say so. I don’t really see this anymore as I have a technique to deal with it and I was experiencing it on mains powered devices.

 

6) and 7)

I am loath to give any more details on this other than to say yes, “I is not stoopid!!! It is on local access”

This is well reported on the forum and in Bugzilla. I can unequivocally say that neither the Android phone app (which I have had installed since the first beta was released) and the Android tablet app (which I have had installed since the beginning of this year) have ever connected consistently flawlessly on any version installed. There are multiple problems including:

-       not being able to find the HC2

-       failing authentication

-       looking like it is connected but when making changes they do not get communicated back to the HC2 or they do but with a delay or up to 1 minute (but usually less than 10 seconds)

The tablet is a lot more stable than the phone. I don’t know why, but for me it simply is. I have tested on 1x Sony Z3 phone, 2x Samsung S4 phones, 1x Samsung S2 phone, 1x Lenovo tablet, 1x Sony Z2 tablet. I can’t say anyone of the devices works better than the other barring that the tablets are more stable than the phones.

 

8) There is a bugzilla for this, but for some reason I’m struggling to find it. Argghh!!! I have reported this to UK support as well and there is a thread on the forum about issue where scenes are not working.

Put simply you click save on a scene, test it and it works fine… for a while. Then (usually I spot this the next day) the scene just stops working. Until I click save again on the scene, then it starts working again and seems to work indefinitely from there on in. I did have a problem in v4.040 where it stopped working again after the 2^nd save but this seems to have gone away in v4.042.

 

I am looking forward to getting resolution on the above as well as my Bugzilla on the Fibaro Blind Module and my windows. Notwithstanding that it’s practically summer, so I couldn’t care less right now if the heating panel works or not, I am happy to record a video of the behaviour on the tablet/phone for you, but you’ll only end up seeing what I have explained above.

[dw89 8]

Aleks,

 

Perfectly understand what you are saying, just saying that, in my experience (based on what I have), that it's not the disaster I thought it 'could' be...that's all. Certainly a lot of room for improvement but still 'pretty' good.

 

HTTPS support in scenes/VD's etc i.e. you can use secure HTTP which we couldn't in 3.590/3.6

 

A. Socha, Any comment on the Power Metering for TKB, Popp, Greenwave? Nothing's working for me and I'm pretty knackered without it.

 

KR, Dave

Please login or register to see this image.

/emoticons/default_icon_biggrin.gif" alt=":-D" />

[dw89 8]

Oh, just remembered, I too have noticed that iOS isn't always showing updates to switches etc as well as it used to in 3.590

 

Also, A. Socha, the switches thing (where you cannot make a relay which controls light) show up as lighting in iOS (shows as switch even if you say controlled as 'Lighting'). Is this being fixed? This is a real nightmare for me when my Everspring light sockets and Fibar relays don't show up as lights

Please login or register to see this image.

/emoticons/default_icon_confused.gif" alt=":-?" />

 

KR, Dave

[rajp 14]

Aleks,

 

Perfectly understand what you are saying, just saying that, in my experience (based on what I have), that it's not the disaster I thought it 'could' be...that's all. Certainly a lot of room for improvement but still 'pretty' good.

 

HTTPS support in scenes/VD's etc i.e. you can use secure HTTP which we couldn't in 3.590/3.6

 

A. Socha, Any comment on the Power Metering for TKB, Popp, Greenwave? Nothing's working for me and I'm pretty knackered without it.

 

KR, Dave

Please login or register to see this image.

/emoticons/default_icon_biggrin.gif" alt=":-D" />

The TKB power metering is now on multiple devices in my setup.. I have switched my power reading off the second device and it is working as expected. Though, why it has been split into multiple devices, I have no clue. It does now also show the power input from Mains now too.

 

 

Oh, just remembered, I too have noticed that iOS isn't always showing updates to switches etc as well as it used to in 3.590

 

Also, A. Socha, the switches thing (where you cannot make a relay which controls light) show up as lighting in iOS (shows as switch even if you say controlled as 'Lighting'). Is this being fixed? This is a real nightmare for me when my Everspring light sockets and Fibar relays don't show up as lights

Please login or register to see this image.

/emoticons/default_icon_confused.gif" alt=":-?" />

 

KR, Dave

 

This is also happening to me on the iOS devices. I have to go and refresh from Network for it to pick up the correct status.

[alex88 71]

Aleks,

 

Perfectly understand what you are saying, just saying that, in my experience (based on what I have), that it's not the disaster I thought it 'could' be...that's all. Certainly a lot of room for improvement but still 'pretty' good.

 

HTTPS support in scenes/VD's etc i.e. you can use secure HTTP which we couldn't in 3.590/3.6

 

A. Socha, Any comment on the Power Metering for TKB, Popp, Greenwave? Nothing's working for me and I'm pretty knackered without it.

 

KR, Dave

Please login or register to see this image.

/emoticons/default_icon_biggrin.gif" alt=":-D" />

 

I also understand your comments.

 

On the positive side my system is actually fairly stable and lots of the functionality is working as expected.

 

Now if Fibaro can keep the momentum up and iron out the remaining critical/severe bugs then they will have finally provided to us the system that we paid for and have been waiting for (some of us for 3 years now). I sincerely look forward to that day!

 

 

*******************************************************************************************************************************************************

Can you please share any code you have on HTTPS?

 

I really want to send commands to my voice activated UBIs from my HC2. It will transform the level of interaction. At the moment I can only send commands from UBI to the HC2 which is great, but audio feedback from the UBI and being able to pull from the 5 sensors to the HC2 would be awesome!

*******************************************************************************************************************************************************

[A.Socha 133]

How to do get in https on 4.x

Please login or register to see this code.

[alex88 71]

 

How to do get in https on 4.x

Please login or register to see this code.

 

Thanks. I will try it out soon.

 

 

UPDATE: It works!! I now have scenes that get the UBI to speak. Awesome.

 

I am not sure why but when I embed the code into a scene it only works if the scene aborts straight after. Any scene that has more code running will not execute the HTTPS request. In the end I have setup a single scene to handle all UBI speaking requests and barring a little lag (which seems to be inconsistent) it is working like a charm.

 

Thanks for the code A.Socha 

Please login or register to see this image.

/emoticons/default_icon_smile.gif" alt=":-)" />

 

UPDATE2: I don't know why or how, but the lag seems to have gone away. Fingers crossed it stays that way.

[dw89 8]

Sorry Aleks,

 

Only just saw this, glad you sorted it out

Please login or register to see this image.

/emoticons/default_icon_biggrin.gif" alt=":-D" /> Please explain your UBI?

 

I've not messed with https yet (only been on v4 a week) but I will be using it for Pushover very soon so I can do away with my fixed IP pushover scene......it'll now be dynamic which is fantastic.

 

Anyway, updates for Fibaro.......

1) The 'not being able to make a switch a light' scenario.....for some reason, out of the blue, it started working?! WTF?! One worked at first so I kept changing the 'controlled as' parameter to 'Lighting' and 'Saving' and eventually they all work as they should. Don't ask me why they didn't work straight off.....guess we'll call it a transition 'feature'

Please login or register to see this image.

/emoticons/default_icon_razz.gif" alt=":-P" />

2) Still nothing on Power data Fibaro??? No response A Socha?? Surely you can tell me whether you are working on fixing this or not? Looks like Dean had a ticket on it but it got closed for some reason??? Why when it's not fixed?

3) Maybe this is just me....but what exactly is the point of Plugins? i.e. Roadmap or reason? I only ask because, naively, I thought that I would be, at last, able to (eventually) create a plugin (to give away or sell) and be able to assign it as a widget to the home screen (say an Alarm or Remote or whatever) but, as I just tried, you STILL can't assign VD's as a widget and nor can you do it with Plugins? WHY fibaro, please tell me. This is a major design flaw in my opinion....the user wants to be able to access custom VD's or Plugins from the Home Screen but can't....there's no quick pick (like with Scenes, Temp, Lights and Alarm) and you have to go 'find it' in the particular room which, if it's an alarm VD, takes WAY too long! Surely you could, say, add a quick pick to the top bar? PLEASE!

 

Dave

Please login or register to see this image.

/emoticons/default_icon_biggrin.gif" alt=":-D" />