HDC1080 Temp/Humidity sersor #418

Open
opened 2021-04-09 13:16:40 +01:00 by fx-host-assistant · 1 comment
fx-host-assistant commented 2021-04-09 13:16:40 +01:00 (Migrated from github.com)

Hello, great plugin! Thanks!
I have some HDC1080 Temp/Humidity sersors. They work perfectly on I2C bus, I can read both values (a simple python script here https://github.com/switchdoclabs/SDL_Pi_HDC1000), but I cannot use them with the plugin because it is not supported. No need to install anything else than what you already wrote for the i2c sensors. Could you please add it? They are more precise and reliable than SI7021 and don't over estimate the temp like BME280 plus I don't need to buy other sensors :-p
Many thanks for your help and I wish you fast recovery from your health problem.

Hello, great plugin! Thanks! I have some HDC1080 Temp/Humidity sersors. They work perfectly on I2C bus, I can read both values (a simple python script here https://github.com/switchdoclabs/SDL_Pi_HDC1000), but I cannot use them with the plugin because it is not supported. No need to install anything else than what you already wrote for the i2c sensors. Could you please add it? They are more precise and reliable than SI7021 and don't over estimate the temp like BME280 plus I don't need to buy other sensors :-p Many thanks for your help and I wish you fast recovery from your health problem.
wickedbeernut commented 2021-04-14 15:36:23 +01:00 (Migrated from github.com)

How about a temperature / humidity plugin for the plugin? In other words, rather than adding support for a new sensor, how about allowing the user to configure the path / filename of his / her Python script? The Python script would simply need to return the temperature and/or humidity in the prescribed format. This way the Enclosure plugin doesn't need to change with each new sensor. Periodically, the new Python scripts could be folded into the Enclosure plugin (along with the corresponding setup / menu selection) for others to leverage (without having to maintain their own local copy of the script). However, users wouldn't be blocked waiting for this update in order to take advantage of a new sensor.

How about a temperature / humidity plugin for the plugin? In other words, rather than adding support for a new sensor, how about allowing the user to configure the path / filename of his / her Python script? The Python script would simply need to return the temperature and/or humidity in the prescribed format. This way the Enclosure plugin doesn't need to change with each new sensor. Periodically, the new Python scripts could be folded into the Enclosure plugin (along with the corresponding setup / menu selection) for others to leverage (without having to maintain their own local copy of the script). However, users wouldn't be blocked waiting for this update in order to take advantage of a new sensor.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Gandalf/OctoPrint-Enclosure#418