BME280 & 4 x LTR-329ALS ?

[M*I*B]

Hello there from Germany...

...and at 1st excuse my ugly English pls... Hope I'm right here and also hope you can follow up what I write down here

I use ESPeasy since some weeks and I'm happy with it as it. Very well piece of software for dummys like me I use it on WeMOS and SONOFF in conjunction with FHEM...

But now I like to build something new to couple it with FHEM... As you can see in the topic I like to connect a BME280 and 4 (four) LTR-392 via I²C to a WeMOS. To couple it isn't the problem. All of the Chips has enough addresses that they don't have to fight together. But in the 2.0 I don't know how to implement them all together that I can catch the data with FHEM...

May someone like to help?

[M*I*B]

... ok then ...

[budman1758]

It does not look like the LTR-329ALS is supported. You might try to put a request for support on Github.
FHEM is a supported controller but I don't have any experience with it.

[Shardan]

Hello,

the LTR-329 is not supported by ESPEasy atm. As Budman758 said, maybe plae a feature request on github.

If it is possible to run more then one equal sensor same time depends on more then different I²C addresses.
This should be tested first. For example it is not possible to run two LCD or OLED displays same time on I²C.
Sometimes plugins don't like to be loaded twice or more....

Connecting ESPEasy to FHEM might be the easiest controller connection ESPEasy can offer.
If you use an up to date FHEM, the ESPEasy Bridge is already installed, it just needs to be defined.
Define the bridge, basically it's just one command:

Code: Select all

define MyEsp ESPEasy bridge 8383

MyEsp - just the name of your ESP bridge in FHEM
8383 - IP-Portnumber.
More command parameters are optionally possible as described in https://fhem.de/commandref.html#ESPEasy

Then open the Bridge in ESPEasy (shown in the menu on the left) and define an username and password for ESPEasy.
That's all with FHEM.

Open your ESPEasy device's webpage, set a controller to FHEM and set parameters (IP-Adress of FHEM-Box, Port, user and password).

And now: Just wait until your ESP-Device sends some data - it will be configured automatically in FHEM.

Regards
Shardan

[M*I*B]

@Shardan:
FHEM works well with it. There I have no problems anyway (ok, 1st try some things kick my ass but that's history), also not with the OLED- Display.

If it is possible to run more then one equal sensor same time depends on more then different I²C addresses.

Ouch! That's bad! Than ESPEasy is not the right one for my need ... Right?
I have to drive four (4) daylight-sensors (LTR... is death; OPT3001 is much better), the Bosch BME and maybe later the internal A/D twice. An other project needs to catch two RS232-TTL datastreams (9600,7,e,2).
May you have noticed that I'm ok in Hardware (I'm Layout-Designer (Altium) in MedTech developement) but extremly bad in Software. I²C is a system special to drive many devices on the same line; we use it often to create sensor-networks (ok, tripple secure due human live hangs on it...). But if that not working here I probably put on the wrong horse... If I'm right with that meaning?

[Shardan]

Honestly i never tried with multiple instances of same sensor plugin, that's why i said it should be tested.

Different sensors and one OLED works quite well, i'm running that for my room sensors (e. g. BME280, TSL-Luminosity and OLED Display).

I've tried to build a multi-display box: As soon as i use one plugin twice (2 x OLED, 2x framed OLED, 2x LCD) it fails,
Obviously the plugins interfere to eachother.

As said i don't have any experience with more then one I²C sensor if same sensor types are used,
maybe a breadboard test should be done before starting bigger projects.
As being old school hardware tech (started with apprenticeship as Radio/TV-Tech 40 years ago...) i don't have
programming knowledges sadly... Developing some nice hardware is more my street.

Regards
Shardan

[M*I*B]

As being old school hardware tech (started with apprenticeship as Radio/TV-Tech 40 years ago...) i don't have programming knowledges sadly... Developing some nice hardware is more my street.

Hey! Shake hands! Same my side... Born '62 and finnished my 1st 0-V-2 on a shoebox I was 12 (or 11 or 13...) years old and noticed 1st time that 280V DC is much more OUCH than 230V AC I'm more into Tubes(see radiomuseum.org) and analog then digital. All with less than 300V are babystuff

[Shardan]

*grins*
I can remember my first selfmade 144MHz power amplifier with a QQE 06/40 tube... 900V with BIG capacitor.....

(ex DD3QX)

[TD-er]

The BOSCH sensors BME/BMP280 might work together, as long as you change the I2C address on at least one of them to make them unique.
I have changed a number of those sensors (e.g. INA219) to be able to use more than one at the same time.
Those changes are in the MEGA branch.
I have not tested the BME/BMP ones in multi-setup. But I still have to look into the temp reading of them (I cannot believe the offset is always so far off) and will try them in multi setup.

[M*I*B]

