Running 2.6.4 beta right now, and it takes some time (it did w/ other firmware releases as well) to create/modify scenes, adding and removing devices from scenes etc. and recently, about half of the time my request fails. When tryng to add a device to a scene, I get the system busy progress bar and it goes two or three times taking about 30 seconds each time. While I'm not crazy about the wait, I can easily accept it if it's the norm, but should this be expected?

Not happening here with 2.6.4. I do get the progress bar, but it's usually gone within 8-10 seconds. I haven't seen it go more than once. Do you have Access Points in your network?

 

Running 2.6.4 beta right now, and it takes some time (it did w/ other firmware releases as well) to create/modify scenes, adding and removing devices from scenes etc. and recently, about half of the time my request fails. When tryng to add a device to a scene, I get the system busy progress bar and it goes two or three times taking about 30 seconds each time. While I'm not crazy about the wait, I can easily accept it if it's the norm, but should this be expected?

Zellarman,

 

1. Do you have any RemoteLincs in those scenes?

2. What's the average number of controllers in those scenes?

3. Is there a pattern (a set) of devices that are common in the failing scenes?

4. Please use the Event Viewer to see what ISY fails on

 

With kind regards,

Michel

 

Running 2.6.4 beta right now, and it takes some time (it did w/ other firmware releases as well) to create/modify scenes, adding and removing devices from scenes etc. and recently, about half of the time my request fails. When tryng to add a device to a scene, I get the system busy progress bar and it goes two or three times taking about 30 seconds each time. While I'm not crazy about the wait, I can easily accept it if it's the norm, but should this be expected?

1) There are no remotelincs in any of the scenes

2) there are no more than 2 controllers in any of the scenes

3) there's no particular pattern of common devices, some of the scenes do have common devices but have the problem w/ other scenes as well

4) I don't know how to make any sense of the event viewer

Zellarman,

 

Please start Event Viewer, try adding something to a scene, and then look for failure messages. These messages will tell you in what part of the process there was a failure and which device caused it.

 

With kind regards,

Michel

 

1) There are no remotelincs in any of the scenes

2) there are no more than 2 controllers in any of the scenes

3) there's no particular pattern of common devices, some of the scenes do have common devices but have the problem w/ other scenes as well

4) I don't know how to make any sense of the event viewer