I’m aware. I already have this device in my possession for about two months.
It’s a bug to newer firmware making changes. I’ll fix this with the next release.
Thanks for analysing the issue! I will wait for the next release.
Breaking change release 3.29.4
Release 3.29.4 has removed all drivers that have been deprecated for almost two years now. Devices still using these drivers will stop functioning within Homey if they aren’t re-paired.
Background story
In August 2022 a generic Shelly WiFi device driver was introduced which replaced all device specific device drivers. This was done to accommodate the ever growing Shelly eco system and making the app more manageable and therefor future proof. The device specific drivers where deprecated at that point in time as well. It was communicated that, for the time being these deprecated drivers would continue to function, but it was recommended to re-pair your devices with the generic driver as these device specific drivers weren’t maintained anymore. Some less used drivers have been removed since then but the time has come to remove them all because errors are occurring due to these unmaintained drivers.
I’m aware there is still a small user base that have missed or ignored all previous communication and is still using deprecated drivers. But extending the grace periode for even longer than the current 1,5 years will probably not help either. A phased approach with initial timeline warnings and disabling status updates will hopefully get the attention of at least a part of this user base.
Reacting would be easier if the new driver worked with my Shelly4Pro.
Neither With CoAP or without the new driver will connect.
FW is latest 20201019-110845/v1.6.6_4Pro@bad181e4
The app finds the Shelly4Pro every time without problem
Without Password I get the message Device does not support unicast.
If I setup a password It does not ask for a password and just tells me error 404 and wrong password.
Wireshark tells me:
192.168.87.15 224.0.1.187 CoAP 235 NON, MID:25810, Unknown 30, /cit/s
So Unicast should be working on the shelly side. But no local message from Homey.
I restarted the Shelly and Homey multiple times.
Step 7 from your Pairing instructions never happens any ideas ?
Hello,
I’ve just started to use Homey Pro in conjunction with Shelly Wave devices.
For my energy saving home automation application I would like to automate lights and shades.
The Idea is to open the shades if it is past sunrise and lights will be turned turned on. After opening lights should be turned off.
Only issue is the Shelly Wave Shutter does not offer an “if” flow card with the position state nor offer a “and” with the position. The Shelly support told me that there are commands what could be implemented.
Is there a possibility to add those commands in the flow cards?
Things would be easier for me if users would just read and follow instructions 
This is not the latest firmware and the cause of your issue. The instructions tell you to enable cloud connection before checking the firmware version. You will find out it’s outdated.
There is a trigger card called Position changed with a token that holds the position as a percentage. You can use that token in a condition card to validate stuff and decide which actions need to be performed. Nothing needs to be implemented for this in the Shelly app.
Well for the Original 2018 Shelly4pro it is the latest. According to all sources I found. It is the “SHSW-44”
And the only setting I can change is CoIOT enable or disabled.
It is connected to the cloud. As I am able to read.
I would also like a FW update and would love to get that ancient FW disconected from the cloud as son as possible who knows what bugs are in that FW.
I also was thinking of going to find an alternate FW but the Shelly4pro is not ESP based.
I enabled the cloud and a new firmware appeared, and it did the trick. Many thanks
Ah yes, that device was discontinued and that outdated firmware probably doesnt support unicast if there is only an enable / disable CoIoT setting. That indeed does not work at the moment. I will have to see if I can find a workaround for these deprecated devices. Could you post the output of http://yourshellyip/settings using a code block.
Today my Shelly plug S stopped working whit my Homey pro early 2019. The Shelly plug S got the latest firmware and I can connect to it in my webbrowser. Is this device obsolete for Homey Shelly app? Firmware info(The current Firmware version of your Shelly device is 20190516-073020/master@ea1b23db No newer firmware available.) Regards Peter
Probably related to using a driver that has been deprecated for almost two years. Read this post.
New firmware (3.29.4) solved the issue. Thanks!
It does Send some sort of unicast like I wrote above.
Some CoAP packets to an unkown adress in unicast IP space
224.0.1.187
Here some outputs Passwords, lat & lng, and network names have been modyfied.
/cit Gives no output
/debug Gives no output
Here Is the output of /settings
{"device":{"type":"SHSW-44","mac":"780473F64411","hostname":"shelly4pro-F64411","num_outputs":4, "num_meters":4, "num_rollers":0},"wifi_ap":{"enabled":false,"ssid":"shelly4pro-F64411","key":""},"wifi_sta":{"enabled":true,"ssid":"Example","ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"wifi_sta1":{"enabled":false,"ssid":null,"ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"mqtt": {"enable":false,"server":"192.168.87.20:1883","user":"tux","reconnect_timeout_max":60.000000,"reconnect_timeout_min":2.000000,"clean_session":true,"keep_alive":60,"will_topic":"shellies/shelly4pro","will_message":"True","max_qos":0,"retain":true,"update_period":30},"sntp": {"server":"time.google.com"},"login":{"enabled":false,"unprotected":false,"username":"admin","password":"0000"},"pin_code":"","coiot_execute_enable":true,"name":"","fw":"20201019-110845/v1.6.6_4Pro@bad181e4","build_info":{"build_id":"20201019-110845/v1.6.6_4Pro@bad181e4","build_timestamp":"2020-10-19T11:08:45Z","build_version":"1.0"},"cloud":{"enabled":true,"connected":true},"timezone":"Europe/Berlin","lat":40.129902,"lng":10.548000,"tzautodetect":true,"time":"19:23","hwinfo":{"hw_revision":"prod-2018-12","batch_id":6},"lat":40.129902,"lng":0.548000,"relays":[{"name":null,"ison":false,"has_timer":false,"overpower":false,"default_state":"last","btn_type":"momentary","auto_on":0.00,"auto_off":150.00,"max_power":2300,"schedule":false,"schedule_rules":[]},{"name":null,"ison":false,"has_timer":false,"overpower":false,"default_state":"off","btn_type":"toggle","auto_on":0.00,"auto_off":0.00,"max_power":2300,"schedule":false,"schedule_rules":[]},{"name":null,"ison":false,"has_timer":false,"overpower":false,"default_state":"off","btn_type":"momentary","auto_on":0.00,"auto_off":0.00,"max_power":2300,"schedule":false,"schedule_rules":[]},{"name":null,"ison":false,"has_timer":false,"overpower":false,"default_state":"off","btn_type":"momentary","auto_on":0.00,"auto_off":0.00,"max_power":2300,"schedule":false,"schedule_rules":[]}],"meters":[{"power":0.0,"is_valid":true,"timestamp":1715023398,"counters":[0.000, 0.000, 0.000],"total":0},{"power":0.0,"is_valid":true,"timestamp":1715023398,"counters":[0.000, 0.000, 0.000],"total":0},{"power":0.0,"is_valid":true,"timestamp":1715023398,"counters":[0.000, 0.000, 0.000],"total":0},{"power":0.0,"is_valid":true,"timestamp":1715023398,"counters":[0.000, 0.000, 0.000],"total":0}]}
Output of /Status
{"wifi_sta":{"connected":true,"ssid":"Example","ip":"192.168.87.15","rssi":-56},"cloud":{"enabled":true,"connected":true},"mqtt":{"connected":false},"time":"19:31","serial":1,"has_update":false,"mac":"780473F64411","relays":[{"ison":false,"has_timer":false,"overpower":false,"is_valid":true},{"ison":false,"has_timer":false,"overpower":false,"is_valid":true},{"ison":false,"has_timer":false,"overpower":false,"is_valid":true},{"ison":false,"has_timer":false,"overpower":false,"is_valid":true}],"meters":[{"power":0.0,"is_valid":true,"timestamp":1715023911,"counters":[0.000, 0.000, 0.000],"total":0},{"power":0.0,"is_valid":true,"timestamp":1715023911,"counters":[0.000, 0.000, 0.000],"total":0},{"power":0.0,"is_valid":true,"timestamp":1715023911,"counters":[0.000, 0.000, 0.000],"total":0},{"power":0.0,"is_valid":true,"timestamp":1715023911,"counters":[0.000, 0.000, 0.000],"total":0}],"inputs":[{"input":0},{"input":0},{"input":0},{"input":0}],"update":{"status":"idle","has_update":false,"new_version":"20201019-110845/v1.6.6_4Pro@bad181e4","old_version":"20201019-110845/v1.6.6_4Pro@bad181e4"},"ram_total":47372,"ram_free":18564,"fs_size":83081,"fs_free":19327,"uptime":49574}
Thanks for your Support.
I get why you direct to your troubleshooting guide as otherwise you drown in nuisance complains.
There is no API documentation available for this old firmware anymore so I need to guess the proper command. Could you test if these requests update the coiot setting?
http://192.168.87.15/settings?coiot_execute_enable=false // disabled it
http://192.168.87.15/settings?coiot_execute_enable=true // enable it
Yes It does change the setting.
https://web.archive.org/web/20201228214935/https://shelly-api-docs.shelly.cloud/#shelly4pro
CoIOT seems to be startet in firmware but never has been implemented as other devices have a description and acess to /cit/d and /cit/s
Hy all,
I have a problem with Shelly Plus i4 DC. It looses the server adress for outbound websocket setting occasionally, so I can’t rely on it.
It happens without power failure, WiFi connection is good, latest firmware.
Thx for reply
Thanks for the hint. That worked well in my application.
Did you reboot the device after enabling? It needs a reboot to become active.
Do you have the device connected to any other integration than Homey. Perhaps that is overwriting the settings. And does the device and Homey both have a static IP’s assigned?
