Edge Shelly drivers for Gen1 and Gen2 Devices

Devices & Integrations Device Ideas
, , ,
42

@TAustin
Logs for revised shelly. 2 on-off cycles

2022-01-19T23:22:45.499484466+00:00 TRACE Shelly Device Driver V1 Received event with handler capability
2022-01-19T23:22:45.510071258+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> received command: {“command”:“off”,“component”:“main”,“positional_args”:,“capability”:“switch”,“args”:}
2022-01-19T23:22:45.513580341+00:00 TRACE Shelly Device Driver V1 Found CapabilityCommandDispatcher handler in thisDriver
2022-01-19T23:22:45.516425216+00:00 INFO Shelly Device Driver V1 main switch turned off
2022-01-19T23:22:45.519659758+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.140/relay/0/?turn=off
2022-01-19T23:22:45.622759550+00:00 PRINT Shelly Device Driver V1 response=> {“ison”:false,“has_timer”:false,“timer_started”:0,“timer_duration”:0,“timer_remaining”:0,“source”:“http”}
2022-01-19T23:22:45.626710300+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“state”:{“value”:“off”},“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“main”}
2022-01-19T23:22:45.637824216+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“state”:{“value”:“open”},“capability_id”:“contactSensor”,“attribute_id”:“contact”,“component_id”:“main”}
2022-01-19T23:22:45.648151633+00:00 DEBUG Shelly Device Driver V1 Shelly R1 1 device thread event handled
2022-01-19T23:22:49.098789633+00:00 TRACE Shelly Device Driver V1 Received event with handler capability
2022-01-19T23:22:49.124486967+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> received command: {“command”:“on”,“component”:“main”,“positional_args”:,“capability”:“switch”,“args”:}
2022-01-19T23:22:49.127706383+00:00 TRACE Shelly Device Driver V1 Found CapabilityCommandDispatcher handler in thisDriver
2022-01-19T23:22:49.149155967+00:00 INFO Shelly Device Driver V1 main switch turned on
2022-01-19T23:22:49.170369092+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.140/relay/0/?turn=on
2022-01-19T23:22:49.435174925+00:00 PRINT Shelly Device Driver V1 response=> {“ison”:true,“has_timer”:false,“timer_started”:0,“timer_duration”:0,“timer_remaining”:0,“source”:“http”}
2022-01-19T23:22:49.443365425+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“main”}
2022-01-19T23:22:49.459897508+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“state”:{“value”:“closed”},“capability_id”:“contactSensor”,“attribute_id”:“contact”,“component_id”:“main”}
2022-01-19T23:22:49.475401425+00:00 DEBUG Shelly Device Driver V1 Shelly R1 1 device thread event handled
2022-01-19T23:22:49.481244050+00:00 TRACE Shelly Device Driver V1 Received event with handler server
2022-01-19T23:22:49.504217467+00:00 DEBUG Shelly Device Driver V1 Accepted connection from 192.168.1.140:2808
2022-01-19T23:22:49.507700384+00:00 PRINT Shelly Device Driver V1 Firstline: GET /67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/on HTTP/1.1
2022-01-19T23:22:49.511537467+00:00 PRINT Shelly Device Driver V1 Headerline: Host: 192.168.1.154:42841
2022-01-19T23:22:49.514938217+00:00 PRINT Shelly Device Driver V1 Headerline: Content-Length: 0
2022-01-19T23:22:49.530100092+00:00 PRINT Shelly Device Driver V1 Headerline: User-Agent: Shelly/20211109-124958/v1.11.7-g682a0db (SHSW-1)
2022-01-19T23:22:49.545262092+00:00 INFO Shelly Device Driver V1 Message for Shelly R1 1: endpoint=/67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/on
2022-01-19T23:22:49.549129967+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“state”:{“value”:“closed”},“capability_id”:“contactSensor”,“attribute_id”:“contact”,“component_id”:“main”}
2022-01-19T23:22:49.558058634+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“main”}
2022-01-19T23:22:52.382725509+00:00 TRACE Shelly Device Driver V1 Received event with handler capability
2022-01-19T23:22:52.395238801+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> received command: {“command”:“off”,“component”:“main”,“positional_args”:,“capability”:“switch”,“args”:}
2022-01-19T23:22:52.398567051+00:00 TRACE Shelly Device Driver V1 Found CapabilityCommandDispatcher handler in thisDriver
2022-01-19T23:22:52.401748592+00:00 INFO Shelly Device Driver V1 main switch turned off
2022-01-19T23:22:52.404952051+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.140/relay/0/?turn=off
2022-01-19T23:22:52.484668051+00:00 PRINT Shelly Device Driver V1 response=> {“ison”:false,“has_timer”:false,“timer_started”:0,“timer_duration”:0,“timer_remaining”:0,“source”:“http”}
2022-01-19T23:22:52.488615259+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“state”:{“value”:“off”},“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“main”}
2022-01-19T23:22:52.499156051+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“state”:{“value”:“open”},“capability_id”:“contactSensor”,“attribute_id”:“contact”,“component_id”:“main”}
2022-01-19T23:22:52.509703176+00:00 DEBUG Shelly Device Driver V1 Shelly R1 1 device thread event handled
2022-01-19T23:22:54.471098384+00:00 TRACE Shelly Device Driver V1 Received event with handler capability
2022-01-19T23:22:54.481247259+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> received command: {“command”:“on”,“component”:“main”,“positional_args”:,“capability”:“switch”,“args”:}
2022-01-19T23:22:54.484763967+00:00 TRACE Shelly Device Driver V1 Found CapabilityCommandDispatcher handler in thisDriver
2022-01-19T23:22:54.487519842+00:00 INFO Shelly Device Driver V1 main switch turned on
2022-01-19T23:22:54.490760759+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.140/relay/0/?turn=on
2022-01-19T23:22:54.628693551+00:00 PRINT Shelly Device Driver V1 response=> {“ison”:true,“has_timer”:false,“timer_started”:0,“timer_duration”:0,“timer_remaining”:0,“source”:“http”}
2022-01-19T23:22:54.632928884+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“main”}
2022-01-19T23:22:54.643220176+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“state”:{“value”:“closed”},“capability_id”:“contactSensor”,“attribute_id”:“contact”,“component_id”:“main”}
2022-01-19T23:22:54.656285342+00:00 DEBUG Shelly Device Driver V1 Shelly R1 1 device thread event handled
2022-01-19T23:22:54.660278009+00:00 TRACE Shelly Device Driver V1 Received event with handler server
2022-01-19T23:22:54.673043301+00:00 DEBUG Shelly Device Driver V1 Accepted connection from 192.168.1.140:22771
2022-01-19T23:22:54.676645342+00:00 PRINT Shelly Device Driver V1 Firstline: GET /67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/on HTTP/1.1
2022-01-19T23:22:54.680592051+00:00 PRINT Shelly Device Driver V1 Headerline: Host: 192.168.1.154:42841
2022-01-19T23:22:54.683963759+00:00 PRINT Shelly Device Driver V1 Headerline: Content-Length: 0
2022-01-19T23:22:54.687271551+00:00 PRINT Shelly Device Driver V1 Headerline: User-Agent: Shelly/20211109-124958/v1.11.7-g682a0db (SHSW-1)
2022-01-19T23:22:54.697019967+00:00 INFO Shelly Device Driver V1 Message for Shelly R1 1: endpoint=/67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/on
2022-01-19T23:22:54.700793717+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“state”:{“value”:“closed”},“capability_id”:“contactSensor”,“attribute_id”:“contact”,“component_id”:“main”}
2022-01-19T23:22:54.710043426+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“main”}
listening for logs… -

