Bruno, I / we may have nailed it.
Deleted both Shelly1 from the dashboard and the device list and added back in first SHelly1 on IP address 192.168.1.107 using the new inbuilt Shelly WiFi driver.
Within the Device list first device added with a child entity Underfloor 1 Channel 1 is added it to the dashboard and the switch can toggle from both elements.
Added in 2nd Virtual Shelly on 192.168.1.108 but the child entity is not added.
Can you reboot underfloor2 and then click save preference in your Hubitat device? Be sure you are using the correct username and password (if you used it)
No change Bruno, I am writing to support now as I wonder if this comes down to the Shelly WiFi driver chanel setting having been hard coded. Many thanks for your support.
@Evilborg am getting this in the logs for one of my shelly1 switches running the stock driver:
dev:11762020-12-03 06:31:03.274 pm infosendEvent Device FW is current
dev:11762020-12-03 06:31:03.056 pm infoMax power is set to 0 Watts
dev:11762020-12-03 06:31:03.020 pm infoRelayName is null
dev:11762020-12-03 06:31:03.006 pm infoDeviceName is null
dev:172020-12-03 06:31:02.157 pm infoManufacturer Name Received
sys:12020-12-03 06:31:00.771 pm warnReceived data from 192.168.86.5, no matching device found for 192.168.86.5, C0A85605:DB52, B4E62D4A59C8 or C0A85605.
dev:11762020-12-03 06:31:00.679 pm infoCalling /relay/0?turn=off
the only error I see is
sys:12020-12-03 06:31:00.771 pm warnReceived data from 192.168.86.5, no matching device found for 192.168.86.5, C0A85605:DB52, B4E62D4A59C8 or C0A85605
The rest are INFO logs. So what is the device that sys error gave?
Each time the Shelly1 (dev1176) turns on or off I get this system error. The switch does work but I get this error each time? The device that the error is about is the shelly1 @ that IP address
My drivers do not make any call backs... Are you sure you are using MY driver and NOT hubitats? Have you set url actions via the device website?
Yes your driver, 3.0.6 i think. And no I havent set anything like that up
I just tested it here and that version of the driver isn't showing any debugging errors. So re-check everything including the URL actions on that device.
3.0.7 will come out by the weekend for the Shelly Switch Relay driver.
what are URL actions?
That was it, i deleted all the URL's and saved. How did they get there?
If you used the Hubitat built-in drivers prior to mine I believe they are set when the device is added. Mike uses a different approach then I do to get the status of switches.
That would be it then, I deleted and re-added with yours but never thought to go delete the urls
Not your fault as Hubitat doesn't tell the user of this edit.
I moved this thread under the new community apps/drivers section instead of developers.
FYI according to Shelly API documentation: " Shelly devices implement a CoAP-based protocol for monitoring which we call CoIoT."
Do any of the developers have the Shelly Motion Sensor yet? I believe it's to be released in Feb.
Ah, just seen the post in the Facebook thread asking for the docs to build the driver!
Not supported with Hubitat
Don't have it yet and Dimitar hasn't sent me any info on it yet.
I'm using a Shelly PlugS to measure the power usage of other devices - eh, I want to... 
I've tried the available drivers to get a power changed trigger working - without success.
Only when I manually press Refresh on the device page such a trigger will launched.
Has anyone accomplished such task?
Any other ideas (but not using polling)?
Unfortunately the Shelly has no Action URL for Power Changed, as e.g. for Button Pressed, which at least made the refresh of the Switch State possible.
Download the Hubitat app
