Update 3.583 BETA

[I. Szymanski 0]

Beta version is designed for user testing and soon will be released as official.

WARNING! In case of update from old version, v1.x, after that update all users will be deleted. Admin password will be reset. Also update to Beta software all devices will be automatically reconfigured to work with new system architecture. Reconfiguration progress will be shown in pop-up window.

This update can last longer than previous. If this update lasts longer than 30 minutes, please go to main HC2 address (e.g. 192.168.0.1).

If "System temporarily unavailable" text will appear during update, please wait - you will be redirected to the main page when all services start.

Mobile apps fully working with this version:

- iPhone app - version 2.1.1 (available on the App Store),

- Android phones app - version 1.3 (available on the Google Play),

- iPad app - version 1.2 (available on the App Store).

3.583

- Z-Wave engine improvements.

3.582

- Fibaro Alarm minor fixes.

- Gateway Connections improvements.

- Other minor bug fixes.

3.581

- Optimized for remote access activities.

- Support for Fibaro Motion Sensor.

- Other minor bug fixes.

[Guest shapa]

Again, the same for me. 2 days - one sensor battery is already empty.

Fibaro QA team is non-existent...

where the problems started. Not sure if they were not properly detected (e.g. no battery icon?) but after a few days the battery of some was already empty (I thought well, cheap battery and bought some new)..

[GlennNZ 0]

Update again

Had prompt reply from support despite time difference issues.

Suggested it may have been autolights - "using a lot of hardware resources"

Never been issue before and is the backbone of my automation - as no point turning something on without it turning off later !

None-the-less deleted it.

Please login or register to see this image.

/emoticons/default_icon_sad.gif" alt=":-(" />

No change.

Very slow response to commands - things on 5 minutes later off with similar delay.

Still something else Major going on.

Waiting for someone in Poland to wake up.

Glenn

[Guest shapa]

robmac,

Never seen any HC2 "beta" or "stable" version which is stable enough to be really stable.

I'm very happy that Fibaro smoke alarms are just for redundancy - Nest works ideally (zero problems, push notifications are nearly instant, very sensitive and reliable, interconnections works fine also), Fibaro's one is like a toy instead of reliable fire alarm system.

Guessing when someone will burn his house and create some legal case against them

Please login or register to see this image.

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

Hopefully no deaths will be involved.

[robmac 173]

It is deeper than that. If it was that simple everyone would have issues.

[K.Bergmann 2]

Dear Users,

Please be sure that first feedback about our products is extremely important for us. If you will find any difficulties or issues please feel free to ask our support team or report it using bugtracker.

[deanrparry 19]

Please login or register to see this link.

There is your first one

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" /> feel free to ask me questions like...

How annoying is the beeping after 2 days? is it loud enough to wake a 9 months old baby?

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" />

Good luck and by the way you do not even need to include it to the zwave network just pull one out the box and plug in 12v 1a adapter...

[robmac 173]

that is interesting Dean.

So the unit I have was working when it was connected with the HC2 on old version.

Now the HC2 has new version and it is not.

Your device also has same symptoms when there is no connection.

New version changed how HC2 communicates with modules.... looks suspicious.

[A.Socha 133]

robmac, but hc2 can't turn on chamber alarm on device, every 5s smoke testing self if he check problem with chamber he start alarming that why we asking about hardware not about hc2

if you dont trust me try go back to last stable and check if you get chamber alert on 3.580

or stay on 3.583 but move smoke sensor to other place for test

[deanrparry 19]

or just use batteries and the problem seems to vanish!!!!

[ Added: 2014-02-25, 22:13 ]

robmac, but hc2 can't turn on chamber alarm on device, every 5s smoke testing self if he check problem with chamber he start alarming that why we asking about hardware not about hc2

if you dont trust me try go back to last stable and check if you get chamber alert on 3.580

or stay on 3.583 but move smoke sensor to other place for test

^^^

that was my point! my sensors did not even know about the hc2 box! yet as soon as i powered them up "beeeeeeeeeeep bbbbbbbbbbbeeeeep beeep" driving me mad! as Socha says its detected a fault internally but as i said to Socha 3 units and 3 failing? i am not the luckiest person on the planet but i sure as * would expect 1 out of 3

Please login or register to see this image.

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

so either they do not like my psu or they do not like ANY psu! it has nothing to do with the location either!

kitchen/bedroom/nursery/living room/mars/venus/moon!

[A.Socha 133]

deanrparry, shapa was wrote that he got that problem but on battery but give me feedback if on battery you will get that alarm too

deanrparry, Robmac all your sensor was power up by 12V?

[deanrparry 19]

all my flood sensors and smoke sensors and ubs use EXACTLY the same 12v 1a units...

Please login or register to see this link.

[ Added: 2014-02-25, 22:17 ]

i am just saying socha that since swapping to batteries not ONE beep!

[ Added: 2014-02-25, 22:19 ]

and personally judging by shapa comments i think he had it 12v powered initially? included then swapped to battery hence the major battery drain no? or he changed the default parameters?

[robmac 173]

deanrparry, shapa was wrote that he got that problem but on battery but give me feedback if on battery you will get that alarm too

deanrparry, Robmac all your sensor was power up by 12V?

Only the smoke sensor and I only have one to test just now.

I have not moved it so unless it failed by coincidence just after the upgrade it makes no sense.

Happy to swap it out for a new one

[ Added: 2014-02-25, 23:07 ]

robmac, but hc2 can't turn on chamber alarm on device, every 5s smoke testing self if he check problem with chamber he start alarming that why we asking about hardware not about hc2

if you dont trust me try go back to last stable and check if you get chamber alert on 3.580

or stay on 3.583 but move smoke sensor to other place for test

It does not go off every five s it is every few hours for me.

It ran for weeks with no issue.

Sure HC2 does not turn it on but if module does not hear from HC2 properly could it falsely report a chamber issue for a communication issue.

Also why no temperature reports... remove, reset and add back and I have temperature reports.

[deanrparry 19]

yes robmac every few hours but approx 5 beeps 1 sec apart with red led?

[ Added: 2014-02-25, 23:16 ]

so what your implying robmac is that potentially 3.853 has upgraded the firmware on the smoke sensors? a.socha is this likely?

[ Added: 2014-02-25, 23:16 ]

and would me doing a factory reset of the sensor resort it back to day 1 firmware or 3.853 still?

[Poppy 0]

Hello,

I don't know if this can change but i have 2 Smoke sensors and one ubs powered on one 12V 1A power source (

Please login or register to see this link.

).