1 Like
43

Hi, The only values ​​that appear to me are energy consumption, temperature and signal strength.

44

I’m sorry for the problems with this 2.5 roller mode device. It’s a bit more tricky to get right, but I have more confidence in the driver update I just pushed out, so hopefully you’ll see better results. Please give it another shot and let me know. (@dusanhauko)

I appreciate your patience! I’ve now got one of these devices on order so I’ll soon have one to test myself.

1 Like
45

It works partialy in Roller mode.
Works with percentage bar 0-100% without issues.
Buttons open/close/pause just spins that icon and nothing happens. In a few seconds i get popup info about networ error.
Other info is there and updates.

Hey! This is our hobby and the patience is necessary :wink:

Dusan

46

Thank you Dusan. I’m surprised about the spinning buttons; are you certain that you had gotten the update I sent out shortly ago? Check the Driver version by tapping the 3 vertical dots in the upper right corner within the creator device details screen. Then tap ‘Driver’ and look for the Version. It should be:

2022-01-20T18:10:01.741155

47

Ups… Stil on 19.01.22, 21:35 :triumph:

48

SmartThings says hubs can take up to 12 hours to update, but most people I’ve heard from says it happens much quicker. Some get updates almost immediately. Give it some time…

1 Like
49

@TAustin
I have done some additional testing with my Shelly1.
I noticed the when you operate the dumb hard wired switch that the state in the app changes to on but does NOT change back to off when you turn off the dumb switch.

