Dimmer feedback & patch

Attaching a Sensor dimmer to a channel only associates that dimmers' information with that channel.  It does not automatically record loads.  If you want to record loads, that needs to be done through DimStat. 

That sentence says that the red '!' will be displayed to indicate that a dimmer has an error; such as Overtemp or Breaker Trip or No Load or Load Low, etc. 

I totally understand. The manual says on the bottom of page 110 lamp out. What does it mean by that? 

Also I just finished labeling names in dimstat. Saved & sent config. To devices.  Why does my label on the EOS in patch still read "Dimmer 351[D-Cat_351]? How can I delete Dimmer 351 & have just what I labeled? D-Cat_351

In addition , some labels are not reading at all what's in dimstat. 

Doesn't seem like the labeling is consistent .

Also I just finished labeling names in dimstat. Saved & sent config. To devices.  Why does my label on the EOS in patch still read "Dimmer 351[D-Cat_351]? How can I delete Dimmer 351 & have just what I labeled? D-Cat_351

In addition , some labels are not reading at all what's in dimstat. 

Doesn't seem like the labeling is consistent .

The Lamp Out is actually an incorrect way of stating AF Load Low.  There is no Lamp Out error state in CEM or Eos. 

If you label a CEM dimmer using SensorConnect or DimStat, Eos will put that label in brackets when you attach the dimmer to a channel.  In your example, the "Dimmer 351" is a label that you entered in Eos.  We allow users to put their own label for that dimmer in Patch and also see the dimmer name that is part of the CEM config.

If you don't want "Dimmer 351", delete the label from that channel in Eos.  The existing label will still be in brackets though to designate it is the dimmers name retrieved through feedback.

I personally don't use DimStat and do all of my configuration using SensorConnect.  I would double check that all of the label changes you made in DimStat have been correctly sent to the CEM config.  Eos will only show the information that is sent from the CEM.  If there is a discrepency between DimStat and the CEM, Eos will get what the CEM has and not what DimStat thinks it has.