Hi!
Got this really strange issue since a month or so.
Adding any Fibaro device to a scene crashes the Classic app, same thing if I try to edit a scene with a Fibaro device. Adding the same device to a scene in the new app doesn’t crash the app but the one/off settings is blank and no matter which I chose nothing happens.
Tried both custom and ST provided DH…
@JB_Bentz@Thyg0d what Fibaro devices exhibit this problem and what DTH are you using? If it’s a custom DTH, does it contain the code addChildDevice? If it does, and one of the parameters is isComponent=false can you try removing the code that sets componentName, deleting the device and joining it again? This PR has an example of the change I’m suggesting:
This has been a problem for a very long time. I’ve submitted a support request for it (developer support I think). It happens with any child device that was created with “isComponent:false” I believe.
Same issue here with scenes crashing the app when i include fibaro or qubino child devices. I’m using the default Qubino device handler and Eric’s great device handler for the Fibaro. Any solution tried and confirmed ?
Hi @Fab…
Yeah, sort of…
But you probably won’t like it, I didn’t enjoy it anyway…
I got my 223 to work by removing them all, removing Eric’s DH , adding the devices using the new app.
This sorted the crashing issue in the old app and you can now create scenes with the Fibaro 223 devices using the old app. You can also control each device manually in the new app.
Downside, if you add the 223’s to a scene in the new app it doesn’t work and since you’ve edited the scene in the new app you can never edit it in the old app ever again.
I my case I need to create some 40 new scenes, 20+ routines and a bunch of “Smart Lightning” routines and of course SMH settings.
Now I’ve got even more issues…
Smart lighting automations are loosing their name saying no devices or scenes have been selected but when I check the automation it shows devices selected…