The following are the logs for 2 on-off cycles with the dumb switch:
2022-01-21T01:48:30.774654507+00:00 TRACE Shelly Device Driver V1 Received event with handler server
2022-01-21T01:48:30.786029466+00:00 DEBUG Shelly Device Driver V1 Accepted connection from 192.168.1.140:8503
2022-01-21T01:48:30.789553591+00:00 PRINT Shelly Device Driver V1 Firstline: GET /67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/on HTTP/1.1
2022-01-21T01:48:30.793187216+00:00 PRINT Shelly Device Driver V1 Headerline: Host: 192.168.1.154:54025
2022-01-21T01:48:30.796544799+00:00 PRINT Shelly Device Driver V1 Headerline: Content-Length: 0
2022-01-21T01:48:30.800169841+00:00 PRINT Shelly Device Driver V1 Headerline: User-Agent: Shelly/20211109-124958/v1.11.7-g682a0db (SHSW-1)
2022-01-21T01:48:30.810510299+00:00 INFO Shelly Device Driver V1 Message for Shelly R1 1: endpoint=/67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/on
2022-01-21T01:48:30.814829091+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“component_id”:“main”,“capability_id”:“contactSensor”,“attribute_id”:“contact”,“state”:{“value”:“closed”}}
2022-01-21T01:48:30.826006007+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“component_id”:“main”,“capability_id”:“switch”,“attribute_id”:“switch”,“state”:{“value”:“on”}}
2022-01-21T01:48:35.235159756+00:00 TRACE Shelly Device Driver V1 Received event with handler server
2022-01-21T01:48:35.277207881+00:00 DEBUG Shelly Device Driver V1 Accepted connection from 192.168.1.140:17775
2022-01-21T01:48:35.280714756+00:00 PRINT Shelly Device Driver V1 Firstline: GET /67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/on HTTP/1.1
2022-01-21T01:48:35.287741631+00:00 PRINT Shelly Device Driver V1 Headerline: Host: 192.168.1.154:54025
2022-01-21T01:48:35.292683048+00:00 PRINT Shelly Device Driver V1 Headerline: Content-Length: 0
2022-01-21T01:48:35.296095090+00:00 PRINT Shelly Device Driver V1 Headerline: User-Agent: Shelly/20211109-124958/v1.11.7-g682a0db (SHSW-1)
2022-01-21T01:48:35.317435881+00:00 INFO Shelly Device Driver V1 Message for Shelly R1 1: endpoint=/67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/on
2022-01-21T01:48:35.324215381+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“component_id”:“main”,“capability_id”:“contactSensor”,“attribute_id”:“contact”,“state”:{“value”:“closed”}}
2022-01-21T01:48:35.345039631+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“component_id”:“main”,“capability_id”:“switch”,“attribute_id”:“switch”,“state”:{“value”:“on”}}
listening for logs… /

