Did you follow the troubleshoot guide from the first post?
Yes I did.
Then the Blu Motion is probably out of range of the 1PM Gen3 (or you didnt follow the troubleshoot guide to the letter and there is still something wrong with your setup). What was the result the debugging the Bluetooth Proxy script?
I added the line console.log(BTHparsed); in the script with the shelly App. The output of the debug is: WebSocket ist closed to 192.168.178.26. Error code: 1006
There you have it. Obviously something is wrong with the outbound websocket connection between the Shelly plus and Homey. Look at the schema from the first post and follow the actions from step 3.
Hey. I have a problem with my new Shelly BLU Button 1. The Button is paired with Shelly Cloud and works well in the Shelly App. I also could add it to my Homey (Cloud) without problems. I want to use the Button as Trigger in some Flow. When I press the Button it is recognized in the Shelly App but my Homey Flow wonât start. It seems like Homey Cloud doesnât know that the Button was pressed.
How where you able to add this device to Homey Cloud in the first place. Shelly BLU devices are not supported on Homey Cloud.
That explains my problem 
After I added it to the shelly app I was able to add it to my home cloud. Just the normal way. Click on the plus and âadd a new deviceâ and after choosing the shelly app the button was shown there and I was able to add it to my homey.
I see, I wasnt aware that Plus/Pro devices that are connected to the Shelly Cloud also expose the Shelly BLU devices associated with it. Iâll have to see if that allows me to add support for these BLU devices for Homey Cloud.
That would be great!
Is it possible to measure the bluetooth strength of the BLU Motion with the 1PM Gen3 bluetooth gateway? Or is there an other way to measure or show it?
Check the RSSI capability under the BLU device in Homey.
Hi @Phuturist,
Sorry to disturb you, but today after seeing the #3 Podcast from Homey I would like to see if you can answer to one question.
On minute: 0:34:35â, they answered a question from one user:
Q1: Is there a supported platform for OTA updates, like Zwave?
The answer was no, and maybe not so soon⌠Maybe with Matter.
But he also said that companies with their own apps could do it if they want.
Do you have any idea if it will be possible in the future to update Shelly Zwave Devices using Homey?
Thank you.
Not sure how you expect a different answer from me on this.
If the guys from Athom say it will not be supported (soon) than it will not be supported (soon). Athom needs to update their SDK so developers can use that to create OTA functionality for their Zwave devices. If they dont think that functionality like OTA is of high priority than users must use a different platform to achieve this. You could for instance use Home Assistant with ZwaveJS or even standalone ZwaveJS2MQTT to update Shelly Wave devices.
1 Like
They say that developers can implement OTA updates (also for Zigbee), but they donât explain how or provide any example code, nor do they implement firmware updates for any of their own apps. Theyâre basically putting the blame on the developers for not implementing this feature, which IMO is really bad (but typical).
Until Athom shows us an actual working example, Iâm calling BS that itâs even possible.
2 Likes
Maybe good if you would also make a support ticket to Athom. The last news I got is that the developers are going to look into it but we know how that will go 
Yes Didier, I sent also to Athom a few days ago. Iâll keep you updated.
1 Like
@Phuturist Tonight tried to hook up a Shelly Flood sensor.
First gave the sensor its own IP address, which went well.
Then rebooted. New wifi and IP address were accepted.
Then add to Homey, 2019.
The sensor is recognized, click next and immediately the story that the device should be kept awake. But it is awake. With the web interface I can access the device.
Shelly app restart, makes no sense.
Tried on HP 23, exact same story. Unable to add. Pressing the button was also no use.
So Homey restarted and adding the sensor was no problem.
Flood sensor now running on latest Beta firmware,
Works fine, thank you.
Just wanted to let you know this.
As far as I can tell itâs an issue with mDNS caching on Homey. Not for me to fix and I donât think Athom will acknowledge and fix this either.
I did not see it as a real problem.
The only thing is that it finds the new device when you search for new devices. It only does not add it to Homey, you have to restart Homey first.
