Ugh me either, ST hates me this week haha. I wanted to use the switch child device but the July 14th, 2020 commit on github (history here) has a
comment that mentions “Changing how child devices are created to work with new app”. So I wasn’t sure if I should exclude the switch child device DTH or not.
Good question!! From within the ST IDE > My Devices > the manually created device, this is the device network ID (below):
Which looked odd, so I removed and re-created the device and attempted the auto discovery this time. It worked (no idea why it’s working sometimes and not others). Now the device has the actual MAC address for the device network ID. Also further down under ‘Data’ it now shows the mac address along with the IP and port, but it wasn’t showing the mac address there previously.
Now it’s not giving me the network error, but the controller won’t actually turn the LEDs on from within ST. It works normally from the controller web interface. Here is the log data:
I’m no developer, but it looks like the controller is responding with a ‘null’ value. Maybe it’s the PIN assignments or something? I didn’t change those for the H801 device. Do these look correct?
(Combining with my other reply from below and deleting to clean up my communication)
Edit 2: OK so this is even more strange. If I manually turn “ON” the LEDs from within the H801 controller’s web interface, this change shows up within the ST mobile app, which is great. So it appears to be communicating correctly. And THEN I can turn the LED lights “OFF” from within the ST mobile app and it works. BUT! HAHA! I then can’t turn them back “ON” from the ST mobile app. Strange right?!
Edit 3: Well folks I have NO IDEA what was/is going on, but after cycling between rebooting the hub, rebooting the controller, removing/re-adding the SmartApp and DTH, etc this silly thing is FINALLY working. To everyone who has helped out and provided time/effort to this project in general, I just want to say: