In advanced settings I only see IP Address, username and password.
In Settings is section "Plugged In " where i can choise “virtual classes”, their I have “other”.
That’s what I mean.
But what I mean is definined in your driver line 10 “class”: “socket”,:
I’m aware of what you mean but you can override this device class through the device settings as mentioned.
You could try and follow the advanced troubleshooting instructions for Bluetooth devices from the first post. Goal would be to monitor the console of the Bluetooth proxy script to see if the BLE advertisements are received by the Bluetooth proxy.
Great! That already looks much much better. I can now adjust the slat position perfectly!
But what I am still missing is a card in the flows, with which I can set not only the position of the Venetian blind, but also the slat angle.
Tanks a lot for the great support.
You should report that to Athom. This is a default capability and Athom should implement flow cards for that.
Where can I do this?
On GitHub here: Issues · athombv/homey-apps-sdk-issues · GitHub
Or here to Athom support. To be able to actually request this feature to Athom using a form you need to select the “Other …” option and not “App” as this is not an issue with the app but with Homey SDK. The “App” option will divert you to the Github of the Shelly app as Athom is trying to avoid users contacting them.
I’m wrong about this. The always helpful @robertklep pointed out the the device class is not the same as the virtual device class you can select under the device settings. There currently is a new release pending approval but with the release after I’ll change the device class for the Pro 3EM. I’m not sure this will change the behaviour in the energy tab though.
Hello,
I have Shelly Wave 2PM.
Wave 2PM provides precise power consumption monitoring on each channel separately and in total.
“on each channel separately” - not working for me.
I see only total power :frowning 
Maybe I need to change the settings of device?
1 Like
Hello,
Till recently my shelly plug S wall sockets worked fine, but since some days there not working anymore. In the shelly app it does work ok. What I noticed is that the device in Homey gets another IP adres then in the Shelly app. When I change the IP adres to the same IP as in the shelly app it works 5 seconds and than it goes back to the ‘Homey IP adres’. What I noticed is that when I click the on/off button in the shelly app the status in the homey app syncs. So in that direction it’s working (also with the different IP adres). But when I send a command from the Homey app to the wall socked it’s not working. I think it’s something in my network. I have a Deco mesh system and the wall socket is in range 192.168.68.XX and. In the Homey app the wall socket is in the range of 192.168.2.XX. Nothing changed in the network as for as I know, and it worked for months flawless. Can someone please send me in the right direction. Both the Homey and the wall plug have a static IP address.
Could you do two things for me.
First go into the zwave parameters and change the zwave association group from 1.1 to 1 and save. After saving, go back into this settings and change it back to 1.1. Now check if this has fixed your issue. There is a bug in Homey core when settings multichannel association from driver.compose.json to a value of 1.1. Athom is aware but is not giving it priority.
If this does not solve the issue, could you post a screenshot of both channels.
1 Like
What the app does is update the IP address in Homey of the device once it receives a status update for that device (matching is done on device id) and the currently registered IP address does not match the IP address of the received message.
So either the IP address in the Shelly app is incorrect (not synced because cloud is disabled), or there is indeed something wrong with your network where the device is reporting a different IP address in it’s CoAP message or you manually switched the IP address of two or more devices in Homey while the mechanism is changing it back based on the original device id which was saved during pairing. You could try rebooting the plugs or worst case scenario, just remove and re-pair them.
Thanks for your fast reply, really appreciate it. Shelly cloud is enabled. I looked into the log of the Deco X60 and found this:
Edit: found the problem, Deco was not setup as accespoint 
1 Like
I’m on Homey Cloud and of course experiencing the disconnect bug from time to time, quite infrequently and random. Accepting the situation for now hoping that sooner or later it will be solved.
Now, what would be good meanwhile is automatic detection that Homey and Shelly have disconnected.
Anyone developed something for this?
I’m experimenting with this
1: I have a Shelly Plug that I from the Shelly App with a timer generate an on/off pattern, for instance, 00:00-12:00 ON + 12:00-24:00 OFF
2: I have a Homey flow that tests this pattern by reading status of that Shelly Plug
3: If pattern is not matching the expected state a notification is sent to me and I can reinstall the Homey Shelly app
Are there better/smarter solutions?
Maybe developers of Shelly app in the software could detect that connection is lost and expose a test-function in the Homey Shelly app?
I just tried to pair up a Shelly Plus HT via the web Homey Pro 2023 interface, but it fails. Then I tried using the iPhone Homey App and it worked just fine. Is there a difference in the app? Basically the web version didn’t ask for any IP address etc. Thank you
Not from the app point of view. But it seems the WebUI dors behave different sometimes. Having to enter the IP address indicates issues in your network though. Normally Homey would discover the device over mDNS. Apparently Homey is unable to do so. If you are seeing updates from the device you are good for now but it might be something to look at though.
The device is working fine fortunately. Does seem weird though it didn’t auto discover.
