Beiträge von mbcmb

Issues with amazon echo and all Shelly devices since 15th

Current issues are with 5x shelly1 relays

Hey, just wondering if anyone else is having any issues controlling there devices using amazon echo devices?

Everything has been working perfect for months. And suddenly at the same time on the 15th all Shelly devices went to an unresponsive state in the Alexa app.

I’ve removed all devices, and the skill, and then added back the skill, authenticated, and discovered all the devices.

Which worked all devices were discovered

But all the devices still show was unresponsive and control is not possible.

I’ve spoken with amazon support who have indicated there maybe a Shelly API issue between the vendor and amazon but as of yet no fix.

However, Control via apple home works perfectly as it always has, control via home assistant works perfectly.

There have been no changes on my network setup either.

Manual control of the devices using the Shelly cloud app from iPhone also works but I have noticed the devices now take a few seconds to connect which was never an issue before, I have disabled the new eco mode but this has not helped. Any ideas?

Hi All,

I was wondering if anyone has experienced anything similar to issues i have experienced with the Shelly Motion.

When trying to connect the Shelly Motion to my Wi-Fi network it would not even attempt to try to associate to the WI-Fi network.

Troubleshooting:

1. Took multiple pcaps from the access points - No attempt from the device to connect to the access points
2. Reviewed logs from the meraki cloud dashboard - Confirms findings from PCAP, no attempt to associate.
3. Forced WI-Fi to use channel 13 ^{(See below for normal network config)} - No change
4. Setup new SSID (Name:testwifi)- No Change
5. Set new SSID to not require Authentication - No Change

At this point i was out of ideas on how to get this device to join the network

Considering there is already Shelly 7 devices on the network which have worked flawlessly i start to think it must be a hardware issue on the Shelly motion.

One More try

As one last attempt to get to the bottom of the problem, i Dusted off an Mikrotik WI-Fi device i had in storage.

1. Setup the Mikrotik with a new SSID (Name:Miktestwifi) - WPA2 PSK
2. Reset the Shelly motion device to factory
3. Joined this new WI-Fi on first attempt.

It Works?

At this stage, i start to wonder is it a special character issue between the Shelly motion hardware and the WI-Fi itself.

Next Steps

1. Copy the SSID and authentication settings from the Meraki System to the Mikrotik AP
2. Disable the SSID on the Meraki system
3. Connect the Mikrotik to VLAN759 so that the normal DHCP and DNS configuration is applied to all devices on the shelly SSID which is now live on the Mikrotik AP.
4. all 7 devices reconnect + 1 new motion device.

I am at a complete loss as to what the issue might be with the incompatibility between the Shelly Motion and the Meraki APs' at this stage.

If Anyone who reads this has any suggestions, comments, ideas, i would greatly appreciate it.

Cheers.

Environment:

Shelly Hardware:

• Shelly 1:
  • 6 Connected to WI-Fi
• Shelly Contact 2:
  • 1 Connected to WI-Fi

Network:

• Switch:
  • 2 x Cisco Layer 3 Managed
    • multiple VLANs
• WI-Fi
  • 2 x Cisco Meraki MR32 Running
    • Multiple SSIDs
      • 2.4Ghz
      • Channel Width 20Mhz
      • Channel 1 and 6
      • 5Ghz also running but not applicable in this issue.
• Edge & Up-links:
  • HA hardware firewalls
    • SDWAN Active.
  • Fiber connection
  • 5g Backup connection
• DHCP & DNS Managed by local Linux server