Heinz

So from what I found out it is in the road map but Unfortunately no eta on when it's going to be released and on what version of the product. Yes, the Shelly Wave 2pm has that option but between the wave and the shutter, they are two separate products. This is all I am able to provide at this current time but yes it will be coming

what settings and what router are you using?

I can find out what some information about this would take me some time though

Yes i also see that the IP address in the device is .102 and the SSID is "xxxxxx" this is from he looks of it a fritzbox? The signal to the Router is also don't he not great side with a -76. any chance you could increase the connectivity to the device?

im not sure about that i can ask

All the Shelly Pro devices have an RJ-45 network port integrated into the device. The Pro devices similar to the gen2 and Gen3 Devices can act as an Access point. However, the name of the SSID can not be changed. You could then add a camera to the AP of the Shelly Pro. But I think it would be simpler to have a PoE switch at the gate to then power a camera and provide network connectivity to the Shelly and Camera at the gate. Regarding what shelly to use by the gate would need more information on what type of gate controller you currently have to provide the best solution

In some cases re-adding it into the network would resync. But sometimes like the case above it did not. I would log in to the device via the WebUI and reconnect the device to the network. when you delete the device linked to scenes from the app and re-add it with the same name and in the same room, it should relink the device to the scenes. I have not tested what it does with the local actions, but that should be stored on the device's memory. This is only removed with you do a factory reset. hope this helps

awsome thanks for the update

The one thing people have tried to help with the connection issue is set a static IP this does help somewhat with the power consumption and connection time. Similar to the Smoke, the devices go into sleep mode to conserve power.

Na this was truly an honest mistake 🙂

Thats a much better location 😄

No post was removed 🙂 It was just moved to the correct location once the topic was finished off. Was just a minor permission issue.

@Walt Du hast dieses Thema bereits gepostet und es wurde zu den Feature Requests verschoben. Ich kann deine Frustration verstehen, aber gib den Änderungen etwas Zeit, das geht nicht über Nacht.

Translation Feature Update The translation feature has been improved! When translating forum posts, images, schematics, and graphics will now be retained in the translated version. Important Note: Some older pages stored in the translation cache may still be affected, but all new posts containing graphics will keep them intact during translation.

Alexa can work with Shelly devices, but it does not directly support Shelly app groups. To control multiple Shelly devices as a group using Alexa, you'll need to create the group within the Alexa app itself.

have you tried this with a scene or a action ?

@Cor Check DM 🙂

Hi. I can't see the internal IP address of your network so I can't see if there is an issue or not 😄 ( its generally no major risk to showing your internal IP address but never share your public IP, as long as your internal IP is not pointing outside its not a major risk 🙂 ) what you can try is to make the DNS and the gateway the same IP address this should be the IP address of your network Default gateway. What I sometimes do with networks before I set a static IP address in a complex network is see that the device is working when getting an IP address from the DHCP server. Does the Device still say offline when you set the device to get the automatic IP address? If it stays offline when getting the IP address from the DHCP server ( Router ), there is a block. But I don't think by the sounds of it that you have any firewall to block devices. Try that and let me know

Hmm odd there can only be a few things that would stop the cloud connection. Network settings and default gateway is incorrect. Firewall settings blocking connection I would look at the debug log on the device to confirm that there are no errors from the device side from the looks of that screen show that does not look like the latest firmware. can you confirm what firmware you have installed and also check on your cloud settings that its connected to a cloud server

could you send a debug log of your device? Below is the guide on how to do it

im doing the update to 1.4.0 to check if I get the same issue

not with the bus system sadly not.

are the shelly devices on a other vlan ?

Perfect glad it worked and thanks for the feedback

Ich würde den Shelly-Support kontaktieren, indem ich ein Ticket eröffne, und sehen, was sie für dich tun können.