#First I have a temperature check for <
calm zealot
yeah, too new. better have a custom component for now. if that one gets lots of adoption, then it may make sense to move it to core
plush turtle
https://github.com/parob/homecast-hass seems like it already is one.
calm zealot
<https://github.com/parob/homecast-hass> seems like it already is one.
created yesterday too
plush turtle
The website looks quite good at least
ember canopy
Hmpf, I don't like my message quite yet
Hello 👋🏻,
So we discussed this PR in the core team and generally when we want to add an integration we want to make sure the product or service is available and is more established. We currently don't see this project as established yet and we encourage you to publish the integration as a custom integration for now.
I will close the PR for this reasoning
I feel like I need to point out why we think it's not established yet, but it's hard to do without making an accusation (we are now to a new domain, we have x users already)
-# cc @iron sleet as you're good with these kinda of messages
iron sleet
I think this service is a bad deal, period. I don't think we'll ever accept it. If users want to pay for accessing their devices away from home there are cheaper and better alternatives, like Home Assistant Cloud which works with all devices for Home Assistant.
ember canopy
True, but would you already slam the door closed for good right now? As in, we still don't really have documented any of this
iron sleet
I'd say that we don't think this service is a good fit to be in core, considering what it offers and the pricing.
While we do promote choice we also have a responsibility to curate the risk associated with built-in integrations. I think this falls under that.
ember canopy
I mean, in the end I don't think it could never make it. As in, you can also start out with zwave via smartthings. Doesn't have the cost, but it'd work, but we wouldn't block that either considering the size of smartthings + people could already be using it
marsh marten
