When adding new device take a long time, as I see it is updating all the open/close sensors it there a setting?

[mjohnson007]

Running :

Firware - Insteon_UD994 v.5.3.0 (2020-10-01-14:39:56)

UI - - Insteon_UD994 v.5.3.0 (2020-10-01-14:39:56)

When adding new device take a long time, as I see it is updating all the open/close sensors also, is this as planed or is something configured wrong.

I have 3 open close sensors and it seems evertime I try and add a new device it also seems to be writig to them also 

so it writes to all of the following wich makes it extreemly slow:

Sensor-Heartbeat

Sensor-closed

Sensor-opened

 

is there a setting to not update them and do only whe on that device

 

Thanks

Edited July 24, 2021 by mjohnson007

[MrBill]

the bug you are encountering was fixed in 5.3.2... don't stop there tho, upgrade to 5.3.3

After you upgrade you will need to wake up all your wireless sensors (press the set button until the LED starts blinking) and get the cached desire to write taken care of (right click the device in the tree and select "write updates to device").  when complete the green 1011 icon will disappear on those wireless nodes. 

[mjohnson007]

Thasnks for the quick respons, I though I was loosing my mind

I will do a backup, then upgrade 

Thanks again

[mjohnson007]

Can I ask another quick question, after I add a new device and want to set the On Level and Ramp rate it doesnt seem to do it directly to the device, I have tried right clicking and select  Now if I add to device to a scene it allows me to update by selecting the update button on the right side of the page , if I remember older versions would write the changes as soon as a value in the dropdowns was changed

[MrBill]

1 hour ago, mjohnson007 said:

Can I ask another quick question, after I add a new device and want to set the On Level and Ramp rate it doesnt seem to do it directly to the device, I have tried right clicking and select  Now if I add to device to a scene it allows me to update by selecting the update button on the right side of the page , if I remember older versions would write the changes as soon as a value in the dropdowns was changed

The answer is not intuitive.  set the dropdown, then push the button to the left of the dropdown. 

On, Beep, On Level, Ramp Rate, and Backlight are buttons.

there is an unfixed bug around backlight.  You can set the backlight by setting the dropdown and hitting the backlight button, the change will be sent to the device.  but you can't trust what the dropdown says without setting.  after admin console is restarted it will say 0 again... it's not.  After you set one device that setting will appear to be be carried forward to the next device... that's a lie.  the dropdown and button work reliably, but there is no way to tell what the setting in the actual device is.

[Teken]

The answer is not intuitive.  set the dropdown, then push the button to the left of the dropdown. 

On, Beep, On Level, Ramp Rate, and Backlight are buttons.
there is an unfixed bug around backlight.  You can set the backlight by setting the dropdown and hitting the backlight button, the change will be sent to the device.  but you can't trust what the dropdown says without setting.  after admin console is restarted it will say 0 again... it's not.  After you set one device that setting will appear to be be carried forward to the next device... that's a lie.  the dropdown and button work reliably, but there is no way to tell what the setting in the actual device is.

To be clear on one point unless something has since changed. Any hardwired device can be queried and settings will be updated in the AC. A battery device will not unless placed in learning mode. Regardless, all known states will be lost during a reboot / loss of power.

Hence why the system offers the 3AM Query All to obtain a snap shot of the current status & user defined settings. The same can be done if the heart beat is used to send updates to a battery only device.

This feature works on some devices and is definitely a YMMV!

[MrBill]

35 minutes ago, Teken said:

To be clear on one point unless something has since changed. Any hardwired device can be queried and settings will be updated in the AC. A battery device will not unless placed in learning mode. Regardless, all known states will be lost during a reboot / loss of power.

Hence why the system offers the 3AM Query All to obtain a snap shot of the current status & user defined settings. The same can be done if the heart beat is used to send updates to a battery only device.

This feature works on some devices and is definitely a YMMV!

To be clear, no wireless devices are being discussed here. 

Point 1 is that is NOT intuitive to set the dropdown then press a button to the left of the dropdown to SET the value.

Point 2 is that "backlight" does not correctly "default" the dropdown to the value stored in the device.  If the admin console was started before arriving on this node it will say 0 "zero" regardless of what is stored in the device, it will NOT fix the the value displayed in the admin console if the device is queried.   If we CHANGE the value in the dropdown to an odd value say 24%, then move to a DIFFERENT Device, the dropdown box will be populated not with 0 but with 24%.  This is an admin console bug.   The dropdown does however work correctly for SENDING a value to the DEVICE, which will be retained by the device once it is sent, regardless of what the admin console subsequently says.  All switches with a BACKLIGHT are wired, this has nothing to do with not being able to query a wireless device.

[Teken]

To be clear, no wireless devices are being discussed here. 
Point 1 is that is NOT intuitive to set the dropdown then press a button to the left of the dropdown to SET the value.
Point 2 is that "backlight" does not correctly "default" the dropdown to the value stored in the device.  If the admin console was started before arriving on this node it will say 0 "zero" regardless of what is stored in the device, it will NOT fix the the value displayed in the admin console if the device is queried.   If we CHANGE the value in the dropdown to an odd value say 24%, then move to a DIFFERENT Device, the dropdown box will be populated not with 0 but with 24%.  This is an admin console bug.   The dropdown does however work correctly for SENDING a value to the DEVICE, which will be retained by the device once it is sent, regardless of what the admin console subsequently says.  All switches with a BACKLIGHT are wired, this has nothing to do with not being able to query a wireless device.

Yes, both issues you stated are true. My reply was to provide insight about how the current state could / would be obtained. Again YMMV as it pertains to using the heart beat to query the current status. As this is highly dependent upon the device, firmware, and strength of the Insteon RF mesh!

[MrBill]

7 minutes ago, Teken said:

Yes, both issues you stated are true. My reply was to provide insight about how the current state could / would be obtained. Again YMMV as it pertains to using the heart beat to query the current status. As this is highly dependent upon the device, firmware, and strength of the Insteon RF mesh!

To be clear, again, there is no queries, or wireless devices, or heartbeats being discussed in my reply to the poster that asked the question.  You are bringing up confusing points that have no bearing on the question that was asked.

[Teken]

To be clear, again, there is no queries, or wireless devices, or heartbeats being discussed in my reply to the poster that asked the question.  You are bringing up confusing points that have no bearing on the question that was asked.

Once again my reply was to offer more insight and feedback as it pertains to current status!

The initial thread pertains to a BATTERY operated device. The OP also inquired about STATUS. I simply added to your comments to provide MORE information which any reasonable person would understand.

Given the high intellect in this forum I am not worried about confusion anyone because I’m sure they can Read, Understand, and Apply the information if and when it’s needed!

If it doesn’t apply they can surely ignore the same and carry on with life!

I don’t think my point can be made any clearer on the topic at hand?!?

[MrBill]

3 minutes ago, Teken said:

The initial thread pertains to a BATTERY operated device.

You quoted the wrong message in your initial reply then.  The message that you quoted of mine was answering the OP's follow up question, which has nothing to do with what you are "chiming in with".  But again, your "clarifying comments" are not really pertinent to the "device writes" bug that existed nearly 2 years and was finally fixed in v5.3.2 which is the initial question by the OP.