search

jghaanstra / cloud.shelly

Homey app to control Shelly Cloud devices
GNU General Public License v3.0
21 stars 15 forks source link

Shelly 25 shutter up/down period homey bridge #179

Closed waynelaagewaard1 closed 1 year ago

waynelaagewaard1 commented 1 year ago

Well its too bad the bridge app suport app doesnt support offset. But the closest thing going up/down for a period doesnt work.

d02bcd45-842c-4848-ac08-76234e568d11

why is that or what am I doing wrong

wayne

jghaanstra commented 1 year ago

Well its too bad the bridge app suport app doesnt support offset.

This was removed from the app altogether quite some time ago as it wasnt working consistent for all users. You should be able to recreate that yourself with some complex flows but that's out of scope for me.

But the closest thing going up/down for a period doesnt work.

According to the docs the cloud API does not have a duration parameter so that might not work over cloud altogether. I'll ask Allterco Robotics if this is available.

But what does it do now? Does it not move at all or does it not respect the give duration? And what have you configured as max move time under the device settings @waynelaagewaard1

jghaanstra commented 1 year ago

It's confirmed by Allterco Robotics that's it's currently not available in the Cloud Control API but they will add it. I'll keep this open until it's confirmed to work.

jghaanstra commented 1 year ago

Ok. It actually was available on the cloud control API and i don't see anything wrong with the code.

Could you try again and create a new diagnostic report afterwards. What does the trigger card say. Does it show a successful green checkmark? And could you let me know the Shelly device ID as shown in the Shelly smartphone app or the Web UI of the device.

waynelaagewaard1 commented 1 year ago

Hoi Jelle

17782d7b-3b75-4769-9d78-175f7e657ad4

Wayne Laagewaard www.dynamicsguru.nlhttp://www.dynamicsguru.nl

Van: Jelger Haanstra @.> Verzonden: Tuesday, March 7, 2023 7:12:27 AM Aan: jghaanstra/cloud.shelly @.> CC: Wayne Laagewaard @.>; Mention @.> Onderwerp: Re: [jghaanstra/cloud.shelly] Shelly 25 shutter up/down period homey bridge (Issue #179)

Ok. It actually was available on the cloud control API and i don't see anything wrong with the code.

Could you try again and create a new diagnostic report afterwards. What does the trigger card say. Does it show a successful green checkmark? And could you let me know the Shelly device ID as shown in the Shelly smartphone app or the Web UI of the device.

— Reply to this email directly, view it on GitHubhttps://github.com/jghaanstra/cloud.shelly/issues/179#issuecomment-1457602515, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATUDDGO23HRAIA5673FV4W3W23GUXANCNFSM6AAAAAAVPPOLRU. You are receiving this because you were mentioned.Message ID: @.***>

jghaanstra commented 1 year ago

There is nothing in the log related to setting the roller. I also asked for the Shelly device ID as shown in the Shelly app or web ui. Could you post that here.

There is a strange other error in the log saying a device is not found. Did you recently remove a device from Homey Cloud?

stderr:
    513:28)
    at WebSocket.emit (node:domain:489:12)
    at Receiver.receiverOnMessage (/app/node_modules/ws/lib/websocket.js:1068:20)
    at Receiver.emit (node:events:513:28)
    at Receiver.emit (node:domain:489:12)
    at Receiver.dataMessage (/app/node_modules/ws/lib/receiver.js:517:14) {
  statusCode: 404
}
[ManagerDrivers] [Driver:shelly_cloud] [Device:86a20c48-dff3-4295-916c-ca559be30141] Trying to update capability measure_temperature with value 44.2 for (a channel of the) device 3494547c2424
[ManagerDrivers] [Driver:shelly_cloud] [Device:86a20c48-dff3-4295-916c-ca559be30141] Error: Not Found (MongoDB): Device with ID 86a20c48-dff3-4295-916c-ca559be30141
    at Remote Process
    at HomeyClient.emit (/homey-cloud-app-runner/node_modules/@athombv/homey-apps-sdk-v3/lib/HomeyClient.js:44:23)
    at Object.emit (/homey-cloud-app-runner/node_modules/@athombv/homey-apps-sdk-v3/manager/drivers.js:78:54)
    at Object.emit (/homey-cloud-app-runner/node_modules/@athombv/homey-apps-sdk-v3/lib/Driver.js:125:50)
    at /homey-cloud-app-runner/node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js:570:27
    at runMicrotasks ()
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async ShellyCloudDevice.updateCapabilityValue (/app/drivers/device.js:510:13)
    at ShellyCloudDevice.setCapabilityValue (/homey-cloud-app-runner/node_modules/@athombv/homey-apps-sdk-v3/lib/Device.js:562:23)
    at ShellyCloudDevice.updateCapabilityValue (/app/drivers/device.js:510:24)
    at ShellyCloudDevice.parseFullStatusUpdateGen1 (/app/drivers/device.js:757:14)
    at WebSocket. (/app/app.js:703:45)
    at WebSocket.emit (node:events:513:28)
    at WebSocket.emit (node:domain:489:12)
    at Receiver.receiverOnMessage (/app/node_modules/ws/lib/websocket.js:1068:20)
    at Receiver.emit (node:events:513:28)
    at Receiver.emit (node:domain:489:12)
    at Receiver.dataMessage (/app/node_modules/ws/lib/receiver.js:517:14) {
  statusCode: 404
}
waynelaagewaard1 commented 1 year ago

