Please try to get a definitive answer from ActionTiles as to when they are going to fix their application to fully support SmartThings devices. There’s no sense going back and forth with them about one particular component or capability.
I’m still not enthusiastic about designing device profiles to account for ActionTile’s shortcomings.
I write it here @TAustin To give feedback :I had to unplug 1 Shelly 1pm for a few days, to redo some wiring. The Shelly app obviously recognized it as offline, from SmartThings obviously not. I don’t know if he tried reconnecting all these days, but now that I reconnected it, it immediately didn’t work, but after 10 minutes it was back to work. Without having to restart the Hub. Great
after a long time I got a reply from actiontiles. the answer is: they have only migrated “main” so far, if there are any other components, they will not work. according to the statement, they don’t even know when or if it will be supported at all, the new platform is completely different and I have the feeling that more things don’t work there. when I read various discussions, there are a lot of problems after the migration, but it is uncertain whether they will be able to solve some of them.
that’s why I would like to ask you if you could convert the controller to UNI shells, at least so that there is a switch, sensor 1 and ADCS (relay1, temperature, humidity, volatge) in the main, otherwise it is not such a priority for me. other components can be used in automation, but it would be good to be able to display these things in one place.
and one more design change comes to my mind, so that it would be possible (since it is a universal device) in smarthings to choose how to display me (switch, temperature, humidity, volatage) and accordingly the device would be displayed in smarthings with the value of the selected sensor.
you have this functionality in one of your drivers - MQTT device creator
Thanks again for the Gen2 driver logs. I had a couple things to fix and have pushed out an updated driver, version 2023-01-19T02:11:42.535636275.
There was a bug that was preventing button events from getting processed correctly.
I also fixed some code that prevented you from initializing a device that you created manually, with a configured IP address. That should now work ok. Although I would like to address the reason WHY you had to manually create a device: you said one of your devices was not being discovered. Did you try more than once?
EDIT: One more thing: I had inadvertently included an ethernet component on the I4 device, so I removed it now. So please delete your I4 devices and rediscover or manually recreate them once you have this new driver.
Found 10 Shelly Gen2 devices - but only 1 I4. I waited for some time, but didn’t try again automatically.
Because I just wanted to test I4, I removed all the other 9 Shelly Gen2 devices.
Started CLI log to test I4… What a mess… Logs with “BUG” and “Warning” running non stop, because of the deleted devices. No way to test I4 like that.
Removed all the devices. Uninstall the driver. Install the driver again. Checked CLI log, and now was all ok… CLI just waiting to record something.
Start automatic discovery again.
This time, just found 1 Shelly Gen2 devices. The I4 that was not found in the 1st place. All the other ones I think just ignored them. Ok for me at this time.
So I tried to add manually the other I4, that was added automatically at the first time, but not now.
And then I started the test, that I sent to you. I hope you understood…
In my opinion, the automatic add of the devices is amazing, when the driver is ready and not on test phase, so you can add all at once. But when we are testing we want to check one by one, and we should add the devices manually only.
Now, I will start testing with the update you sent.
Test results on Shelly Gen2 Device Driver - version 2023-01-19T02:11:42.535636275:
Because I had some time, I made tests with I4 and also 1 PM+.
I started the automatic search for 3 times, and all the times some devices were added. I didn’t try more even knowing that there were more Shelly GEN2 devices to add. [Logs - https://we.tl/t-1aiv9CU4Mm - Not possible by message, too much caracters ]
The 2 devices I have were added automatically
They are working perfectly.
Graphically on Smartthings we can see everytime the button is pressed.
The ones added automatically are working perfectly. With interactions and energy information. All good.
One that I add manually is not at 100%:
– Interaction is ok. Can turn ON and OFF the light.
– Don’t give any info of the device. Energy and the others.
– Don’t appear in the bottom the network info, as the ones added automatically.
– [Logs - [Sent by message - Shelly Gen2 Device Driver - Shelly 1PM Plus (Add 1PM+ manually.) ]
Using CLI with this driver now, to check the logs, even without any interaction, there is logs all the time.
Is that normal, or there is something wrong? [Logs - [Sent by message - Shelly Gen2 Device Driver - Logging without any changes]