-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] the ability to build a similar interface to the Tasmota Admin interface #573
Comments
Take a look at: You can add this to Home Assistant via HACS. It exists both as an HA Add-On and also as a stand-alone App for Mac and Windows. I did a fair bit of work on it at the beginning of the year because I wanted to manage all my Shellys (50+) without depending on a cloud service that I can't control or secure. I asked Shelly support and a few YouTubers what they thought but there was little interest so I refocussed on other projects but could be persuaded back. |
MAN!!!
Max, this is AWESOME! I don’t know why nobody took it up sooner; I can only suspect that it was because of bandwidth on their part due to other commitments. But truly great, exactly what I was looking for, it shows all my devices and their firmware status. I will play around with it, and if I can think of anything that needs to be updated or changed, I will let you know.
Can I also suggest that this addon is not well published because I looked and looked and could not find anything that even hinted that this existed. This could also explain the lack of interest.
From: Max Lyth ***@***.***>
Sent: Sunday, 31 October 2021 11:52 PM
To: StyraHem/ShellyForHASS ***@***.***>
Cc: Tony Fitzsimmons ***@***.***>; Author ***@***.***>
Subject: Re: [StyraHem/ShellyForHASS] [FR] the ability to build a similar interface to the Tasmota Admin interface (#573)
Take a look at:
https://github.com/maxlyth/hassio-addons/tree/main/shelly-admin
You can add this to Home Assistant via HACS. It exists both as an HA Add-On and also as a stand-alone App for Mac and Windows.
I did a fair bit of work on it at the beginning of the year because I wanted to manage all my Shellys (50+) without depending on a cloud service that I can't control or secure. I asked Shelly support and a few YouTubers what they thought but there was little interest so I refocussed on other projects but could be persuaded back.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#573 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIE7PFIGZGTFZ2IG5SSABRDUJU3WNANCNFSM5CTW26SA>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
nice interface |
Wow, super impressive what @maxlyth has done. Why is that not part of the standard supervisor add ons? I wasn't even aware that you can define additional repositories. |
Thanks for the positive responses. I had a few PMs including a question about password protected devices and this is supported (both on a global password and per-device password level) but not in the release version. The Shelly connection library I used did not work for authentication (and other random reliability) so I ended up having to re-write that from the ground up. I applaud anyone that recognises the importance of IoT security but I also realise that this appeals to a minority of the audience so it is only currently in the development branch of the code on Github. More code means potentially new bugs and without testers I did not want to release it. People have asked why I did not publicise this more but I got the brush-off from Shelly at beta release. I was only after early access to new graphics and meta-data schemas so I could magically make them look great to new customers when they got their shiny new products but I think Shelly want to promote their cloud solution while paying lip-service to open standards, eg MQTT. Don't get me wrong, I have a big investment in Shelly, hence the work on this admin product but it seems the majority think having Amazon listen to their private conversations is acceptable so I can't blame Shelly for going that way. I use much more recent code for myself but that is to save me time and there have been no Github commits from me for 6 months. I really hoped that there would be interest back in early 2021 but I got distracted on commercial projects. I don't need endorsement from Shelly but public releases are much harder than coding for myself so if anyone can help then I can share what I have. |
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
one of the more frustrating things when looking for devices on your network is that its not straight forward to indentify the device on your network, articulalrly if the device is not reporting to Home assitant a name that makes secnce to a human like "hallway light" but rather "Shelly 1 - BA0408" one solutioin to this chalange would be to be able to build a lovelace page that has all the relevent information about the chally device in one place, along with a clickable link to the device IP address. if you take a look at the screenshot on this page https://github.com/hassio-addons/addon-tasmoadmin you can get the idea of what I am talking about. the tasmoadmin page has all the information about all your tasmota flashed devices in one place. it would be nice to have the same thing for Shelly as they are a much better device to bigin with.
Describe alternatives you've considered
the only way I have been able to work out a work around id to use Node Red to build a dashboard of all my shelly devices, but this is not dynamic and needs to be updated every time I add more devices, it would be good to be able to have a page that works like the tasmotadmin page which automaticlay populates with all of your Shelly devices. I have tried to build it in Lovelace, however the IP address is nested deeply in the paramiters so its not that easy to present as a clickable link. this is realy what I am looking for. the ability to click on a link and open the page for the device its self.
Additional context
here is an other screenshot just to help make it more clear.
The text was updated successfully, but these errors were encountered: