Persistent Query Window

[sfhutchi]

The persistant 'query' window continues to be an annoyance. I am not sure of the value of continually forcing this to the foreground is. Unless this is a Windows issue, I suggest removing this... or simply adding something to the main console to show that there is activity in progress.

 

As an example, after I upgraded, I queried the system and it took about 4-5 minutes. Not really a big deal because I could switch to other programs on my desktop... Unfortunately, the 'query' window continually closes and then opens another that forces itself to the foreground. Certainly not a show stopper, but annoying nonetheless.

 

*After I first installed 2.4.11 about 20% of my devices could not be communicated to by the ISY. I closed everything and reloaded and then didn't have any problem. Not sure that this is an issue, but thought I would mention it.

[Michel Kohanim]

sfhutchi,

 

You are 100% correct. It's an annoyance for which we have not yet found a cure. It might involve a redesign which we have been postponing since we wanted to get 2.5 out.

 

Now, not being able to communicate with devices is a problem which we have to address. As far as I remember, this is a problem which you've been experiencing intermittently all along, right? If so, would you please let me know the firmware version of your PLM? I think you should upgrade to 52 and use an AccessPoint (not SignaLinc) on top.

 

Thanks and with kind regards,

 

The persistant 'query' window continues to be an annoyance. I am not sure of the value of continually forcing this to the foreground is. Unless this is a Windows issue, I suggest removing this... or simply adding something to the main console to show that there is activity in progress.

 

As an example, after I upgraded, I queried the system and it took about 4-5 minutes. Not really a big deal because I could switch to other programs on my desktop... Unfortunately, the 'query' window continually closes and then opens another that forces itself to the foreground. Certainly not a show stopper, but annoying nonetheless.

 

*After I first installed 2.4.11 about 20% of my devices could not be communicated to by the ISY. I closed everything and reloaded and then didn't have any problem. Not sure that this is an issue, but thought I would mention it.

[sfhutchi]

Yes it is a problem that I had seen in the past, but this was resolved with the Signalinc on top of the PLM. It has been solid since. The current issue appears to be related specifically to 2.4.11. Even devices that don't report as non-communicative can't be controlled by the console.

 

Switching back to 2.4.10 resolved it.

[Chris Jahn]

This is very odd because nothing we added to 2.4.11 should affect device communication. How long were you running 2.4.11?

 

Has anyone else experienced this problem with 2.4.11?

[Mark Sanctuary]

The busy query popup window has going spastic on me too.

 

I thought though that it was my new PLM causing it though because my new PLM must have a much different S/N ratio for Insteon Signals than my old one. Now I am going to have to get an extra devoted Accesspoint just for my PLM. Why can't the PLMs just have the Accesspoint built in? Geese.

 

So this is the only changes I can think of that I have done and now have a spastic busy query popup window.

 

• Upgraded ISY to 2.4.11
  Swapped out my 4a PLM for a 5.2 PLM.

[Michel Kohanim]

Mark,

 

Precisely. The new PLM works at 75% and thus you should expect a lot of communication problems.

 

With kind regards,

Michel

 

The busy query popup window has going spastic on me too.

 

I thought though that it was my new PLM causing it though because my new PLM must have a much different S/N ratio for Insteon Signals than my old one. Now I am going to have to get an extra devoted Accesspoint just for my PLM. Why can't the PLMs just have the Accesspoint built in? Geese.

 

So this is the only changes I can think of that I have done and now have a spastic busy query popup window.

 

Upgraded ISY to 2.4.11
Swapped out my 4a PLM for a 5.2 PLM.

[Mark Sanctuary]

Why at 75%? What is the change for?

[Michel Kohanim]

Hi Mark,

 

I think you should post this question at techmall!

 

With kind regards,

Michel

 

Why at 75%? What is the change for?

[Mark Sanctuary]

Hee hee, ok I get it.

[sfhutchi]

This is very odd because nothing we added to 2.4.11 should affect device communication. How long were you running 2.4.11?

 

Has anyone else experienced this problem with 2.4.11?

 

I only ran it for less than 2 days. I will upgrade to 2.4.12 and see if there is anything. Possibly my PLM was on the fritz also.