TSL2561 not working Version 5.11.1 (Sonoff TH16) #1644

joopy · 2018-01-19T20:24:18Z

Hi I don't get a TSL2561 to work. I'm using GPIO 4 en GPIO 14

@ console

21:20:53 CMD: I2Cscan
21:20:53 MQT: stat/sonoffTH16-2/RESULT = {"I2CScan":"Device(s) found at 0x39"}

Anyone got a clue?

joopy · 2018-01-19T20:55:54Z

#define USE_TSL2561 // Add I2C code for TSL2561 sensor using library Adafruit TSL2561 Arduino (+1k2 code)

user_config.h

totally forgot that one...

joopy · 2018-01-19T21:02:30Z

TSL2561 Illuminance	0 lx

A little further, but it keeps on 0 lx?

joba-1 · 2018-02-03T23:35:34Z

I had the same learning curve (didn't know I need to #define USE_TSL2561 and when I did, I got 0 lx).

My sensor has a floating address bit, So it should be found at 0x39. And the following code snippet does so in a separate sketch on a nodemcu (and reports proper lx after that);

Wire.beginTransmission(0x39); if( Wire.endTransmission() == 0 ) Serial.print("found");
Tasmota reports always as 0x29, no matter if I set address bit to low, float or high.

lowvolt2 ESP-I2C: TSL2561 found at 0x29

for me it looks like boolean TSL2561::begin(void) has a problem. It probably should check result of Wire.endTransmission().

joba-1 · 2018-02-03T23:38:30Z

Hm, I set the address bit to low to actually make the sensors address 0x29. But still no joy.

joopy · 2018-02-04T12:22:12Z

Thnx Joba, for now I give up. I'm not so into coding, so I will wait for someone to fix it. Mayby Arendst can help out.

Merdeka · 2018-02-04T14:48:33Z

There seems to be a problem with the for loop in xsns_16_tsl2561:

for (byte i = 0; i < sizeof(tsl2561_addresses); i++) {
    tsl2561_address = tsl2561_addresses[i];
    tsl = new TSL2561(tsl2561_address);
    if (tsl->begin()) {
      tsl->setGain(TSL2561_GAIN_16X);
      tsl->setTiming(TSL2561_INTEGRATIONTIME_101MS);
      tsl2561_type = 1;
      snprintf_P(log_data, sizeof(log_data), S_LOG_I2C_FOUND_AT, "TSL2561", tsl2561_address);
      AddLog(LOG_LEVEL_DEBUG);
      break;
    }
  }

It only runs once and tries to start the tsl with address 0x29.
When I change the line tsl = new TSL2561(tsl2561_address); to tsl = new TSL2561(TSL2561_ADDR_FLOAT); my tsl starts working as it is on address 0x39.

joopy · 2018-02-04T19:28:04Z

So we need to change that line off code and recompile?

arendst · 2018-02-04T19:39:50Z

The problem is in the Adafruit library which fails to report a not present device. The solution above is a workaround to use a fixed address of TSL2561_ADDR_FLOAT bypassing other possible addresses.

If @Merdeka gets it to function with the float address then why can't @joba-1 get it to work with the default low address? Perhaps @Merdeka could try with the low address too. If it works I will just settle for a fixed low/float/high address. You may decide.

NB. I do not own a TSL2561 (there are other device providing luminosity) so I can't test.

joba-1 · 2018-02-04T23:25:21Z

Hi,
Not sure why it didnt work with low address, but this lib change makes autodetect work for me:

diff -u Sonoff-Tasmota-5.11.1/lib/TSL2561-Arduino-Library/TSL2561.cpp Sonoff-Tasmota-5.11.1.tsl2561/lib/TSL2561-Arduino-Library/TSL2561.cpp 
--- Sonoff-Tasmota-5.11.1/lib/TSL2561-Arduino-Library/TSL2561.cpp       2018-01-07 22:45:40.000000000 +0100
+++ Sonoff-Tasmota-5.11.1.tsl2561/lib/TSL2561-Arduino-Library/TSL2561.cpp       2018-02-04 18:06:30.559187730 +0100
@@ -63,7 +63,9 @@
 #else
   Wire.send(TSL2561_REGISTER_ID);
 #endif
-  Wire.endTransmission();
+  if( Wire.endTransmission() != 0 ) {
+    return false;
+  }
   Wire.requestFrom(_addr, 1);
 #if ARDUINO >= 100
   int x = Wire.read();

arendst · 2018-02-05T11:43:28Z

Without changing the library could anyone please test if the following change in xsns_16_tsl2561.ino also works.

Pls replace from line 47:

      tsl = new TSL2561(tsl2561_address);
      if (tsl->begin()) {
        tsl->setGain(TSL2561_GAIN_16X);
        tsl->setTiming(TSL2561_INTEGRATIONTIME_101MS);
        tsl2561_type = 1;
        snprintf_P(log_data, sizeof(log_data), S_LOG_I2C_FOUND_AT, "TSL2561", tsl2561_address);
        AddLog(LOG_LEVEL_DEBUG);
        break;
      }

to

    if (I2cDevice(tsl2561_address)) {
      tsl = new TSL2561(tsl2561_address);
      if (tsl->begin()) {
        tsl->setGain(TSL2561_GAIN_16X);
        tsl->setTiming(TSL2561_INTEGRATIONTIME_101MS);
        tsl2561_type = 1;
        snprintf_P(log_data, sizeof(log_data), S_LOG_I2C_FOUND_AT, "TSL2561", tsl2561_address);
        AddLog(LOG_LEVEL_DEBUG);
        break;
      }
    }

joba-1 · 2018-02-05T16:30:58Z

Did some more research digging in the datasheet of the TSL2561.

It seems, to get a valid value from the chip, the command bit (0x80) has to be set in addition to the register itself (0x0a). An example in the current driver can be found e.g. in the enable() method.

If I dont do that, I get no valid values, just a reflection of the register number.
E.g. if I just send TSL2561_REGISTER_ID (0x0A), i always get back TSL2561_REGISTER_ID (0x0A) again.
But if I send TSL2561_REGISTER_ID | TSL2561_COMMAND_BIT, then I get 0x50, at least if I wait long enough. For some time after powering up I get just 0x00.
I don't know why I get 0x50 and not 0x10 like described in the datasheet, but in the sparkfun driver example, also 0x5x is mentioned as expected value (without giving a reason for that).
My fix above, check address but not the id register (removing the check if (x & 0x0A) ...) seems to be the safest way to make it work.

That said: why only check for sensors on startup? The bus allows plugging them in and out any time...

joba-1 · 2018-02-05T16:33:16Z

Didnt see your test request, will check...

joba-1 · 2018-02-05T17:05:25Z

I can confirm, it works. Great! Here is the startup log:

2018-02-05T17:48:44.238288+01:00 lowvolt2 ESP-DOM: idx 14, nvalue 0
2018-02-05T17:48:50.043828+01:00 lowvolt2 ESP-SHT: Sensor did not ACK command
2018-02-05T17:48:50.084088+01:00 lowvolt2 ESP-I2C: TSL2561 found at 0x39
2018-02-05T17:48:51.049465+01:00 lowvolt2 ESP-MQT: tele/lowvolt2/STATE = {"Time":"2018-02-05T17:48:51","Uptime":0,"Vcc":3.357,"POWER1":"OFF","POWER2":"OFF","Wifi":{"AP":1,"SSId":"job.fritz.ssid","RSSI":78,"APMac":"00:18:39:C6:B6:32"}}
2018-02-05T17:48:51.156817+01:00 lowvolt2 ESP-MQT: domoticz/in = {"idx":13,"nvalue":0,"svalue":"65535"}
2018-02-05T17:48:51.160378+01:00 lowvolt2 ESP-MQT: tele/lowvolt2/SENSOR = {"Time":"2018-02-05T17:48:51","TSL2561":{"Illuminance":65535}}

As you can see, the driver has a bug (it checks for negative unsigned variable :) ). This results in 65535lx although it is very dark.
Two questions: the driver you use is obsolete. Why are you using the obsolete driver? There is a new version on github. And it might be even more compact because it reuses the adafruit sensor lib now.
Unfortunately this driver still has the same bug, but it might be easier to get it fixed there.
Would you mind switching to the new driver?

