Please, I want to ask you two questions about the modified dth for local execution you mean
- Have you tried it and it works in smart lighting app without internet connection?
- I think you are in the firmware beta program. Have you seen if an automation created with this device with modified dth is marked as local?
I ask you this because as we already mentioned in old private thread, I have Fibaro double switch 2, which I modified the parent DTH to work as a local the main switch and it works perfectly in smart lighting app without internet, but I am not in the beta program to test it with local automations.
I understand your concern about local DTHs, but based on everything I have read in this great community and above all analyzing how devices respond to the changes in DTHs and how they affect their type of execution, I am increasingly convinced that in the Hub firmware there are no DTHs, it executes only the standard capabilities of the devices, switch, motion, contact … standard batttery calculation … and I don’t know if in the future also the custom capabilities that will replace the custom DTHs.
The rest of the code, installed, configure, refresh, methods or custom calculations redirects them to execution in the cloud.
I have all the official smartsense motion, multisensors and fibaro DTHs switches, modified and they still work perfectly locally with samart lighting app.
From my humble point of view, I think this is the easiest way when Samsung wants to use a hub with an economical price, medium performace and capacity and intends to use locally zigbee and zwave devices that are compatible with many manufacturers and also local automations, which do need space to host and run on the hub.
If this was really the way, I think you shouldn’t be so concerned about local DTHs, but since there are no official confirmations …