Remember State when losing power

sirhc · January 6, 2022, 1:13pm

Hey!

Is there a way to tell a bulb to remember the last state after power loss for eg osram bulbs in zha?

It is possible in zigbee2mqtt (LEDVANCE 4058075208360 control via MQTT | Zigbee2MQTT for example)

Thanks a lot.
Greetings

le_top · January 6, 2022, 1:32pm

My method is to lookup the responsible code:

github.com

Koenkk/zigbee-herdsman-converters/blob/38f9a4c773ab31439876006f44fa49d5473324c3/converters/toZigbee.js#L2319..L2324

    
      
          ledvance_commands: {
              /* deprectated osram_*/
              key: ['set_transition', 'remember_state', 'osram_set_transition', 'osram_remember_state'],
              convertSet: async (entity, key, value, meta) => {
                  if (key === 'osram_set_transition' || key === 'set_transition') {
                      if (value) {
                          const transition = (value > 1) ? (Math.round((value * 2).toFixed(1)) / 2).toFixed(1) * 10 : 1;
                          const payload = {0x0012: {value: transition, type: 0x21}, 0x0013: {value: transition, type: 0x21}};
                          await entity.write('genLevelCtrl', payload);
                      }
                  } else if (key == 'osram_remember_state' || key == 'remember_state') {
                      if (value === true) {
                          await entity.command('manuSpecificOsram', 'saveStartupParams', {}, manufacturerOptions.osram);
                      } else if (value === false) {
                          await entity.command('manuSpecificOsram', 'resetStartupParams', {}, manufacturerOptions.osram);
                      }
                  }
              },
          },
          lidl_watering_timer: {
              key: ['timer'],

Leading to the code:

github.com

Koenkk/zigbee-herdsman/blob/8abf23aa0437c53c3d0ba32da276732dce173948/src/zcl/definition/cluster.ts#L3872..L3895

    
      
              commands: {
                  cmd0: {
                      ID: 0,
                      parameters: [
                      ],
                  },
              },
              commandsResponse: {
              },
          },
          manuSpecificOsram: {
              ID: 64527,
              attributes: {
              },
              commands: {
                  saveStartupParams: {
                      ID: 1,
                      parameters: [
                      ],
                  },
                  resetStartupParams: {

Which I think means that these are manufacturer specific commands.

You can try my newly implemented Cluster command in my fork of zha_custom .

sirhc · January 6, 2022, 2:17pm

Thank you. Seems that i have to read more about your addon to figure out what the cluster message needs to look like for my command😁

NathanCu · January 6, 2022, 3:12pm

First you need to determine if your device CAN do this. Just because Z2MqTT can do something doesn’t mean the device supports it.

Osram bulbs for instance - I know for a FACT that older ones don’t, (I used to run Osrams as my bulb of choice) a few years ago it was a tossup - depending on firmware, and newer ones do.

If the bulb, doesn’t you can always build a DIY ‘canary’ solution to determine if you had an unexpected power cut, go look up the last known state of the bulbs and reapply it but that gets messy fast.

So before you go down that path - research your bulbs by MODEL and firmware revision to determine if you can first.

le_top · January 6, 2022, 3:36pm

It’s a command without parameters, so it should be something like:

service: zha_custom.execute
data:
  ieee: 5c:02:72:ff:fe:92:c2:5d # The Id of the devce
  command: zcl_cmd
  extra:
    cmd: 1 # The ID of the command
    cluster: 64527 # I suppose that the ID in the zigbee2mqtt definition is the cluster id.
    endpoint: 1 # Not sure, you need to check the device details to find the ID.
    manf:  0x1189 # You can check this in the device details

You can first check if your device supports this or just send the command and verify in practice.
As your bulb is powered, there should be be an issue in receiving the command (it’s always awake).

Personnally I’ld test: the device is from the same manufacturer and it’s likely that their manufacturer commands are consistent accross models (even if not all support them).