Jan Iven

* the AFS 'kernel upcall' (ioctl) is done either via an executable (`aklog`, `afs5log`) or integrated into a library (there are different flavours of `pam_krb5.so`, some with AFS support..). *...

* each pam_session will get a separate Kerberos credential cache and AFS "process group" (PAG, i.e that thing that shares the AFS token). * passing a Kerberos ticket between sessions...

@KPfff: many thanks for this investigation. I guess that part of the issue is that not everybody is using `zigbee2mqtt`. To convert your findings to a `zha-device-handlers` "quirk" means writing...

Work-in-progress "quirk": * gets loaded, * Zigbee "manage device" sees the custom cluster, * **but** does not load any data ( all values are null) * even for stuff like...

I had a look but am stuck, no idea whether the "attributes" from @KPfff have been correctly put in place in this code, or whether something basic is missing (this...

Attached is a new version of the "quirk" (apparently need some offset to "translate" attributes numbers between zigbee2mqtt and ZHA), as usual need to rename to `something.py` (but cannot upload...

> Hi, I tested a new script, Reconfiguring device,  But again it doesn't show me the entities... @robertstumberger : this is not so bad, the device has been recognized...

As you've seen, the `Tuya_EnergyMeter_2Clamp` class "knows" how to read the interesting attributes from the device (based on the work by @KPfff ). It then stuffs data into two helper...

Here is a new version that has both clamps individually (as well as the total) [ts0601_sp_clamp_power.py.v2.txt](https://github.com/zigpy/zha-device-handlers/files/13626919/ts0601_sp_clamp_power.py.v2.txt) However, I haven't yet found a way to give them different entity names (so...

@robertstumberger - thanks for the test. Could you edit the "quirk" and change ` t.uint16_t` to `t.int16s` in the following? ``` 62 TOTAL_POWER_AB_ATTR: ("power_both", t.uint16_t, True), 63 TOTAL_POWER_A_ATTR: ("power_A", t.uint16_t,...