1 Like
50

Thanks Paul. There definitely is no ‘off’ message being received shown in the log.

Could be something went wrong with the callback url setup. Could you capture a log showing initial device status retrieval & setup? Temporarily change the IP address in settings to something else, and then back again.

51

Here are the logs from when I changed the IP back to the correct adress. 2 errors at end.

2022-01-21T03:53:10.528249666+00:00 TRACE Shelly Device Driver V1 Received event with handler device_lifecycle
2022-01-21T03:53:10.615385374+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> received lifecycle event: infoChanged
2022-01-21T03:53:10.630004041+00:00 TRACE Shelly Device Driver V1 Found DeviceLifecycleDispatcher handler in thisDriver
2022-01-21T03:53:10.633108541+00:00 DEBUG Shelly Device Driver V1 Info changed handler invoked
2022-01-21T03:53:10.641542499+00:00 INFO Shelly Device Driver V1 Device address changed to: 192.168.1.140
2022-01-21T03:53:10.645140416+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.140/status
2022-01-21T03:53:10.746340499+00:00 PRINT Shelly Device Driver V1 response=> {“wifi_sta”:{“connected”:true,“ssid”:“K21E8”,“ip”:“192.168.1.140”,“rssi”:-58},“cloud”:{“enabled”:true,“connected”:true},“mqtt”:{“connected”:false},“time”:“22:53”,“unixtime”:1642737190,“serial”:296,“has_update”:false,“mac”:“8CAAB5C51A51”,“cfg_changed_cnt”:10,“actions_stats”:{“skipped”:0},“relays”:[{“ison”:false,“has_timer”:false,“timer_started”:0,“timer_duration”:0,“timer_remaining”:0,“source”:“http”}],“meters”:[{“power”:0.00,“is_valid”:true}],“inputs”:[{“input”:0,“event”:"",“event_cnt”:0}],“ext_sensors”:{},“ext_temperature”:{},“ext_humidity”:{},“update”:{“status”:“idle”,“has_update”:false,“new_version”:“20211109-124958/v1.11.7-g682a0db”,“old_version”:“20211109-124958/v1.11.7-g682a0db”},“ram_total”:50880,“ram_free”:39428,“fs_size”:233681,“fs_free”:149596,“uptime”:776078}
2022-01-21T03:53:10.761126707+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“component_id”:“main”,“capability_id”:“signalStrength”,“attribute_id”:“rssi”,“state”:{“value”:-58}}
2022-01-21T03:53:10.776189832+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“component_id”:“main”,“capability_id”:“switch”,“attribute_id”:“switch”,“state”:{“value”:“off”}}
2022-01-21T03:53:10.789935457+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“component_id”:“main”,“capability_id”:“contactSensor”,“attribute_id”:“contact”,“state”:{“value”:“open”}}
2022-01-21T03:53:10.807915457+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.140/settings/actions/?index=0&name=out_on_url&enabled=true&urls[]=http://192.168.1.154:54025/67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/on
2022-01-21T03:53:16.100607500+00:00 ERROR Shelly Device Driver V1 HTTP request failed: [string “socket”]:1406: timeout
2022-01-21T03:53:16.162701583+00:00 ERROR Shelly Device Driver V1 Shelly R1 1 thread encountered error: [string “st.dispatcher”]:229: Error encountered while processing event for <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)>:
arg1: infoChanged
arg2: table: 0x14834f8
[string “R1”]:63: attempt to index a nil value (global ‘socket’)
listening for logs… /

52

