u/CautiousAssumption39

Experiences with the Enphase Air Thermostat?

I'm considering buying the Enphase Air thermostat. It's expensive at $599. However, I've been using an Ecobee and it's not at all optimized for my setup.

I have a 30-panel Enphase system with 5 5p batteries. We installed a heat pump 18 months ago. We're in CA with PG&E.

The problem I've had for a long time is that Ecobee has no understanding that we have solar or batteries. So it's constantly trying to "optimize" based on PG&E rate schedules. But rate schedules are mostly irrelevant because our power is being pulled from our batteries, not from PG&E. Ecobee even defaults to "eco-mode" and makes it almost impossible to disable eco-mode.

So this seems like a great solution if it's well done. So my questions are things like: How smart is the AI in the system? Does it do a better job of optimizing based on panel generation and battery levels? Does it understand heat pumps well enough to optimize for them? Does it optimize based on utility rate schedules (but also understand battery storage levels as well)? Are there any downsides you've found with the thermostat?

Thanks!

reddit.com
u/CautiousAssumption39 — 2 days ago

Mitchum: Why is there scent in “unscented” product?

Did you think we wouldn’t smell it?

It smells!

I’ve returned it.

u/CautiousAssumption39 — 27 days ago
▲ 12 r/Slack+1 crossposts

Anyone found a way to configure Teams to work like Slack?

I've been trying, but finding many issues that seem impossible to overcome.

The capability in Slack I'm trying to replicate is:

  • Topic channels are open for anyone to join (or leave)
  • Channels are public by default
  • Anyone can browse public channels to find topics they care about and then join them.
  • When you join a public channel, you can see all history to get caught up on the topic
  • When you post in a channel, you can tag anyone (whether they have joined or not.)

The only workaround I've found is:

  • Create a large "team" in Teams with your whole company or macro team
  • Inside the team, you can create public channels
  • Problems with this approach:
    • Teams doesn't have a way of people "joining" certain channels. Everyone is automatically joined to every channel in the team. (what?!)
    • You're only able to tag people that are already in that team. If you want to tag someone from another part of the company, good luck. (Or they have to be added to the team).
    • There is no way to do a @ channel or @ here message that notifies everyone interested in that topic. Teams doesn't even allow you to use the @ Everyone tag in team channels.

Other problems I've found generally about Teams versus Slack:

  • Teams automatically creates a new "channel" for every meeting. So conversations sometimes continue in these ad-hoc channels, so you have important side conversations continuing in these meeting channels rather than consolidated in a topic channel.
  • A group chat in Teams can be given a name. This is OK, except they are always only private chats. Also... if you want to create a new chat with the same group of people, but a different topic, you can't. The topic is always defined by the people in the chat. (Makes no sense.)
  • Organization is a mess. The combination of Teams team channels, private chats, private chats that have been named, and "meeting" group chats seems like it's built for creating chaos if you're trying to understand where to talk about a topic.
  • You're only allowed to have conversation "threads" in team channels. Anytime you have a group chat (named or not named), Teams doesn't allow you to have conversation threads. The only thing available is "quote replies" where everything is in the main channel and conversations on sub topics are impossible to follow because their spread throughout the channel.

Has anyone run into these problems? Seen a good blog or video for how to solve this?

Thank you!

reddit.com
u/CautiousAssumption39 — 29 days ago