ArjanKranenburg / virtual-devices

Homey-app to add Virtual Devices that can trigger your flows.
Other
25 stars 17 forks source link

Feature request Time(Tekst) #155

Open ECort opened 2 years ago

ECort commented 2 years ago

Hi Arjan, It's clear that lot's of people are using your VD-app. As am I 😀. It really is perfect and forms the heart of almost all flows.

So here's another of the many feature request I'd like tot add. I'm measuring aircraft noise above our house. At the start of a 'quiet' period I register the 'time' wichtig a tekst field. It's an important time for me and it would be nice if I could show this in the dashboard screen using your 'device' feature like a 'sensor'.

No hurry and no urgency.

Thanks for all the work and your wunderfull app!

Kind regards, Eric Corten

ArjanKranenburg commented 2 years ago

Hi Eric,

Wow that is a very specific use-case. To manage the expectations, despite the "no hurry, no urgency" note, I don't see me working on this app anymore. Today, I've added a note to the readme to state the same and with some more explanations.

Thanks for the compliments and your idea. I will keep this open. It may inspire others.

/Arjan

ECort commented 2 years ago

Ha Arjan, Thanks for the reply. No problem at all. You’ve already delivered a very good app with lot’s of features 😀.

Just out of curiosity, may I ask why you will stop further development on your app?

Kind regards, Eric Corten

Van: Arjan Kranenburg @.> Verzonden: donderdag 26 mei 2022 10:39 Aan: ArjanKranenburg/virtual-devices @.> CC: ECort @.>; Author @.> Onderwerp: Re: [ArjanKranenburg/virtual-devices] Feature request Time(Tekst) (Issue #155)

Hi Eric,

Wow that is a very specific use-case. To manage the expectations, despite the "no hurry, no urgency" note, I don't see me working on this app anymore. Today, I've added a note to the readme to state the same and with some more explanations.

Thanks for the compliments and your idea. I will keep this open. It may inspire others.

/Arjan

— Reply to this email directly, view it on GitHubhttps://github.com/ArjanKranenburg/virtual-devices/issues/155#issuecomment-1138302832, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATEQTEL55HRCIK572GTKJGDVL42BVANCNFSM5WLJTJXQ. You are receiving this because you authored the thread.Message ID: @.**@.>>

ECort commented 2 years ago

Ha Arjan, Thanks for the reply. No problem at all. You’ve already delivered a very good app with lot’s of features 😀.

Just out of curiosity, may I ask why you will stop further development on your app? SORRY: Found it in your profile. Very clear :) ! Thanks for all the work done. Good luck with the other idea's :)

Kind regards, Eric Corten

ECort commented 2 years ago

Van: Eric Corten Verzonden: donderdag 26 mei 2022 13:09 Aan: ArjanKranenburg/virtual-devices @.***> Onderwerp: RE: [ArjanKranenburg/virtual-devices] Feature request Time(Tekst) (Issue #155)

Ha Arjan, Thanks for the reply. No problem at all. You’ve already delivered a very good app with lot’s of features 😀.

Just out of curiosity, may I ask why you will stop further development on your app? SORRY: Found the answer in your profile 😊

Kind regards, Eric Corten

Van: Arjan Kranenburg @.**@.>> Verzonden: donderdag 26 mei 2022 10:39 Aan: ArjanKranenburg/virtual-devices @.**@.>> CC: ECort @.**@.>>; Author @.**@.>> Onderwerp: Re: [ArjanKranenburg/virtual-devices] Feature request Time(Tekst) (Issue #155)

Hi Eric,

Wow that is a very specific use-case. To manage the expectations, despite the "no hurry, no urgency" note, I don't see me working on this app anymore. Today, I've added a note to the readme to state the same and with some more explanations.

Thanks for the compliments and your idea. I will keep this open. It may inspire others.

/Arjan

— Reply to this email directly, view it on GitHubhttps://github.com/ArjanKranenburg/virtual-devices/issues/155#issuecomment-1138302832, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATEQTEL55HRCIK572GTKJGDVL42BVANCNFSM5WLJTJXQ. You are receiving this because you authored the thread.Message ID: @.**@.>>