python-ambee

Asynchronous Python client for the Ambee API

Explore on GitHub Read Hacker News discussions

3Distinct people

3Mentions

0Explicit recommenders

8GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Asynchronous Python client for the Ambee API

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour3 dated mentions

Observed mentions: 2021-06-14 17:49:50 UTC to 2021-06-14 18:14:33 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
Jun 14, 17:00	2021-06-14 17:00:00 UTC	2021-06-14 18:00:00 UTC	2	0	2
Jun 14, 18:00	2021-06-14 18:00:00 UTC	2021-06-14 19:00:00 UTC	1	0	1

What Hacker News says

3 sources

yongjik·Jun 14, 2021

Am I missing something, or is the project in question literally just one week old? https://pypi.org/project/ambee/#history https://github.com/frenck/python-ambee/commits/main

In “Please don't add any of my stuff to this project”

f311a·Jun 14, 2021

It's just a small dependency for Home Assistant. I don't think the author will receive a lot of reports. https://github.com/frenck/python-ambee The project has zero issues right now. I think that is not the real reason.

In “Please don't add any of my stuff to this project”

Zancarius·Jun 14, 2021

> (That’s not the issue here but it touches on the same challenge.) I don't think so. The "problem" here is that the author doesn't want nixos to repackage his library because he's concerned about a "support burden" imposed, presumably, by nixos users who might get confused and report issues to him instead of the packager. I can vaguely understand where he's coming from, but being as his library in question[1] doesn't even have a single issue submitted, I can't help but feel that the "support burden" is either a consequence of paranoia or an excuse to have his sources pulled from nixos. Worse, his package is being pulled--if I'm not mistaken--as a dependency of home-automation. So this is a totally different issue than yours. As the sibling poster said, once you license something under a FOSS license, your intentions are pretty clear. If

Read the rest

you don't want that to happen, pick a different (non-free?) license. Saying "this is open source, but I don't want $CLASS_OF_USER using it" no longer makes it open source by definition and thus no longer a free license. His solution is to release a new version distributed under a license denying repackaging of his code, which is one solution, but that's almost certainly going to cause his package to get forked from an earlier version (under MIT) or dropped from home-automation. Either way, this issue is going to get resolved, and I suspect it'll be resolved in a way he doesn't like. This should be a warning to anyone distributing under FOSS licenses: If you're squeamish about any vague possibility that someone, somewhere, might--maybe--post an issue on your issue tracker that has something to do with a use case you didn't plan, then you really ought to not distribute it under a FOSS license. [1] https://github.com/frenck/python-ambee/issues

In “Please don't add any of my stuff to this project”