joba-1 · 2018-02-05T17:09:40Z

Btw. here is the fix (including the actually working id check):

--- Sonoff-Tasmota-5.11.1/lib/TSL2561-Arduino-Library/TSL2561.cpp       2018-01-07 22:45:40.000000000 +0100
+++ Sonoff-Tasmota-5.11.1.tsl2561-works/lib/TSL2561-Arduino-Library/TSL2561.cpp 2018-02-05 17:01:46.853477179 +0100
@@ -54,16 +54,21 @@
 }
 
 boolean TSL2561::begin(void) {
+  // Initialise I2C
   Wire.begin();
 
- // Initialise I2C
+  // Check if someone listens at _addr
   Wire.beginTransmission(_addr);
 #if ARDUINO >= 100
-  Wire.write(TSL2561_REGISTER_ID);
+  Wire.write(TSL2561_COMMAND_BIT | TSL2561_REGISTER_ID);
 #else
-  Wire.send(TSL2561_REGISTER_ID);
+  Wire.send(TSL2561_COMMAND_BIT | TSL2561_REGISTER_ID);
 #endif
-  Wire.endTransmission();
+  if( Wire.endTransmission() != 0 ) {
+    return false;
+  }
+
+  // Check if we are actually talking to a TSL2561
   Wire.requestFrom(_addr, 1);
 #if ARDUINO >= 100
   int x = Wire.read();
@@ -71,7 +76,7 @@
   int x = Wire.receive();
 #endif
   //Serial.print("0x"); Serial.println(x, HEX);
-  if (x & 0x0A ) {
+  if ( (x & 0xF0) == 0x50 ) {
     //Serial.println("Found TSL2561");
   } else {
     return false;
@@ -194,17 +199,18 @@
     {b=TSL2561_LUX_B8T; m=TSL2561_LUX_M8T;}
 #endif
 
-  unsigned long temp;
-  temp = ((channel0 * b) - (channel1 * m));
+  // Calculate luminosity of full light and ir-only channel in lux according to datasheet
+  channel0 *= b;
+  channel1 *= m;
 
-  // do not allow negative lux value
-  if (temp < 0) temp = 0;
+  // Only consider non-ir luminosity, avoid overflow
+  uint32_t lux = (channel0 > channel1) ? channel0 - channel1 : 0;
 
   // round lsb (2^(LUX_SCALE-1))
-  temp += (1 << (TSL2561_LUX_LUXSCALE-1));
+  lux += (1 << (TSL2561_LUX_LUXSCALE-1));
 
   // strip off fractional portion
-  uint32_t lux = temp >> TSL2561_LUX_LUXSCALE;
+  lux >>= TSL2561_LUX_LUXSCALE;
 
   // Signal I2C had no errors
   return lux;

5.11.1i * Fix some Energy Monitoring related issues (#1677) * Fix TSL2561 device detection (#1644) * Fix command PWM response if no PWM channel is configured (#1783)

joopy · 2018-02-06T12:25:42Z

Just flashed 5.11.1i on the sonoff TH16, I now get

TSL2561 Illuminance | 10708 lx

The chip itself can go up to 40,000 Lux
But when i put it in direct sunlight it goes to 0? Is there a max in the softwarecode?

joba-1 · 2018-02-06T15:33:38Z

You made me wonder. I checked the code and datasheet:

The code simply uses getLuminosity() which returns raw sensor data, not lux!

I'll try to fix this...

joba-1 · 2018-02-06T16:08:26Z

If you want to check:

In file Sonoff-Tasmota-5.11.1/sonoff/xsns_16_tsl2561.ino change the line (around no 70)

uint16_t illuminance = tsl->getLuminosity(TSL2561_VISIBLE);

to

uint32_t light = tsl->getFullLuminosity();
light = tsl->calculateLux(light & 0xFFFF, light >> 16);
uint16_t illuminance = (light > 0xFFFF) ? 0xFFFF : (uint16_t)light;

It compiles and shows a value for me that seems to make sense. But I have no equipment to verify correctnes.

joopy · 2018-02-06T19:37:40Z

Yes joba-1 output is much more what i expected:

20:30:01 MQT: tele/sonoffTH16-2/SENSOR = {"Time":"2018-02-06T20:30:01","TSL2561":{"Illuminance":13}} (light out / only monitor light)
20:35:04 MQT: tele/sonoffTH16-2/SENSOR = {"Time":"2018-02-06T20:35:04","TSL2561":{"Illuminance":95}} (light on semi direct light)

So yeah I think this is working!

joba-1 · 2018-02-07T10:05:50Z

It is working better, but not good yet.

I sometimes get 0xffffffff from getFullLuminosity() raw value. Due to overflow in calculations within calculateLux() this results in 95lx. It should probably return an easily identifiable error value like 0xffffffff.
@arendst: Is there a convention for a sensor value in tasmota that says "value not valid"?

Then, when raw brightness of visible + ir light rises above ~0x8000, it beginns to stall while the ir part still rises, until both values are equal at 0x90cc, resulting in calculated 54lx. Tested with a bright smartphone led, not sunlight.

There is a define in the driver that changes lux calculations a bit (I think ~10-20%). I don't know how to determine which of the 2 variants is right for my chip.

All those are not tasmota errors, but tsl2561 driver errors.
I see there is some clipping and auto gain done in the newer version of the adafruit lib. I plan to try this out. Then there is a sparkfun lib, dont know if it is any better.

@arendst: Getting a reading with auto gain and integration time could take a second (maybe even a bit more). Would that be an acceptable response time for tasmota or should a "driver" do continuous readings so it has a proper value ready when asked for? The chip only uses 0.24mA typical when powered on, so that doesnt really matter compared to what the esp needs with active wlan.

Finally: I don't insist in using that chip. I just liked, I can read ir and normal light because in the end this might enable me to differ light sources (sun, led, ...). Anyone has a suggestion for an alternative?

arendst · 2018-02-07T11:11:20Z

Current value not valid policy is do not display or keep it for up to 10 teleperiod reads then drop display.

I prefer reading time as low as possible. If driver can kick device to start processing, then back off and connects after a second again to read value that's fine with me.

joba-1 · 2018-02-08T16:43:31Z

to round this up here:

The mystery about the two sets of parameters for lux calculation and the chip id 0x50 vs 0x10 are solved:
According to the newer datasheet (not the one adafruit links to, but this one, page 18: http://html.alldatasheet.com/html-pdf/560746/AMSCO/TSL2561/2958/19/TSL2561.html) 0x1? is the CS package and 0x5? the other ones. So one can choose the correct parameter set dynamically (not with #defines).
the programming error that checks for less than zero of an unsigned variable is already in the manufacturers example code - very reassuring :)
My pull request with the fix for the lux calculation is already in the dev branch. Thanks Theo! I plan to improve that with the new infos

5.12.0 20180209 * Change library PubSubClient.h define MQTT_MAX_PACKET_SIZE from 512 to 1000 for Home Assistant support * Change relation of define MESSZ being dependent on PubSubClient.h define MQTT_MAX_PACKET_SIZE * Change command color parameter input checks to less strict for Home Assistant support * Change command Ina219Mode into command Sensor13 * Change commands HlwPCal, HlwUCal and HlwICal to PowerCal, VoltageCal and CurrentCal to be used for both Pow and S31 calibration * Change commands HlwPSet, HlwUSet and HlwISet to PowerSet, VoltageSet and CurrentSet to be used for both Pow and S31 calibration * Change uptime from hour to second resulting in a display of 123T13:45:21 where 123 is days * Change module name Wemos D1 mini into Generic (#1220) * Change HTML from width=100% to style=width:100% supporting HTML5 (#1358) * Change OSWATCH_RESET_TIME (Blocked loop) from 30 to 120 seconds to allow slow networks (#1556) * Change WIFI_MANAGER_SEC into WIFI_CONFIG_SEC (#1616) * Change function pointers code to save code space and memory (#1683) * Change webserver argument processing gaining 5k code space (#1705) * Change weblog memory usage (#1730, #1793, #1819) * Update TasmotaSerial library to 1.1.0 * Update language files Italian (#1594), Dutch (#1723) and Spanish (#1722) * Fix Non-English JSON temperature unit attachement * Fix Arilux RF induced exception by moving interrupt handler to iram on non ESP8266/Arduino lib v2.3.0 * Fix truncated command names and wrong response for DomoticzSwitchIdx (#1571) * Fix %-sign issue as printf escape character in Humidity and Sonoff SC (#1579) * Fix DS18B20 temperature JSON decimal dot (#1561) * Fix Energy JSON message (#1621) * Fix IRSend parameter translation (#1636) * Fix TSL2561 device detection (#1644, #1825) * Fix BME680 teleperiod resistance measuring (#1647) * Fix Energy Monitoring Energy Today and Energy Total reading after restart (#1648) * Fix IRReceive Data value (#1663) * Fix Energy Monitoring Energy Period roll-over (#1688) * Fix compiler warnings (#1774) * Fix command PWM response if no PWM channel is configured (#1783) * Add locale Decimal Separator to Web sensor page * Add ColorTemperature to light status message * Add command PowerOnState option 5 which inverts PulseTime and allows for delayed always on after power on * Add OtaMagic two step Web server OTA upgrade using filename-minimal image if OTA free space is too small * Add support for PMS5003 and PMS7003 particle concentration sensor * Add command SetOption21 1 to allow Energy Monitoring when power is off on Sonoff Pow and Sonoff S31 (#1420) * Add Chinese language file (#1551) * Add French language file (#1561) * Add Spanish language file (#1589) * Add HTTP Allow Cross Origin removed from ESP8266/Arduino lib v2.4.0 (#1572) * Add Home Assistant MQTT Discovery for switch and light to be enabled by command SetOption19 1 (#1534) or define HOME_ASSISTANT_DISCOVERY_ENABLE in user_config.h (#1685) * Add command State to retrieve device state information (same data as teleperiod state and status 11 in slightly different JSON format) * Add optional login to Webserver AP mode (#1587, #1635) * Add command Sensor15 2 to start MHZ19(B) Zero Point Calibration (#1643) * Add support for Sonoff S31 Smart Socket with Power Consumption Detection (#1626) * Add command SetOption20 to allow update of Dimmer/Color/Ct without turning power on (#1719, #1741) * Add NTP sync time slot based on chip id (#1773) * Add cursor pointer to web button (#1836)

joopy · 2018-02-10T09:22:45Z

Just flashed my Sonoff Th16 with firmware 5.12a with TSL2561 plugged in I got following error.

00:00:00 Project sonoffth16-2 Sonoff (Topic sonoffTH16-2, Fallback DVES_0DD48D, GroupTopic sonoffs) Version 5.12.0a
00:00:00 WIF: Connecting to AP2 amor in mode 11N as sonoffTH16-2-5261...
00:00:06 WIF: Connected
00:00:06 DNS: Initialized
00:00:06 HTP: Web server active on sonoffTH16-2-5261.local with IP address 192.168.0.94
10:17:21 MQT: Attempting connection...
10:17:23 MQT: Connected
10:17:23 MQT: tele/sonoffTH16-2/LWT = Online (retained)
10:17:23 MQT: cmnd/sonoffTH16-2/POWER =
10:17:23 MQT: tele/sonoffTH16-2/INFO1 = {"Module":"Sonoff TH","Version":"5.12.0a","FallbackTopic":"DVES_0DD48D","GroupTopic":"sonoffs"}
10:17:23 MQT: tele/sonoffTH16-2/INFO2 = {"WebServerMode":"Admin","Hostname":"sonoffTH16-2-5261","IPAddress":"192.168.0.94"}
10:17:23 MQT: tele/sonoffTH16-2/INFO3 = {"RestartReason":"Fatal exception:3 flag:2 (EXCEPTION) epc1:0x4022d46a epc2:0x00000000 epc3:0x00000000 excvaddr:0x40269f20 depc:0x00000000"}
10:17:23 MQT: homeassistant/switch/sonoffTH16-2/config = (retained)
10:17:24 MQT: stat/sonoffTH16-2/RESULT = {"POWER":"ON"}
10:17:24 MQT: stat/sonoffTH16-2/POWER = ON
10:17:25 MQT: stat/sonoffTH16-2/RESULT = {"POWER":"ON"}
10:17:25 MQT: stat/sonoffTH16-2/POWER = ON

Joba his fix:
In file Sonoff-Tasmota-5.11.1/sonoff/xsns_16_tsl2561.ino change the line (around no 70)

Was working fine for me.

arendst · 2018-02-10T09:40:30Z

Strange as his fix should be in the latest versions too. Can you verify if that's the case?

joopy · 2018-02-10T10:28:42Z

Arend around line 70 in xsns_16_tsl2561.ino

There is no such thing as:

uint32_t light = tsl->getFullLuminosity();
light = tsl->calculateLux(light & 0xFFFF, light >> 16);
uint16_t illuminance = (light > 0xFFFF) ? 0xFFFF : (uint16_t)light;

arendst · 2018-02-10T10:30:40Z

See #1825

joopy · 2018-02-11T17:33:52Z

Thnx Arend, however it's not working for me. Joba is latest firmware working for you?

joba-1 · 2018-02-11T18:16:48Z

Hi joopy, sorry, have not checked yet, only a patched 5.11.1. And that worked fine. It could take a little time until I can test this. Currently I work on my own Tsl2561 library. If we really want to use the chip, we will need automatic gain, and maybe more accuracy than 1 lux. Most is already done. Tipps welcome. See https://github.com/joba-1/Joba_Tsl2561 if you like. joopy <notifications@github.com> schrieb am So. 11. Feb. 2018 um 18:33:

Thnx Arend, however it's not working for me. Joba is latest firmware working for you? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1644 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ae8n-h8ObPnpvbzNiL6e2a2FtOQIekkGks5tTySEgaJpZM4RlAR0> .

-- iphone so i typo

joopy · 2018-02-12T16:08:35Z

Thnx Joba,

Looking forward. For now I will wait for a fix no hurry. When your library is finished it will be implemented in Tasmota?

joba-1 · 2018-02-20T01:14:30Z

Hi @joopy, Theo was so kind to accept my pull request #1951 and add it to 5.12.0b with commit ecfa14d already. It works fine for me. Maybe you can test this, too? Just make sure to comment out #define USE_TSL2561 and uncomment the #define USE_TSL2561_JOBA instead.

Btw. you know it is actually using my lib if you see milliLux accuracy.

joopy · 2018-02-20T11:47:54Z

Hi @joba-1 I can confirm it's working. Thnx for your effort! And @arendst for adding!

12:45:43 MQT: tele/sonoffTH16-2/SENSOR = {"Time":"2018-02-20T12:45:43","TSL2561":{"Illuminance":2623.772}}

arendst · 2018-02-20T13:00:46Z

In that case I will remove the original driver and make jobas the standard one. Thnx for your support

5.12.0b * Change TSL2561 driver to joba library and delete Adafruit library (#1644)

joopy · 2018-03-01T18:09:15Z

Is working fine a few weeks now can be closed.

5.11.1i * Fix some Energy Monitoring related issues (arendst#1677) * Fix TSL2561 device detection (arendst#1644) * Fix command PWM response if no PWM channel is configured (arendst#1783)

5.12.0b * Change TSL2561 driver to joba library and delete Adafruit library (arendst#1644)

arendst added a commit that referenced this issue Feb 6, 2018

v5.11.1i - Fixes Energy, PWM and Tsl2561

0d6275f

5.11.1i * Fix some Energy Monitoring related issues (#1677) * Fix TSL2561 device detection (#1644) * Fix command PWM response if no PWM channel is configured (#1783)

arendst added a commit that referenced this issue Feb 20, 2018

v5.12.0b - Consolidate TSL2561 driver

6b3584e

5.12.0b * Change TSL2561 driver to joba library and delete Adafruit library (#1644)

joopy closed this as completed Mar 1, 2018

curzon01 pushed a commit to curzon01/Tasmota that referenced this issue Sep 6, 2018

v5.12.0b - Consolidate TSL2561 driver

639671c

5.12.0b * Change TSL2561 driver to joba library and delete Adafruit library (arendst#1644)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

TSL2561 not working Version 5.11.1 (Sonoff TH16) #1644

TSL2561 not working Version 5.11.1 (Sonoff TH16) #1644

joopy commented Jan 19, 2018

joopy commented Jan 19, 2018

joopy commented Jan 19, 2018

joba-1 commented Feb 3, 2018 •

edited

Loading

joba-1 commented Feb 3, 2018

joopy commented Feb 4, 2018

Merdeka commented Feb 4, 2018 •

edited

Loading

joopy commented Feb 4, 2018

arendst commented Feb 4, 2018 •

edited

Loading

joba-1 commented Feb 4, 2018 •

edited

Loading

arendst commented Feb 5, 2018 •

edited

Loading

joba-1 commented Feb 5, 2018

joba-1 commented Feb 5, 2018

joba-1 commented Feb 5, 2018 •

edited

Loading

joba-1 commented Feb 5, 2018

joopy commented Feb 6, 2018 •

edited

Loading

joba-1 commented Feb 6, 2018

joba-1 commented Feb 6, 2018 •

edited

Loading

joopy commented Feb 6, 2018

joba-1 commented Feb 7, 2018

arendst commented Feb 7, 2018

joba-1 commented Feb 8, 2018

joopy commented Feb 10, 2018

arendst commented Feb 10, 2018

joopy commented Feb 10, 2018

arendst commented Feb 10, 2018

joopy commented Feb 11, 2018

joba-1 commented Feb 11, 2018 via email

joopy commented Feb 12, 2018

joba-1 commented Feb 20, 2018 •

edited

Loading

joopy commented Feb 20, 2018 •

edited

Loading

arendst commented Feb 20, 2018

joopy commented Mar 1, 2018

TSL2561 not working Version 5.11.1 (Sonoff TH16) #1644

TSL2561 not working Version 5.11.1 (Sonoff TH16) #1644

Comments

joopy commented Jan 19, 2018

joopy commented Jan 19, 2018

joopy commented Jan 19, 2018

joba-1 commented Feb 3, 2018 • edited Loading

joba-1 commented Feb 3, 2018

joopy commented Feb 4, 2018

Merdeka commented Feb 4, 2018 • edited Loading

joopy commented Feb 4, 2018

arendst commented Feb 4, 2018 • edited Loading

joba-1 commented Feb 4, 2018 • edited Loading

arendst commented Feb 5, 2018 • edited Loading

joba-1 commented Feb 5, 2018

joba-1 commented Feb 5, 2018

joba-1 commented Feb 5, 2018 • edited Loading

joba-1 commented Feb 5, 2018

joopy commented Feb 6, 2018 • edited Loading

joba-1 commented Feb 6, 2018

joba-1 commented Feb 6, 2018 • edited Loading

joopy commented Feb 6, 2018

joba-1 commented Feb 7, 2018

arendst commented Feb 7, 2018

joba-1 commented Feb 8, 2018

joopy commented Feb 10, 2018

arendst commented Feb 10, 2018

joopy commented Feb 10, 2018

arendst commented Feb 10, 2018

joopy commented Feb 11, 2018

joba-1 commented Feb 11, 2018 via email

joopy commented Feb 12, 2018

joba-1 commented Feb 20, 2018 • edited Loading

joopy commented Feb 20, 2018 • edited Loading

arendst commented Feb 20, 2018

joopy commented Mar 1, 2018

joba-1 commented Feb 3, 2018 •

edited

Loading

Merdeka commented Feb 4, 2018 •

edited

Loading

arendst commented Feb 4, 2018 •

edited

Loading

joba-1 commented Feb 4, 2018 •

edited

Loading

arendst commented Feb 5, 2018 •

edited

Loading

joba-1 commented Feb 5, 2018 •

edited

Loading

joopy commented Feb 6, 2018 •

edited

Loading

joba-1 commented Feb 6, 2018 •

edited

Loading

joba-1 commented Feb 20, 2018 •

edited

Loading

joopy commented Feb 20, 2018 •

edited

Loading