Edge Shelly drivers for Gen1 and Gen2 Devices

Devices & Integrations Device Ideas
, , ,
102

Yes, the ip is the hub SmartThings. (becouse I already use it with the drive edge using shelly 1pm :crossed_fingers:To try

103

Do you have the RGBW2 white or color?

104

I own RGBW2 and curently use it with 4x white option. Feel free to implement it also :wink:

Regards from sLOVEnia :tumbler_glass:

2 Likes
105

New driver update is available (Version 2022-01-28T18:44:21.273414) with the following enhancements:

  • Added Plug device
  • Added 3EM device - you’ll see for this one that the device details are in random order at the moment; I will better organize these after some initial feedback on its operation
  • Fixed erroneous error message in Door/Window sensor log output
2 Likes
106

I can’t add it because the device creator isn’t working for me

Screenshot_2022-01-28-23-57-20-36_ee29f370f755f274a0693481416ae4a8
Screenshot_2022-01-28-23-57-20-36_ee29f370f755f274a0693481416ae4a81080×2400 172 KB

Screenshot_2022-01-28-23-57-12-28_ee29f370f755f274a0693481416ae4a8
Screenshot_2022-01-28-23-57-12-28_ee29f370f755f274a0693481416ae4a81080×2400 102 KB

107

That’s odd; give it some time and try again later. It looks like it’s not picking up the updated device selection list (there’s a new one with this update)

1 Like
108

The strange thing is that before upgrading from the device “shelly maker” I could choose what to create. Now I see only “connected” I will wait until tomorrow, maybe my hub has yet to receive the update :man_shrugging:t2:

109

Now it works, or rather, I can choose 3em,but not works

Screenshot_2022-01-29-00-34-33-89_ee29f370f755f274a0693481416ae4a8
Screenshot_2022-01-29-00-34-33-89_ee29f370f755f274a0693481416ae4a81080×2400 148 KB

If I can do something to help you understand what is the problem, Let me know

1 Like
110

If it doesn’t clear itself after a while, you may need to uninstall and reinstall the driver. Keep me posted. I’d be interested if others are seeing something similar.

111

Mine is ok

1 Like
112

An you try to create a 3EM?

113

Nope only shelly 1,
Just try to create a shelly 3 and i have a
network error , also try shelly 1 network error.

114

We’ll that’s discouraging! Let’s wait 12 hours. If it still is doing the same thing, it may be necessary to delete and reinstall the driver.

I’m really not sure why this would be happening. :thinking:

115

I also can’t add any new devices with the new driver.

116

Also, the door window 2 sensors are no longer responsive - they do not report status.

117

No logs:

│ Driver Id │ Name │

├────┼──────────────────────────────────────┼────────────────────────────────────────┤
│ 1 │ ee23b1ad-8589-4355-924a-283e41a38d98 │ Aqara Cube │
│ 2 │ 8f390da7-c66d-4245-9ba9-e431f95c78ec │ Shelly Device Driver V1 │
│ 3 │ d17e16fd-bf79-42da-a22f-46cf1f8c4f12 │ Virtual Devices │
│ 4 │ d06f05ce-1865-4a16-b99d-bf1778bab8c2 │ Xiaomi Motion Sensor │
│ 5 │ c42a476b-bcc0-4d40-8c6e-21a85bb52a80 │ Xiaomi Sensors │
│ 6 │ c09c02d7-d05d-4bf4-831b-207a1adeae2f │ Xiaomi Temperature │
│ 7 │ e165119d-d6ee-4bac-80e8-7412bb72df80 │ Zigbee Contact │
│ 8 │ a01bd113-efa3-45f1-8b56-a7ed0dbd1689 │ Zigbee Contact Mc │
│ 9 │ 6f87ee54-2d9f-4c94-8bba-01bc087b232d │ Zigbee Level ColorTemperature Bulb │
│ 10 │ 4ff0ceba-8170-4d6f-b177-b34715a436e0 │ Zigbee Level ColorTemperature Light Mc │
│ 11 │ 0e362494-39f0-4f36-a57b-e62afa81fbb1 │ Zigbee Motion Sensor Mc │
│ 12 │ 3e12677e-f9e9-4583-b88f-990c1e1822de │ Zigbee Multi Switch Mc │
│ 13 │ 59259997-a263-431f-ad7b-ddc8d2776e98 │ Zigbee RGB-RGBW Light Mc │
│ 14 │ a2f7ec78-14c8-492d-9965-7544b0fc3b68 │ Zigbee Smoke Detector Mc │
│ 15 │ b0879f79-e81d-4c5f-aebd-4f1c5f4f2fd4 │ Zigbee Switch Mc-(OLD) │
│ 16 │ fea7bb98-51a2-4a1e-a4c6-62761bfdb17c │ Zigbee Switch Mc-(OLD) │
│ 17 │ dfdb7a46-3b9a-49af-b08a-2e4624648a42 │ Zigbee Water Leak/Smoke Sensor │
└────┴──────────────────────────────────────┴────────────────────────────────────────┘
? Select a driver. 2
listening for logs… -

118

It is not necessary, from the device “shelly creator” I changed drivers using the web requesr always yours, I saved and put back the correct drive, so I solved and now the devices can still be added. I added the shelly 3 EM, although the many data indicated, make me very confused and I think it does not work properly. It’s still a good starting point :+1: thanks for your work

Screenshot_2022-01-29-10-48-50-60
Screenshot_2022-01-29-10-48-50-601080×9170 197 KB

119

Log on refresh:

2022-01-29T15:29:01.660425794+00:00 TRACE Shelly Device Driver V1 Found CapabilityCommandDispatcher handler in thisDriver
2022-01-29T15:29:01.663230586+00:00 INFO Shelly Device Driver V1 Refresh requested
2022-01-29T15:29:01.666538794+00:00 DEBUG Shelly Device Driver V1 Vrata otroka device thread event handled
2022-01-29T15:29:01.671539419+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.221/status
2022-01-29T15:29:04.823449171+00:00 PRINT Shelly Device Driver V1 HTTP ret:
2022-01-29T15:29:04.826681254+00:00 PRINT Shelly Device Driver V1 HTTP code: [string “socket”]:1406: connect (with timeout) failed (192.168.1.221:80): Os { code: 113, kind: Other, message: “No route to host” }
2022-01-29T15:29:04.830155296+00:00 PRINT Shelly Device Driver V1 HTTP response:
2022-01-29T15:29:04.833246879+00:00 ERROR Shelly Device Driver V1 HTTP request failed: nil [string “socket”]:1406: connect (with timeout) failed (192.168.1.221:80): Os { code: 113, kind: Other, message: “No route to host” } nil
2022-01-29T15:29:04.836474504+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.221/status
2022-01-29T15:29:07.946835464+00:00 PRINT Shelly Device Driver V1 HTTP ret:
2022-01-29T15:29:07.950266630+00:00 PRINT Shelly Device Driver V1 HTTP code: [string “socket”]:1406: connect (with timeout) failed (192.168.1.221:80): Os { code: 113, kind: Other, message: “No route to host” }
2022-01-29T15:29:07.953375214+00:00 PRINT Shelly Device Driver V1 HTTP response:
2022-01-29T15:29:07.956499380+00:00 ERROR Shelly Device Driver V1 HTTP request failed: nil [string “socket”]:1406: connect (with timeout) failed (192.168.1.221:80): Os { code: 113, kind: Other, message: “No route to host” } nil
2022-01-29T15:29:07.959791464+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.221/status
2022-01-29T15:29:11.063424007+00:00 PRINT Shelly Device Driver V1 HTTP ret:
2022-01-29T15:29:11.066685715+00:00 PRINT Shelly Device Driver V1 HTTP code: [string “socket”]:1406: connect (with timeout) failed (192.168.1.221:80): Os { code: 113, kind: Other, message: “No route to host” }
2022-01-29T15:29:11.070055090+00:00 PRINT Shelly Device Driver V1 HTTP response:
2022-01-29T15:29:11.073114215+00:00 ERROR Shelly Device Driver V1 HTTP request failed: nil [string “socket”]:1406: connect (with timeout) failed (192.168.1.221:80): Os { code: 113, kind: Other, message: “No route to host” } nil
2022-01-29T15:29:11.077237674+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.221/status
2022-01-29T15:29:14.186019508+00:00 PRINT Shelly Device Driver V1 HTTP ret:
2022-01-29T15:29:14.189430467+00:00 PRINT Shelly Device Driver V1 HTTP code: [string “socket”]:1406: connect (with timeout) failed (192.168.1.221:80): Os { code: 113, kind: Other, message: “No route to host” }
2022-01-29T15:29:14.192548217+00:00 PRINT Shelly Device Driver V1 HTTP response:
2022-01-29T15:29:14.195672050+00:00 ERROR Shelly Device Driver V1 HTTP request failed: nil [string “socket”]:1406: connect (with timeout) failed (192.168.1.221:80): Os { code: 113, kind: Other, message: “No route to host” } nil
2022-01-29T15:29:14.198995925+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.221/status
2022-01-29T15:29:17.303579593+00:00 PRINT Shelly Device Driver V1 HTTP ret:
2022-01-29T15:29:17.306817552+00:00 PRINT Shelly Device Driver V1 HTTP code: [string “socket”]:1406: connect (with timeout) failed (192.168.1.221:80): Os { code: 113, kind: Other, message: “No route to host” }
2022-01-29T15:29:17.310132260+00:00 PRINT Shelly Device Driver V1 HTTP response:
2022-01-29T15:29:17.313179635+00:00 ERROR Shelly Device Driver V1 HTTP request failed: nil [string “socket”]:1406: connect (with timeout) failed (192.168.1.221:80): Os { code: 113, kind: Other, message: “No route to host” } nil
2022-01-29T15:29:17.316331093+00:00 ERROR Shelly Device Driver V1 Failed to get status for Vrata otroka
2022-01-29T15:29:17.319624802+00:00 DEBUG Shelly Device Driver V1 Vrata otroka device thread event handled

120

I notice that my shelly 1 devices are seen as a door sensor, with indicated open or closed. I realized that on is closed and off it is open, like an electrical circuit. I realized that this thing was done to allow you to use automations with alexa, which is able to activate with port sensors and not with switches. Ok, but for me who don’t care about this feature in the slightest, can I somehow delete it? :thinking: The aesthetics of the page of the Device I do not like that it is seen so:

Screenshot_2022-01-29-21-38-46-56_ee29f370f755f274a0693481416ae4a8
Screenshot_2022-01-29-21-38-46-56_ee29f370f755f274a0693481416ae4a81080×2400 130 KB

And another thing, The history of the ignitions becomes dispersive, with n a sort of double notifications, a closed plus an on, an open plus one off…

Screenshot_2022-01-29-21-39-49-01_ee29f370f755f274a0693481416ae4a8
Screenshot_2022-01-29-21-39-49-01_ee29f370f755f274a0693481416ae4a81080×2400 148 KB

Is it possible to see only on off as I would expect from a Device on/off?
Sorry, it’s just my request, I would just like to understand if possible. Thank you

122

Are you certain that you have the correct IP address for your device? If it’s not set as a static address it might have changed. You can also try just typing this in your browser and see if you can get a response:

http://192.168.1.221/status