Jelger,

The device id was in the screenshot. But then my my question is how do i get the id

Wayne Laagewaard www.dynamicsguru.nlhttp://www.dynamicsguru.nl

Van: Jelger Haanstra @.> Verzonden: Tuesday, March 7, 2023 12:17:23 PM Aan: jghaanstra/cloud.shelly @.> CC: Wayne Laagewaard @.>; Mention @.> Onderwerp: Re: [jghaanstra/cloud.shelly] Shelly 25 shutter up/down period homey bridge (Issue #179)

There is nothing in the log related to setting the roller. I also asked for the device is. Could you post that here.

There is a strange other error in the log saying a device is not found. Did you recently remove a device from Homey Cloud?

stderr: 513:28) at WebSocket.emit (node:domain:489:12) at Receiver.receiverOnMessage (/app/node_modules/ws/lib/websocket.js:1068:20) at Receiver.emit (node:events:513:28) at Receiver.emit (node:domain:489:12) at Receiver.dataMessage (/app/node_modules/ws/lib/receiver.js:517:14) { statusCode: 404 } [ManagerDrivers] [Driver:shelly_cloud] [Device:86a20c48-dff3-4295-916c-ca559be30141] Trying to update capability measure_temperature with value 44.2 for (a channel of the) device 3494547c2424 [ManagerDrivers] [Driver:shelly_cloud] [Device:86a20c48-dff3-4295-916c-ca559be30141] Error: Not Found (MongoDB): Device with ID 86a20c48-dff3-4295-916c-ca559be30141 at Remote Process at HomeyClient.emit @./homey-apps-sdk-v3/lib/HomeyClient.js:44:23) at Object.emit @./homey-apps-sdk-v3/manager/drivers.js:78:54) at Object.emit @./homey-apps-sdk-v3/lib/Driver.js:125:50) at @./homey-apps-sdk-v3/lib/Device.js:570:27 at runMicrotasks () at processTicksAndRejections (node:internal/process/task_queues:96:5) at async ShellyCloudDevice.updateCapabilityValue (/app/drivers/device.js:510:13) at ShellyCloudDevice.setCapabilityValue @.***/homey-apps-sdk-v3/lib/Device.js:562:23) at ShellyCloudDevice.updateCapabilityValue (/app/drivers/device.js:510:24) at ShellyCloudDevice.parseFullStatusUpdateGen1 (/app/drivers/device.js:757:14) at WebSocket. (/app/app.js:703:45) at WebSocket.emit (node:events:513:28) at WebSocket.emit (node:domain:489:12) at Receiver.receiverOnMessage (/app/node_modules/ws/lib/websocket.js:1068:20) at Receiver.emit (node:events:513:28) at Receiver.emit (node:domain:489:12) at Receiver.dataMessage (/app/node_modules/ws/lib/receiver.js:517:14) { statusCode: 404 }

— Reply to this email directly, view it on GitHubhttps://github.com/jghaanstra/cloud.shelly/issues/179#issuecomment-1457991594, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATUDDGI4FI3DBJCSMV73TGTW24KMHANCNFSM6AAAAAAVPPOLRU. You are receiving this because you were mentioned.Message ID: @.***>

waynelaagewaard1 commented 1 year ago

