The last issue is related to bad zwave range. Try adding more routers between Homey and the shutter. It could also explain why changes from the physical button aren’t reflected in Homey.
Could someone with this device confirm that it does update in Homey when using physical buttons. I can’t test this myself as I do not have this device and do not have any shutters.
So even if the module is 1.5m away from the Homey, such issues can still occur? Currently, I’m testing devices to see which ones perform best.
Apparently. The error is TRANSMIT_COMPLETE_NO_ACK. It’s a common error, do a search here on the forum and you will see numerous reports about it. It’s often suggested to reboot Homey.
Then again, I dont use Homey myself and am by no means a Zwave expert. The only thing I know is that there are currently no other users reporting about these issues as of yet.
Hi! I have integrated shelly z-wave in homey pro. In advanced settings I put that in venetian mode, because I need to control also my slats position, but nothing changes. I have the same sliding control for the roller, but nothing for the slats. The tooltip says that I should remove the device and then add it without reset. But how is it possible to do that? Could you give me some help to make it works, please?
Un-pair and re-pair the device without doing a full reset. Check the instructions on how to exclude it. And make sure you calibrate the device from the maintenance actions after having re-paired it.
Hi, thank you but what I don’t find anywhere is exactly the instructions you refer to. It is possible to you paste here a link? Please, I am really struggling here.
Shelly app v. 3.28.2
Homey Pro v.10.3.4
The instructions for excluding / unpairing and re-pairing are in the device manual. The option for calibrating the device can be found in the Homey app under the device settings > maintenance actions which are accessed through the cogwheel in the top right corner of the device view.
Release 3.29.x will remove 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. Your timeline will show the Shelly devices that are still using a deprecated driver and which require your attention.
Release 3.29.0 is the first step in completely removing these drivers as it has disables status updates for devices that are still using these drivers.
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.
I’ve got a few Shelly Door Window 2 devices set up in Homey (using Homey Pro 2019) that are giving me some issues. Everything is working fine 95% of the time and Homey is displaying the correct status of each door (Opened/Closed).
But every once in a while, Homey seem to miss a status update from Shelly and incorrectly display that a door is still open, when it’s actually been closed. The Shelly app (as in the iPhone Shelly app) always seem to display the correct status and looking at the log in the Shelly app for a specific device, it correctly displays that it was opened and later closed.
From what I can tell by looking at the logs in the Shelly app, it seems that sometimes the open/close updates have the exact same timestamp, down to the same second. The order seems correct, but it’s a bit weird and unlikely that the events occurred at the same time. That said, I can also find examples where the events didn’t occur at the same time, but the close update still wasn’t picked up by Homey.
Everything is on dedicated ip:s and I got excellent wifi coverage.
New to the forums (and to Homey), but I’ve tried to search and look around to see if there are any matching issues reported by others. If this has been reported and resolved before, please point me in the right direction.
Any clues what might be causing this? Is it a Door Window 2 device issue, Shelly issue or Homey issue?
Battery powered wifi devices only report their status on an event and sleep most of the time. When an event occurs it will wake up and first update the Shelly Cloud status of the device and afterwards send updates to third party integrations like Homey. It seems it sometimes happens the device goes back to sleep before having send the status to Homey, probably when a status update to the cloud is taking longer than expected. Disabling the cloud connection on the device could be a workaround.
Thank your reply and that sounds like a plausible explanation. Makes sense.
A device setting to increase the time the device is awake each time would have been nice, but I guess you can’t have it all. Perhaps some future Shelly firmware update could help resolve this issue.
I might be wrong but I think that the new BLU sensors work differently. For example the Shelly D/W BLU. It uses one plus/pro Shelly device for the Shelly cloud connection and another one for Homey.
I did have some issues with the device in the beginning though and the setup was cumbersome. Eventually it turned out that the root cause of the problems was a completely other device by another vendor that was faulty and congested the Homey’s BLE stack.
Yes, those work a little differently as there is no direct cloud connection. I edited my post to specify that’s about WiFi devices (in answer to a question about a wifi device).
An additional question regarding this came to mind. If the Door Window 2 (battery powered wifi device) wakes up due to vibration or change in lightning (if that has been set as active), would that also trigger an update to Homey that includes the latest status of opened/closed as well? Or will that update just contain the status of vibration or lightning?
If all updates sent from Shelly to Homey contains all current statuses of the device, perhaps I could just enable more triggers on the device to make it wake up more often and try to send updates to Homey?
The Shelly Plus AddOn does not report the change in temperature sensors. Even if there are several degrees in between. Only restarting the Shelly app in Homey causes it to display temperature changes again
c212a8df-8ae1-44c9-9efb-2cda254d42d4
Hi all,
I have tried with 2 shelly’s
Shelly Qubino Wave i4 AC
Shelly Qubino Wave i4 DC
But both sensors just report their input once(when i just paired the devices with my homey pro)
And then the status report stops
I cannot see the inputs change on my homey pro…
Can someone help me?
I first tought it was just a problem with the DC shelly.
Nope, it only reports changed states.
Could you post the output of http://yourshellyip/rpc/Shelly.GetStatus using a code block (the </> icon).
If you want to use the inputs you need to configure the channel as a toggle switch. When set to momentary it will only fire action events and you will need to use the action event trigger card.
I have a shelly pro 4pm but in the homey app i can not connect this anymore. So i can not make any flow in homey anymore
Do i something wrong or why is this device not longer available for programming in Homey?
Please explain in more detail what “can not connect anymore” means. What is the error?
I installed the shelly app, but i can not select the shelly pro 4pm to add this device. This device isnt listed anymore to select.
So no error, device is not able to add to Homey.