Perfect thank-you. For some reason the url callback setup messages are failing. So the device doesn’t even know to send on/off notifications. The http message I’m sending looks right but I’ll have to double check. Could also be that retries are needed if device isn’t able to respond.

53

Is that some thing to do this this message from yesterday?

“Thanks Paul. Apart from that error this sequence brings up something I need to consider: That sending a command to turn on or off will also result in notification from the device that it has turned on or off. I’ll want to avoid emitting duplicate attribute updates to SmartThings if I can. I find with Edge devices, rapid sequential emits can get dropped.”

54

No. That doesn’t cause an error like this.

I got a timeout sending the message to the device, meaning it didn’t answer within 5 seconds. But then there was another error that occurred which I have to figure out.

55

@Paul_Oliver and everyone else:

I just pushed out another driver update. I know that’s 2 in one day so I hope I’m not being disruptive to anyone!

This one contains an increase in the number of retries for sending setup messages to the device to address situations where the SmartThings device isn’t getting updated by changes initiated at the device.

Paul - let me know if this solves it; once you get this, let’s look at the logs again while your device initializes to see if timeouts continue to be a problem.

Driver Id         8f390da7-c66d-4245-9ba9-e431f95c78ec 
Name              Shelly Device Driver V1
Package Key       shellyv1  
Version           2022-01-21T04:51:40.795046
2 Likes
56

log when changing IP

