pimatic-bh1750 plugin available

---

Hello, I have now about 25m cable to the BH1750. And he works with it. I have tested it with 50m that was not working.

Hi. I use a 5m ethernet cable for the bh1750 sensor. Without problems.
For longer distances: do you think its better to have a well shielded cable or is it better to use a cable with stronger cable core (like the normal 220V light cable)?

@dk00000 Hi. I think CAT5 (or generally a shielded cable with low capacity) is the better choice. According to the following article up to 25m should work (in some cases even more with additional measures like separate powering). However, it should be also be noted that i2c has not been designed for long wires and more robust solutions exist for this purpose, e.g., CAN Bus.

See: http://electronics.stackexchange.com/questions/106265/maximum-i2c-bus-length

Hello,

I have try to use the bh-1750 plugin and connect the BH-1750 sensor to the raspberry but when i start pimatic i got an error:
error loading device my-sensor:failed to set address.
What have i done wrong?

Thanks gerrit.

@Thrusty said:

Hi, I have the bh1750 installed. The manual is a bit confusing because the values ​​are already filled in . But no matter .
The sensor now seems to be working . Unfortunately, it seems but just that. I just get the value 1280LUX displayed in pimatic. And nothing changes .

I have the same issue, the BH1750 shows always a value of 11000 Lux with or without the bridge between GND and ADD.
But the sensor and the wiring are correct. I have tested it with the python-skript on this site.
With the script the value was 1.333 without light and 3.666 with light on.

My config is the same as @Thrusty have:

{
      "id": "my-sensor",
      "name": "bh1750 example",
      "class": "BH1750Sensor",
      "device": "/dev/i2c-1",
      "address": "3x23",
      "interval": 10000
    },

Ok, I found the error:

I have changed the address from this:

"address": "3x23",

to:

"address": "0x23",

and it works

@mwittig said in pimatic-bh1750 plugin available:

@Jos-Hendriks Very nice! Two things, I would like to suggest:

• The sensor provides different resolution/sensitivity modes while “H-Resolution Mode” (1 lx, 120ms measurement time) seems to be activated by default (which is good). However, the device also provides a “H-Resolution Mode2” (0.5lx, 120ms) which might be interesting for some applications, e.g. in extreme low-light situations. Therefore, it would be nice to have a device configuration property to select the measurement mode. To get this mapped directly to the base driver, it should be named “command”. It may also be interesting to use the “Power Down after measurement” commands.
• As the sensor values may be inaccurate, it would be nice to be able add an “offset” value (value may be positive or negative decimal) to adjust the sensor value. This may be helpful for users who a have calibrated light meter to compare with.

Important requirement in my opinion. Sad to see that nothing happens since a year or so. I doesnt use the plugin because of this. I use my own python script to control the resolution.
Who could improve this plugin?
Cheers.

@dk00000 said in pimatic-bh1750 plugin available:

Sad to see that nothing happens since a year or so.

Maybe these points have been forgotten somehow. Thus, I have created issue tickets on the github project page to be able to discuss and track these feature requests in a more focussed manner.

https://github.com/circuitdb/pimatic-bh1750/issues/4

https://github.com/circuitdb/pimatic-bh1750/issues/5

Do this plugin working with Pimatic V9.xxx? In the list with the compatible plugins it is marked yellow.

@V1per said in pimatic-bh1750 plugin available:

Do this plugin working with Pimatic V9.xxx?

Yes. I’ve changed the document accordingly