Oh yes,

I had trouble using it from homey cloud and so i deleted it.

Bit this flow doesnt work at all, see attached screenshot

Wayne Laagewaard www.dynamicsguru.nlhttp://www.dynamicsguru.nl

Van: Wayne Laagewaard @.> Verzonden: Tuesday, March 7, 2023 12:57:49 PM Aan: jghaanstra/cloud.shelly @.>; jghaanstra/cloud.shelly @.> CC: Mention @.> Onderwerp: Re: [jghaanstra/cloud.shelly] Shelly 25 shutter up/down period homey bridge (Issue #179)

Jelger,

The device id was in the screenshot. But then my my question is how do i get the id

Wayne Laagewaard www.dynamicsguru.nlhttp://www.dynamicsguru.nl

Van: Jelger Haanstra @.> Verzonden: Tuesday, March 7, 2023 12:17:23 PM Aan: jghaanstra/cloud.shelly @.> CC: Wayne Laagewaard @.>; Mention @.> Onderwerp: Re: [jghaanstra/cloud.shelly] Shelly 25 shutter up/down period homey bridge (Issue #179)

There is nothing in the log related to setting the roller. I also asked for the device is. Could you post that here.

There is a strange other error in the log saying a device is not found. Did you recently remove a device from Homey Cloud?

stderr: 513:28) at WebSocket.emit (node:domain:489:12) at Receiver.receiverOnMessage (/app/node_modules/ws/lib/websocket.js:1068:20) at Receiver.emit (node:events:513:28) at Receiver.emit (node:domain:489:12) at Receiver.dataMessage (/app/node_modules/ws/lib/receiver.js:517:14) { statusCode: 404 } [ManagerDrivers] [Driver:shelly_cloud] [Device:86a20c48-dff3-4295-916c-ca559be30141] Trying to update capability measure_temperature with value 44.2 for (a channel of the) device 3494547c2424 [ManagerDrivers] [Driver:shelly_cloud] [Device:86a20c48-dff3-4295-916c-ca559be30141] Error: Not Found (MongoDB): Device with ID 86a20c48-dff3-4295-916c-ca559be30141 at Remote Process at HomeyClient.emit @./homey-apps-sdk-v3/lib/HomeyClient.js:44:23) at Object.emit @./homey-apps-sdk-v3/manager/drivers.js:78:54) at Object.emit @./homey-apps-sdk-v3/lib/Driver.js:125:50) at @./homey-apps-sdk-v3/lib/Device.js:570:27 at runMicrotasks () at processTicksAndRejections (node:internal/process/task_queues:96:5) at async ShellyCloudDevice.updateCapabilityValue (/app/drivers/device.js:510:13) at ShellyCloudDevice.setCapabilityValue @.***/homey-apps-sdk-v3/lib/Device.js:562:23) at ShellyCloudDevice.updateCapabilityValue (/app/drivers/device.js:510:24) at ShellyCloudDevice.parseFullStatusUpdateGen1 (/app/drivers/device.js:757:14) at WebSocket. (/app/app.js:703:45) at WebSocket.emit (node:events:513:28) at WebSocket.emit (node:domain:489:12) at Receiver.receiverOnMessage (/app/node_modules/ws/lib/websocket.js:1068:20) at Receiver.emit (node:events:513:28) at Receiver.emit (node:domain:489:12) at Receiver.dataMessage (/app/node_modules/ws/lib/receiver.js:517:14) { statusCode: 404 }

— Reply to this email directly, view it on GitHubhttps://github.com/jghaanstra/cloud.shelly/issues/179#issuecomment-1457991594, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATUDDGI4FI3DBJCSMV73TGTW24KMHANCNFSM6AAAAAAVPPOLRU. You are receiving this because you were mentioned.Message ID: @.***>

jghaanstra commented 1 year ago

What screenshots? There are no screenshots of the device ID or a flow in this Github issue. Dont reply through email but visit Github to add attachments.

waynelaagewaard1 commented 1 year ago

E9FF6754-2A14-4FB1-A46F-8C0EF6743C21

waynelaagewaard1 commented 1 year ago

3494547b9dea

jghaanstra commented 1 year ago

Ok, I think I found the issue. Will be fixed in the next release.

jghaanstra commented 1 year ago

Should be fixed with release 3.18.4 which is pending approval in the app store.