Stuck in between versions and no support

[michaelhusbyn 3]

Hi

 

I upgraded HCL to 4.110 and that was a big mistake. Unstable HCL and unhappy wife came with that upgrade.

Contacted support 9th of January but no response. So I reverted back to 4.100. Now I cannot login (cleared cache of browsers) and I only get spinning circle after entering credentials. Tried recovery upgrade back to 4.110 and only get 403 error after credentials.

 

So back to 4.100 and everything works, timer and nodon remote works. Also happy wife...

but no way to change anything. 

 

I'm then stuck between versions and not so keen to wipe all config. Hoping for fixes in next version..

 

Fibaro is using all resources on FibaroID and not support/fixing software that is in desperate need of TLC/openness 

 

 

[Flowy 36]

4 hours ago, michaelhusbyn said:

 

So back to 4.100 and everything works, timer and nodon remote works. Also happy wife...

 

 

That's the most important thing, all the rest is the usual complete chaos.

Imagine that I am still with 4.090, I know all its bugs and I can survive with them with all implemented tricks. Now it would be too much dangerous to touch it, beta or stable (ok everybody knows they are the same....)

Edited February 1, 2017 by Flowy

[michaelhusbyn 3]

To continue the story. 

 

No response from support and I'm 90% happy with the current working solution.

 

But I do not like it that my Nodon controller not works as it should. So I needed to do something.

 

4.100 version, recovery mode. Reset configuration. Could login again.

Restored a backup I had and all devices came back. Also scenes.

 

Now Nodon works every time, fibaro controller do have the correct lights, and I still can logon.

 

Will think 993 times before upgrading to next version

 

[Kuba13 49]

On 1. 2. 2017 at 10:40 PM, Flowy said:

 

That's the most important thing, all the rest is the usual complete chaos.

Imagine that I am still with 4.090, I know all its bugs and I can survive with them with all implemented tricks. Now it would be too much dangerous to touch it, beta or stable (ok everybody knows they are the same....)

 

nah Beta version can get really bloody brutally bad (remember the screwing with scene triggers?). Stable releases are slightly patched betas with USUALLY lesser likelyhood of properly destructive bugs.

 

On 18. 2. 2017 at 8:39 AM, michaelhusbyn said:

To continue the story. 

 

No response from support and I'm 90% happy with the current working solution.

 

But I do not like it that my Nodon controller not works as it should. So I needed to do something.

 

4.100 version, recovery mode. Reset configuration. Could login again.

Restored a backup I had and all devices came back. Also scenes.

 

Now Nodon works every time, fibaro controller do have the correct lights, and I still can logon.

 

Will think 993 times before upgrading to next version

 

 

Glad your HCL works,

 

now sad news is that if youll want remote access you both will have to convert to ID at some point (end of March - oh that will be great 1st April...). Which is both annoying and understandible given what they are planning (actuall backups on servers with the other HCL data yayy!).

 

I keep having major reservations regarding Fibaro's team the whole conversion is troubblesome, but at least it has decent timeframe for users to get used to it.

[michaelhusbyn 3]

Well, Nodon remote did not work after a restart.

 

Hopefully Fibaro comes with a good version before they require 4.110 or newer to be able to use app/remote.

or postpone the requirement.  I'm not betting on any of them.