2022-01-21T04:56:15.850105822+00:00 TRACE Shelly Device Driver V1 Received event with handler device_lifecycle
2022-01-21T04:56:15.862731947+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> received lifecycle event: infoChanged
2022-01-21T04:56:15.871553114+00:00 TRACE Shelly Device Driver V1 Found DeviceLifecycleDispatcher handler in thisDriver
2022-01-21T04:56:15.874472864+00:00 DEBUG Shelly Device Driver V1 Info changed handler invoked
2022-01-21T04:56:15.877462906+00:00 INFO Shelly Device Driver V1 Device address changed to: 192.168.1.140
2022-01-21T04:56:15.880793489+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.140/status
2022-01-21T04:56:15.971605197+00:00 PRINT Shelly Device Driver V1 response=> {“wifi_sta”:{“connected”:true,“ssid”:“K21E8”,“ip”:“192.168.1.140”,“rssi”:-61},“cloud”:{“enabled”:true,“connected”:false},“mqtt”:{“connected”:false},“time”:“23:56”,“unixtime”:1642740976,“serial”:17,“has_update”:false,“mac”:“8CAAB5C51A51”,“cfg_changed_cnt”:6,“actions_stats”:{“skipped”:0},“relays”:[{“ison”:false,“has_timer”:false,“timer_started”:0,“timer_duration”:0,“timer_remaining”:0,“source”:“http”}],“meters”:[{“power”:0.00,“is_valid”:true}],“inputs”:[{“input”:0,“event”:"",“event_cnt”:0}],“ext_sensors”:{},“ext_temperature”:{},“ext_humidity”:{},“update”:{“status”:“unknown”,“has_update”:false,“new_version”:"",“old_version”:“20211109-124958/v1.11.7-g682a0db”},“ram_total”:50880,“ram_free”:39832,“fs_size”:233681,“fs_free”:149094,“uptime”:2582}
2022-01-21T04:56:15.978235447+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“component_id”:“main”,“attribute_id”:“rssi”,“state”:{“value”:-61},“capability_id”:“signalStrength”}
2022-01-21T04:56:15.989667197+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“component_id”:“main”,“attribute_id”:“switch”,“state”:{“value”:“off”},“capability_id”:“switch”}
2022-01-21T04:56:16.001491656+00:00 INFO Shelly Device Driver V1 <Device: 67ed4bc7-fe39-4a6b-942d-3412c6c36d69 (Shelly R1 1)> emitting event: {“component_id”:“main”,“attribute_id”:“contact”,“state”:{“value”:“open”},“capability_id”:“contactSensor”}
2022-01-21T04:56:16.012148197+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.140/settings/actions/?index=0&name=out_on_url&enabled=true&urls[]=http://192.168.1.154:40565/67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/on
2022-01-21T04:56:21.043436029+00:00 ERROR Shelly Device Driver V1 HTTP request failed: [string “socket”]:1406: timeout
2022-01-21T04:56:21.550124488+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.140/settings/actions/?index=0&name=out_on_url&enabled=true&urls[]=http://192.168.1.154:40565/67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/on
2022-01-21T04:56:26.578689736+00:00 ERROR Shelly Device Driver V1 HTTP request failed: [string “socket”]:1406: timeout
2022-01-21T04:56:27.149348570+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.140/settings/actions/?index=0&name=out_on_url&enabled=true&urls[]=http://192.168.1.154:40565/67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/on
2022-01-21T04:56:32.209264027+00:00 ERROR Shelly Device Driver V1 HTTP request failed: [string “socket”]:1406: timeout
2022-01-21T04:56:32.715494943+00:00 ERROR Shelly Device Driver V1 Shelly R1 1 - device initialization error: /settings/actions/?index=0&name=out_on_url&enabled=true&urls=http://192.168.1.154:40565/67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/on
2022-01-21T04:56:32.718945193+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.140/settings/actions/?index=0&name=out_off_url&enabled=true&urls[]=http://192.168.1.154:40565/67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/off
2022-01-21T04:56:37.904137275+00:00 ERROR Shelly Device Driver V1 HTTP request failed: [string “socket”]:1406: timeout
2022-01-21T04:56:38.418182650+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.140/settings/actions/?index=0&name=out_off_url&enabled=true&urls[]=http://192.168.1.154:40565/67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/off
2022-01-21T04:56:43.464108732+00:00 ERROR Shelly Device Driver V1 HTTP request failed: [string “socket”]:1406: timeout
2022-01-21T04:56:43.973807857+00:00 PRINT Shelly Device Driver V1 Sending HTTP request: http://192.168.1.140/settings/actions/?index=0&name=out_off_url&enabled=true&urls[]=http://192.168.1.154:40565/67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/off
2022-01-21T04:56:49.007807564+00:00 ERROR Shelly Device Driver V1 HTTP request failed: [string “socket”]:1406: timeout
2022-01-21T04:56:49.516364231+00:00 ERROR Shelly Device Driver V1 Shelly R1 1 - device initialization error: /settings/actions/?index=0&name=out_off_url&enabled=true&urls=http://192.168.1.154:40565/67ed4bc7-fe39-4a6b-942d-3412c6c36d69/relay/0/off
2022-01-21T04:56:49.521610939+00:00 DEBUG Shelly Device Driver V1 Shelly R1 1 device thread event handled

57

FYI: The app is now showing the correct state when using the dumb switch.

2 Likes
58

I’m surprised because your log showed all url callback configure messages still failed ??

59

I think I see now why they failed; I’ll get a fix out in the morning. Thanks for all the logs. :+1:t3:

60

Hey. It’s working ok in Roller mode.
I would like to se the ‘main’ section on top.
At this moment ‘relay2’ is first listed.
See photo…

Screenshot_2022-01-21-09-02-26-57_ee29f370f755f274a0693481416ae4a8
Screenshot_2022-01-21-09-02-26-57_ee29f370f755f274a0693481416ae4a81080×2400 187 KB

Thanx! :wink:
Dusan

61

Making progress! I see it still says ‘unknown’ for the roller state. This is because it is not receiving updates back from the device. I am hoping that will be fixed in my next update.

Regarding the order of the fields, yes I should have mentioned that earlier. None of these devices have presentation definitions yet. I will create those once everything else is working and you are happy with the all the fields that are included. Then I will create the presentation definitions (i.e. 'device configurations) and the order will be corrected.