For the moment i don't have any problem. I see on other post that the humidity was at 50%, personnaly i have 28% in all my room.

Steve

[GlennNZ 0]

Hi

As much as constant beeps sound annoying - and they do - my 3-5 minute delayed HC2 response has been meet with by support deleting and/or disabling any main loop device.

(No smoke alarm available or installed in this Zwave area)

So far have deleted autolights and essentially have no ongoing automation as this controlled everything. (X6-7 devices only). (Autolights forum feedback suggest unlikely cause - I suspect using more resources than normal as nothing was responding correctly) ie. symptom rather than cause.

Delayed response less frequent but still occurring - none-the-less seems end of supports interest.

Surely this is symptom of wider recently introduced or exacerbated. bug - basic level support surely not going to get to bottom of this? I understand is beta, but some new problem immediately with new beta surely shouldn't have to work its way up support food chain?

Glenn

Will give it a few days more and then recreate and setup auto lights again ;one evening gone, and if/when delays start again probably go thru same process.

Hmm.

[ Added: 2014-02-27, 08:08 ]

I note new 3.590?

But also that 3.583 is no longer listed? Was there a defined issue?

Glenn

[dcspock 17]

Update

After the update to 3.590 the same issue persists - HC2 cannot send signals to the network but receives info about changes.

When reconfiguring the network, it starts already with 59 from 204 devices (the loading bar) - no change...

I guess I will have to write to support if nobody has any further idea...?

Please login or register to see this image.

/emoticons/default_icon_sad.gif" alt=":-(" />

[GlennNZ 0]

Thats no good.

I have found 3.590 helped - although was concerned this morning with minor interaction that was slow and problem may be returning - although didn't - but still early days.

I would strongly suggest emailing support and allowing them port 80 and port 22 access to the Hc2 and include that in your email.

I have found them helpful - although the biggest improvement did seem to be 3.590 - they did also reflash the HC2 z-wave chip in case that was the issue.

Glenn