@TD-er:
I do not need more than one BMx. A single of them is enough.
But what I need is to connect 4 of the OPT3001 Daylight- sensors. The OPT are much better then the LTR-392 or BH1750 and also have the posibility to use one of 4 adresses (see side 12 at http://www.ti.com/lit/ds/symlink/opt3001.pdf) that also don't fight with the adresses of the BMx ...

[HomeJCL]

Hi

I squeeze in with a related question, multiple sensor but of BME type

Tried last night to botch up a dT & dHR measurement.
2x BME280 with Ad hoc address (SDO GD and VC), both sensor come up in scan as 76 & 77 so far OK

Only 1 gives data and pressure is systematically wrong with values offset by -300 not so important for me, but second sensor does not give anything no T and no RH, further it seems that after a couple of minutes RH tends to slide lower and this morning I even saw also temp sliding.

Anyone tested this ? FW last MEGA 2/02/2018 (added BME280 with 6 pins type)

[TD-er]

I can have a look at it.
Do both sensors give proper values when used only one at a time?

If so, please add an issue on Github about it and we will have a look at it.

[HomeJCL]

Sorry for late answer,
Yes individually they are ok, have tested several, ordered a lot for project.

All tip top but as soon as setup together, both 76 and 77 are scanned, but only 1 comes up most visible is Pabs with +/- 300 subtracted
And second sensor gives all 0 values.

Will try tomorrow with different setups. Wemos & Lolin32

Tested : Mega & Node V3
For the record Noob everyone needs to start

[TD-er]

OK, could you add a Github issue about the BME280/BMP180 sensors not working together?
If you could, with some detailed information on what went wrong.

[HomeJCL]

Hi

Will redo test with several platforms to either pin down or confirm a general problem.
Want also to make sure I'm not the problem.

As soon as done will confirm here an open an issue.

Thanks

[HomeJCL]

Followup

Did test again tonight,

1 With DEV 20180206-, all OK both sensors detected and values seem correct, no interferences.

2 Reflashed DEV20180202, does not work with 2 sensors sees them on scan, but only 1 76 does give updates and values.

3 Back to DEV20180206 sensors come up also values again, with a long refresh but suppose it's a BME280

Conclusion latest DEV gives results and works as it should.
Only have 1 sensor with SDO to VCC the other floating or to GND both work.

Is the Github issue still needed ?

[TD-er]

Good you could test with the build made this morning.

There was some issue with the OLED library and I fixed that.
It was causing other issues as well.

[M*I*B]

I'm so brazen and write in my kidnapped thread ...

What do I have to do to somehow generate a chance to be able to nourish the daylight sensor OPT3001?

[TD-er]

Is the OPT3001 supported in the current code? (if so, by which plugin?)
Whether or not it is already supported, I would have to order a few of them to make them all work together in ESPeasy.

So I would suggest you create a Github issue, which is essentially a todo-list for me (or other devs) to support it

And please add as many information as you could on the current status and what you would like to have.

[M*I*B]

... nope, the OPT don't run at the moment (or I can't get it to work) ...

Github? I have heard about this but have no idea how to use it. I'm familiar with hardware (I'm PCB-designer) but a NOOB in software...

Datasheet of the OPT3001 is available here: http://www.ti.com/lit/ds/symlink/opt3001.pdf

Things that makes the OPT3001 my fav sensor are:

* four I²C addresses are selectable
* Can create an interrupt while grow min or max
* Free scaleable min and max border
* Autorange / Auto full scale setting
* Low current < 2µA
* Works from 1.6V to 3.6V
* 5.5V tolerant I/O
*** some much more ...

[TD-er]

OK: https://github.com/letscontrolit/ESPEasy/issues/830
And next time, please also add a link for me to buy the sensors

[M*I*B]

... shure But sometimes it helps to enter "OPT3001" at ePray

[TD-er]

They are already ordered, but the LTR-329ALS ones from the topic title are harder to find.

[M*I*B]

... that's true ... The LTR was my 1st choise before I fall over the OPT3001 ... So just for me the LTR is EOL at my side; I can't say who needs the LTR if they can use the OPT ... Do you?

[TD-er]

Well, the OPT3001 is on its way to my mailbox. The LTR's are not, so I guess those OPT sensors may have a head-start in being supported

[M*I*B]

... perfect

[M*I*B]

... what's about the OPT3001? Any news?

The whole project with the quad OPT3001 (and one BME280) have to placed on the roof... and summertime is the right time to plug it on. If the 1st frozen themperature comes up again it will be to dangerous jumping around of the roof ...

[TD-er]

... what's about the OPT3001? Any news?

The whole project with the quad OPT3001 (and one BME280) have to placed on the roof... and summertime is the right time to plug it on. If the 1st frozen themperature comes up again it will be to dangerous jumping around of the roof ...

Good to help remember me.
It should be there somewhere in the pile of sensors to add.
I should make a list....

[M*I*B]

I should make a list....

... if you get older a list is a very good idea .... believe me

[TD-er]

I should make a list....

... if you get older a list is a very good idea .... believe me

I'm not old... I'm almost at "level 42"....

Even my daughter of 4 is so nice to tell me I'm not old

Edit: Added the sensor to the (newly created) list...

[M*I*B]

... looks as if no more sow cares, just like to the matter with the O-LED (viewtopic.php?f=6&t=5472&p=31876#p31876) ...
That's a pity. I think the system is pretty good, but of course with this way of "support" you get the best OpenSouce software broken down quite quickly.

There is nothing left to do but switch to another system where support isn't a unknown word ...