jghaanstra / cloud.shelly

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

Change request #196

Closed Mor003 closed 12 months ago

Mor003 commented 12 months ago

Two comments/request about adding Shelly devices to Homey Pro (early 2023)

  1. The device list is to limited (see screen shot). It's not possible to tell the devices apart cause you only show very limited info. Please expand the details about the devices or add a "view details" view. Device name and the full IP would be nice!

  2. On the Homey bridge you connect to the Shelly cloud, very convenient! Why is that option not available on the Homey Pro? (Bluetooth and wifi)

Screenshot_20230918_144116_Homey

jghaanstra commented 12 months ago

I have no control over how this list is displayed. You should ask Athom about this and/or contribute to this Github ticket.

https://github.com/athombv/homey-apps-sdk-issues/issues/257

Mor003 commented 12 months ago

Hi! I sent it to Athom first, they said the same thing you say "we have no control over this" ask the developer of the Shelly app :-)

Med vänlig hälsning,

Mats


Mats Rydsbo m: +46 701 43 73 70

Den ons 20 sep. 2023 kl 14:43 skrev Jelger Haanstra < @.***>:

I have no control over how this list is displayed. You should ask Athom about this and/or contribute to this Github ticket.

athombv/homey-apps-sdk-issues#257 https://github.com/athombv/homey-apps-sdk-issues/issues/257

— Reply to this email directly, view it on GitHub https://github.com/jghaanstra/cloud.shelly/issues/196#issuecomment-1727651138, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3JLG2JN5U2CWPBXQ5OVFVLX3LQHBANCNFSM6AAAAAA47ZI3JA . You are receiving this because you authored the thread.Message ID: @.***>

jghaanstra commented 12 months ago

Sure, that's Athoms default response.

  1. The device list is to limited (see screen shot). It's not possible to tell the devices apart cause you only show very limited info. Please expand the details about the devices or add a "view details" view. Device name and the full IP would be nice!

The names already hold the IP address but it's behind the ... dots due to a design choice by Athom of using tiles instead of a list and not being able to filter the device list. As mentioned I have not control over this UI or the functionality of the device list. Adding the friendly name of the device would require an extra query for every device discovered as this is not available in the mDNS message and due to performance reasons I did not implement that. It's added after pairing.

  1. On the Homey bridge you connect to the Shelly cloud, very convenient! Why is that option not available on the Homey Pro? (Bluetooth and wifi)

Because any serious home automation enthousiast should avoid using cloud for these kind of things. Next to that, there isnt very high demand for it as well.

Mor003 commented 12 months ago

Ok, thanks for the clarification. But that the IP is behind the "..." does not help much since you can't click/expand for more info. So if you have many devices with similar IPs its a pain to find the right one! But you say this is for Athom to fix? ¨

Thanks for quick answers!

Regards,

Mats


Mats Rydsbo m: +46 701 43 73 70

Den ons 20 sep. 2023 kl 16:58 skrev Jelger Haanstra < @.***>:

Sure, that's Athoms default response.

  1. The device list is to limited (see screen shot). It's not possible to tell the devices apart cause you only show very limited info. Please expand the details about the devices or add a "view details" view. Device name and the full IP would be nice! The names already hold the IP address but it's behind the ... dots due to a design choice by Athom of using tiles instead of a list and not being able to filter the device list.. Adding the friendly name of the device would require an extra query for every device discovered as this is not available in the mDNS message and due to performance reasons I did not implement that. It's added after pairing.

  2. On the Homey bridge you connect to the Shelly cloud, very convenient! Why is that option not available on the Homey Pro? (Bluetooth and wifi) Because any serious home automation enthousiast should avoid using cloud for these kind of things. Next to that, there isnt very high demand for it as well.

— Reply to this email directly, view it on GitHub https://github.com/jghaanstra/cloud.shelly/issues/196#issuecomment-1727901569, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3JLG2MZRR5ZMB6BLVCW3VLX3MACJANCNFSM6AAAAAA47ZI3JA . You are receiving this because you authored the thread.Message ID: @.***>

jghaanstra commented 12 months ago

The only thing I have control over in this screen is the name of the device. The name now holds the model, the unique identifier and the IP address of a device. That the IP address is being cut of is due to design choices made by Athom. The only thing I could do is add the IP address in front but that would not help since a lot of people have no idea what IP address their Shellies has. The solution is to redesign this screen into a list and/or allow for filtering. But that is out of my hands.

Mor003 commented 12 months ago

I will ask Athome, thanks!

/Mats


Mats Rydsbo m. +46701437370

Den ons 20 sep. 2023 17:31Jelger Haanstra @.***> skrev:

The only thing I have control over in this screen is the name of the device. The name now holds the model, the unique identifier and the IP address of a device. That the IP address is being cut of is due to design choices made by Athom. The only thing I could do is add the IP address in front but that would not help since a lot of people have no idea what IP address their Shellies has. The solution is to redesign this screen into a list and/or allow for filtering. But that is out of my hands.

— Reply to this email directly, view it on GitHub https://github.com/jghaanstra/cloud.shelly/issues/196#issuecomment-1727960037, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3JLG2L6PP6UQ5URVRLL7ADX3MD37ANCNFSM6AAAAAA47ZI3JA . You are receiving this because you authored the thread.Message ID: @.***>