[ST Edge] Issues with infoChanged lifecycle

Developer Programs Writing Edge Drivers
1

on the v 0.40

  • info_changed event stopped working for zigbee devices
local function info_changed(driver, device, event, args)
    log.info("info changed: " .. tostring(event)) << never appears
    ...
end 

lifecycle_handlers = {
        infoChanged = info_changed,
    },
  • when the driver is reloaded, the init function runs with an empty [] device object. so device: get_model () == nil and all vendor-specific logic doesn’t work until the hub is restarted.
2

I saw this last Thursday and I mentioned it to @nayelyz.
The subdrivers don’t work because of this.

3

Hi, @veonua.
I’ve been making some tests and I receive the info_changed event correctly on my driver for a Zigbee device.
I even included the line you shared and this was the result:

--log in driver's code
log.info("info changed: " .. tostring(event))

--result
info changed: infoChanged

Do you mean by “reloaded” when you package, publish and install the driver again (without deleting the previous version) because the infoChanged is called?

Remember that this is a beta version, so it could be some inconsistencies.
Have you tried deleting your device and the driver completely and package, publish and installing it again?

4

Have you tried deleting your device and the driver completely and package, publish and installing it again?

unfortunately, it’s much slower than just rebooting the hub. the idea is to reload the code fast

5

it used to work with the previous firmware. I’ll try to debug this further

6

You can, it’s just in this cases where there are no apparent issues but the driver is not showing the expected behavior.
If deleting completely the driver and installing it again doesn’t solve the issue, we need a further analysis.