Help please! I've just bought a Home Center 2 and it seems to be faulty...

[Mathiasw 0]

I am running software 4.032

 

1)

It is not possible to create a new backup. The “backup popup” appears for about 20 seconds, but when it is complete, there is no new backup in the list. There is plenty of free disk space. All my most recent backups seem to have disappeared too.

 

2)

It is not possible to set up polling on any device. The “polling time interval” is fixed at 0, and any attempt to change it results in it going immediately back to 0.

 

3)

It is not possible to change the polling time interval from 125 (if it is even working). There is a message saying “Number of devices: 30.

Recommended devices polling time interval: 300s.” – but if you try to change the poll interval to anything other than 125, it changes back immediately.

 

4)

Power monitoring on all devices (Philio PAN-01/2/3) has stopped. Might be something to do with polling.

 

I've been stuck since Friday - I've raised a ticket with Fibaro but they have not replied, and it's taken 4 days to gain access to this forum (which I now gather is because it was down, but perhaps it would have been a good idea to make a note of that on the old sign-up page?).

Can anyone suggest any way of making polling and backups work again, or should I just send the device back to the supplier (it's only 5 days old) and get something else?

[1152 33]

Fibaro and HC2 SW v4.0xx is at the moment wip. So if you join the 4.0xx club expect to spend a lot of time and do a lot of work, trial and error. In general I say stay away unless you are equipped for the ride e.g. have the inclination and some experience in the field. (If you want a fairly stable system without to many surprises stay with 3.6).

 

PS As for your Q2-4 I think you will find your answers as you plunge in and read this forum

[dawiinci 5]

What you are talking about are bugs that are known since a long time. There is nothing wrong with your particular device - it's the software.

 

Decide yourself...

[robmac 173]

Item 1 is not normal. Possibly drop support a mail.

[Mathiasw 0]

What you are talking about are bugs that are known since a long time. There is nothing wrong with your particular device - it's the software.

 

Decide yourself...

 

I wasn't aware that I had installed beta software. I bought the device, plugged it in (it came with practically no manual), it asked to upload to the latest version and I picked the one that WASN'T marked beta. I wasn't aware that EVERY 4.xx software release was beta, or I wouldn't have used it.

If I wanted WIP software I could have stayed with Domoticz, which doesn't cost 500 GBP.

The whole reason I am leaving Domoticz is for stability.

[Mathiasw 0]

Item 1 is not normal. Possibly drop support a mail.

 

Support have now replied, and I'm going to give them ssh access to unwravel the box, or fsck it or something.

[dawiinci 5]

Officially this is not a beta. It might feel like one though.

[Mathiasw 0]

Item 1 is not normal. Possibly drop support a mail.

Fibaro have fixed the backup issue with a remote ssh login. I have been advised "not to use special characters in backup names". I don't know what he special characters are, but I am guessing that the some illegal characters were messing up either the file system or the display.

Hopefully they will modify the front end so it's not possible to ENTER these special, secret, characters - whatever they may be.

[UrSv 6]

It's usually @, % and & that cause problems.

[Mathiasw 0]

It's usually @, % and & that cause problems.

The code should validate or filter the user entered data - at the very least, to prevent an XSS attack. Failure to do so is kinda a schoolboy error.

[UrSv 6]

Sure, but this is a closed local system where only local password protected access is provided (remote access is not really access) by hopefully trusted users. I don't think anybody confuses a fairly cheap home kit with a high security multi user system with external access running something requiring high security, I for one don't. Failure to understand the different levels of requirements in system security is perhaps also a shoolboy error. Perhaps it really should do what you suggest and it's imply a bug right now. I don't know and it doesn't matter much. To me.