tasmota-display build isn't enabling TM1637 driver without enabling SPI. #11358

ajithvasudevan · 2021-03-16T17:22:47Z

PROBLEM DESCRIPTION

Tasmota's Display build (tasmota-display.bin) is supposed to support TM1637 in release 9.3.1. However, this is not happening if we configure just the TM1637 specific GPIO pins (TM1637 DIO and TM1637 CLK).

After configuring the TM1637 DIO and TM1637 CLK pins, none of the DISPLAY- commands are available, indicating that xdrv_13_display is not executed.

I have traced the issue (in the latest development branch) to the following in xdrv_13_display.ino :

bool Xdrv13(uint8_t function)
{
  bool result = false;

  if ((TasmotaGlobal.i2c_enabled || TasmotaGlobal.spi_enabled || TasmotaGlobal.soft_spi_enabled) && XdspPresent()) {

The above condition is false even if TM1637 pins are configured

This could be because of TasmotaGlobal.soft_spi_enabled not being true from the following code in support_tasmota.ino

    bool valid_cs = (ValidSpiPinUsed(GPIO_SPI_CS) ||
                     ValidSpiPinUsed(GPIO_RC522_CS) ||
                     (ValidSpiPinUsed(GPIO_NRF24_CS) && ValidSpiPinUsed(GPIO_NRF24_DC)) ||
                     ValidSpiPinUsed(GPIO_ILI9341_CS) ||
                     ValidSpiPinUsed(GPIO_ILI9341_DC) || // there are also boards without cs
                     ValidSpiPinUsed(GPIO_EPAPER29_CS) ||
                     ValidSpiPinUsed(GPIO_EPAPER42_CS) ||
                     ValidSpiPinUsed(GPIO_ILI9488_CS) ||
                     ValidSpiPinUsed(GPIO_SSD1351_CS) ||
                     ValidSpiPinUsed(GPIO_RA8876_CS) ||
                     ValidSpiPinUsed(GPIO_ST7789_DC) ||  // ST7789 CS may be omitted so chk DC too
                     ValidSpiPinUsed(GPIO_ST7789_CS) ||
                     (ValidSpiPinUsed(GPIO_SSD1331_CS) && ValidSpiPinUsed(GPIO_SSD1331_DC)) ||
                     ValidSpiPinUsed(GPIO_SDCARD_CS)
                    );
    // If SPI_CS and/or SPI_DC is used they must be valid
    TasmotaGlobal.spi_enabled = (valid_cs) ? SPI_MOSI_MISO : SPI_NONE;

As a fix, one could add (ValidSpiPinUsed(GPIO_TM1637DIO) && ValidSpiPinUsed(GPIO_TM1637CLK)) to valid_cs above, but then this will automatically assign 3 SPI pins to GPIOs unnecessarily. I had pointed out this issue in the TM1638 PR and had provided a fix there.

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

18:11:01.200 MQT: stat/TM1637/RESULT = {"NAME":"Generic","GPIO":[1,1,1,1,1,1,1,1,1,1,1,1,1,1],"FLAG":0,"BASE":18}
18:11:01.427 MQT: stat/TM1637/RESULT = {"Module":{"18":"Generic"}}
18:11:01.683 MQT: stat/TM1637/RESULT = {"GPIO0":{"6624":"TM1637 CLK"},"GPIO1":{"0":"None"},"GPIO2":{"6656":"TM1637 DIO"},"GPIO3":{"0":"None"},"GPIO4":{"0":"None"},"GPIO5":{"0":"None"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO12":{"0":"None"},"GPIO13":{"0":"None"},"GPIO14":{"0":"None"},"GPIO15":{"0":"None"},"GPIO16":{"0":"None"},"GPIO17":{"0":"None"}}

If using rules, provide the output of this command: Backlog Rule1; Rule2; Rule3:
Provide the output of this command: Status 0:

18:12:36.706 MQT: stat/TM1637/STATUS = {"Status":{"Module":18,"DeviceName":"Tasmota","FriendlyName":["TM1637"],"Topic":"TM1637","ButtonTopic":"0","Power":0,"PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0}}
18:12:36.735 MQT: stat/TM1637/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota/release/tasmota.bin.gz","RestartReason":"Software/System restart","Uptime":"0T00:02:33","StartupUTC":"2021-03-16T17:10:03","Sleep":50,"CfgHolder":4617,"BootCount":11,"BCResetTime":"2021-03-16T16:49:04","SaveCount":26,"SaveAddress":"FA000"}}
18:12:36.769 MQT: stat/TM1637/STATUS2 = {"StatusFWR":{"Version":"9.3.1(display)","BuildDateTime":"2021-03-09T16:13:09","Boot":31,"Core":"2_7_4_9","SDK":"2.2.2-dev(38a443e)","CpuFrequency":80,"Hardware":"ESP8266EX","CR":"353/699"}}
18:12:36.789 MQT: stat/TM1637/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["Andromeda",""],"TelePeriod":300,"Resolution":"558180C0","SetOption":["00008009","2805C8000100060000005A00000000000000","00000080","00006000","00000000"]}}
18:12:36.818 MQT: stat/TM1637/STATUS4 = {"StatusMEM":{"ProgramSize":579,"Free":424,"Heap":27,"ProgramFlashSize":4096,"FlashSize":4096,"FlashChipId":"1640EF","FlashFrequency":40,"FlashMode":3,"Features":["00000809","0FAA858E","04049FA1","000000C3","00000000","00004080","00000020","401F8000","00000000"],"Drivers":"1,2,4,5,8,9,10,13,16","Sensors":"1,2,5,6"}}
18:12:36.848 MQT: stat/TM1637/STATUS5 = {"StatusNET":{"Hostname":"TM1637-5904","IPAddress":"172.20.1.13","Gateway":"172.20.1.1","Subnetmask":"255.255.255.0","DNSServer":"172.20.1.1","Mac":"84:F3:EB:25:77:10","Webserver":2,"WifiConfig":4,"WifiPower":17.0}}
18:12:36.869 MQT: stat/TM1637/STATUS6 = {"StatusMQT":{"MqttHost":"172.20.1.127","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_257710","MqttUser":"DVES_USER","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30}}
18:12:36.892 MQT: stat/TM1637/STATUS7 = {"StatusTIM":{"UTC":"2021-03-16T17:12:36","Local":"2021-03-16T18:12:36","StartDST":"2021-03-28T02:00:00","EndDST":"2021-10-31T03:00:00","Timezone":"+01:00","Sunrise":"07:00","Sunset":"18:56"}}
18:12:36.910 MQT: stat/TM1637/STATUS10 = {"StatusSNS":{"Time":"2021-03-16T18:12:36"}}
18:12:36.918 MQT: stat/TM1637/STATUS11 = {"StatusSTS":{"Time":"2021-03-16T18:12:36","Uptime":"0T00:02:33","UptimeSec":153,"Heap":27,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"Andromeda","BSSId":"00:11:32:6C:33:E2","Channel":5,"RSSI":100,"Signal":-34,"LinkCount":1,"Downtime":"0T00:00:03"}}}

Set weblog to 4 and then, when you experience your issue, provide the output of the Console log:

00:00:00.049 CFG: Loaded from flash at F9, Count 27
00:00:00.055 QPC: Count 1
00:00:00.056 CFG: CR 353/699, Busy 0
00:00:00.059 SRC: Restart
00:00:00.060 Project tasmota Tasmota Version 9.3.1(display)-2_7_4_9(2021-03-09T16:13:09)
00:00:00.211 WIF: Checking connection...
00:00:00.212 WIF: Attempting connection...
00:00:00.548 WIF: Connecting to AP1 Andromeda Channel 5 BSSId 00:11:32:6C:33:E2 in mode 11n as TM1637-5904...
00:00:01.752 WIF: Checking connection...
00:00:01.752 WIF: Connected
00:00:02.003 HTP: Web server active on TM1637-5904 with IP address 172.20.1.13
00:00:02.483 RTC: UTC 2021-03-16T17:13:19, DST 2021-03-28T02:00:00, STD 2021-10-31T03:00:00
18:13:19.157 HTP: Console
18:13:20.043 MQT: Attempting connection...
18:13:20.077 MQT: Connected
18:13:20.080 MQT: tele/TM1637/LWT = Online (retained)
18:13:20.082 MQT: cmnd/TM1637/POWER = 
18:13:20.083 MQT: Subscribe to cmnd/TM1637/#
18:13:20.085 MQT: Subscribe to cmnd/tasmotas/#
18:13:20.086 MQT: Subscribe to cmnd/DVES_257710_fb/#
18:13:20.089 MQT: tele/TM1637/INFO1 = {"Module":"Generic","Version":"9.3.1(display)","FallbackTopic":"cmnd/DVES_257710_fb/","GroupTopic":"cmnd/tasmotas/"}
18:13:20.093 MQT: tele/TM1637/INFO2 = {"WebServerMode":"Admin","Hostname":"TM1637-5904","IPAddress":"172.20.1.13"}
18:13:20.103 MQT: tele/TM1637/INFO3 = {"RestartReason":"External System"}
18:13:23.470 QPC: Reset
18:13:24.382 MQT: tele/TM1637/STATE = {"Time":"2021-03-16T18:13:24","Uptime":"0T00:00:09","UptimeSec":9,"Heap":30,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Wifi":{"AP":1,"SSId":"Andromeda","BSSId":"00:11:32:6C:33:E2","Channel":5,"RSSI":100,"Signal":-38,"LinkCount":1,"Downtime":"0T00:00:03"}}
18:13:25.382 APP: Boot Count 12
18:13:25.735 CFG: Saved to flash at F8, Count 28, Bytes 4096

TO REPRODUCE

Download and flash the 9.3.1 tasmota-display.bin build or build and flash the latest development branch code with the tasmota-display env.
Configure two GPIO with TM1637 DIO and TM1637 CLK pins
Issue the command Display or DisplayModel
Output shows stat/TM1637/RESULT = {"Command":"Unknown"}

EXPECTED BEHAVIOUR

After following the steps to reproduce, the output should show the current settings and it should be possible to use the TM1637 Display as it is documented as supported, in the Release notes.

SCREENSHOTS

NA

ADDITIONAL CONTEXT

See discussion in #11031 for additional context

(Please, remember to close the issue when the problem has been addressed)

The text was updated successfully, but these errors were encountered:

arendst · 2021-03-16T17:34:27Z

As this display type doesn't need SPI or I2C it should not bother with these interfaces.

The goal of adding the dedicated GPIOs was (and is) to only allow this display type to work if a user has configured the specific TM1637 GPIO's. The TM1637 driver should only work when these GPIO's are configured without any need for SPI or I2C.

arendst · 2021-03-16T17:37:28Z

Ah I see what you mean.

I will need to rewrite the check for display support WITHOUT either I2c or SPI present.

ajithvasudevan · 2021-03-16T17:43:45Z

Ah I see what you mean.

I will need to rewrite the check for display support WITHOUT either I2c or SPI present.

I had indeed made those changes earlier (as part of TM1638 PR) here: 75699fe

Fix TM1637 driver selection (#11358)

arendst · 2021-03-17T15:26:53Z

Pls try if latest fix solves selecting the TM1637 driver

ajithvasudevan · 2021-03-17T16:01:36Z

Pls try if latest fix solves selecting the TM1637 driver

@arendst
This latest fix does allow TM1637 driver selection in the display build.

However, I see that the xdsp_interface.ino has the following:

#if defined(USE_I2C) || defined(USE_SPI)
#ifdef USE_DISPLAY

Doesn't this mean the TM1637 driver still "depends" on the existence of either I2C or SPI ? It is working in the Display build after the fix because the Display build already has SPI enabled.
It probably means I can't use TM1637 Display if I have something like the following in my user_config_override.h :

#undef USE_I2C
#undef USE_SPI

#define USE_DISPLAY
#define USE_DISPLAY_TM1637

But being able to do this is not critical. It is good to have.

arendst · 2021-03-17T16:08:22Z

Ah forgot to change . Will have a look now.

Fix some display issues (#11358)

arendst · 2021-03-17T16:26:20Z

Fixed again

ajithvasudevan · 2021-03-17T16:41:58Z

Tested the fix.
It works fine with both the Display build as well as the user_config_override.h settings I mentioned above.

I think the TM1638 PR should work now. Will merge the fix there and test.

Hope it is fine that the same TM1637 driver is used for the TM1638 as well.

Also, I've originally planned to use the the same driver for the MAX7912 as well. But now having second thoughts about it. Maybe I should make the MAX7912 a separate driver? Please suggest.

Thank you!

arendst · 2021-03-17T16:46:05Z

Make it seperate first and if in the end there is too much redundancy you can always merge.

ajithvasudevan · 2021-03-17T16:47:44Z

Make it seperate first and if in the end there is too much redundancy you can always merge.

You mean make the MAX driver separate, right? And let TM1638 still be part of TM1637, right?

arendst · 2021-03-17T16:48:36Z

Correct, Right.

ajithvasudevan · 2021-03-17T17:02:25Z

I have merged this fix with the TM1638 PR and it works fine without any further changes to the PR code.

Would you please accept the PR after review?

sugus6 · 2021-03-18T20:22:55Z

I tried a 6-Digit TM1637 display today.
Program Version 9.3.1.2(display), Build Date & Time 2021-03-18T16:46:09.
The command DisplayType or DisplayType 1 doesn’t work for me.
21:18:13.686 CMD: DisplayType 1 21:18:13.692 RSL: stat/tasmota_7BE2B9/RESULT = {"Command":"Unknown"}

The following commands works: Display, DisplayText 1234, DisplayClock, ....
21:18:34.554 CMD: display 21:18:34.559 RSL: stat/tasmota_7BE2B9/RESULT = {"Display":{"Model":15,"Width":0,"Height":0,"Mode":1,"Dimmer":1,"Size":4,"Font":1,"Rotate":0,"Refresh":2,"Cols":[16,8],"Rows":2}}

What am I doing wrong?

ajithvasudevan · 2021-03-19T02:25:54Z

I tried a 6-Digit TM1637 display today.
. . .
. . .
What am I doing wrong?

If you built the code from the latest arendst/Tasmota development branch, then please use DisplaySize instead. See the documentation in the driver code here: https://github.com/arendst/Tasmota/blob/development/tasmota/xdsp_15_tm1637.ino

DisplayType was introduced in a subsequent PR, but it has been decided to discontinue it (see discussion in said PR). Instead, the command would be DisplayCols to change the number of digits in the future.

ajithvasudevan · 2021-03-19T09:01:26Z

@sugus6,

The future (that I mentioned above) has arrived sooner than expected :) Please ignore the above if you are taking the latest code from arendst/Tasmota development branch.
You should now use DisplayCols to set the number of digits. In your case, Backlog DisplayCols 6 ; Restart 1 should do it.

For now, the documentation is here: https://github.com/arendst/Tasmota/blob/development/tasmota/xdsp_15_tm1637.ino

sugus6 · 2021-03-19T19:03:43Z

Thank you for your quick feedback.
I tried the latest de development build from http://ota.tasmota.com/tasmota/tasmota-display.bin.gz
Tasmota Version 9.3.1.2(display)-2_7_4_9(2021-03-19T14:44:17)

When I execute this command displaycols I get…
19:41:44.189 RSL: stat/tasmota_7BE2B9/RESULT = {"DisplayCols1":4}

I change to 6-digit DisplayCols 6
19:47:10.286 CMD: DisplayCols 6
19:47:10.293 RSL: stat/tasmota_7BE2B9/RESULT = {"DisplayCols1":6}

My Wemos D1 mini reboot automaticaly but is still a 4 digits display!

00:00:00.049 CFG: Loaded from flash at F8, Count 28
00:00:00.054 QPC: Count 1
00:00:00.062 DSP: TM1637 with 4 digits
00:00:00.065 Project tasmota Tasmota Version 9.3.1.2(display)-2_7_4_9(2021-03-19T14:44:17)

19:48:05.516 CMD: displaycols
19:48:05.521 RSL: stat/tasmota_7BE2B9/RESULT = {"DisplayCols1":4}
Displaycols is not saved!

My display lights up at value higer then DisplayDimmer 13
19:34:57.407 CMD: displaydimmer 13
19:34:57.413 RSL: stat/tasmota_7BE2B9/RESULT = {"DisplayDimmer":14}
The FW default value for displaydimmer is 7. Can this value be adjustet to 20 as default value?

ajithvasudevan · 2021-03-20T02:58:36Z

@sugus6 ,

The code is in a bit of flux :)
Can you please try DisplayWidth 6 ?

I will update the default DisplayDimmer value to something higher in the forthcoming PR update to the same driver.

Presently, DisplayMode is supported with values 0,1,2, and 3.

All the 7-segment specific Display- commands work only under DisplayMode 0

Also, Power control is implemented. Power 1 to turn on the display.

sugus6 · 2021-03-21T19:57:13Z

Hi ajithvasudevan

I did tests with the latest build: 9.3.1.2(display)-2_7_4_9(2021-03-21T16:59:32)
I was able to set with command DisplayWidth 6 the correct display size.
Also the Dimmer default value is set to a higher value. Thank you so match for you effort.

When I execute DisplayText 123456 I get a wrong output on my display: 321654.
I’ts look that the two blocks of 3digit are swapped!
I have testet my two 6-digit displays 0.36/0,56 inch, and I get with both the same misrepresentation.
I did a test with the ESPEasy firmware and there is the order of the digts correct.
Can you have a look at this issue?

These are my displays:

TM1637 6-digit displays 0.36/0,56 inch:
https://de.aliexpress.com/item/1005001928450315.html?spm=a2g0s.9042311.0.0.430b4c4dCoFbG8

TM1637 4-digit displays 0.36:
https://de.aliexpress.com/item/1005001993464723.html?spm=a2g0s.9042311.0.0.27424c4dvpel2p
Command DisplayText 1234 works as expected

MAX7219 8-digit displays:
https://de.aliexpress.com/item/1005001432551106.html?spm=a2g0o.productlist.0.0.50fa20bdIalrS0
Command DisplayText 12345678 works as expected

ajithvasudevan · 2021-03-22T04:39:48Z

@sugus6 ,

I did tests with the latest build: 9.3.1.2(display)-2_7_4_9(2021-03-21T16:59:32)

Thanks for testing this driver thoroughly!

When I execute DisplayText 123456 I get a wrong output on my display: 321654.
I’ts look that the two blocks of 3digit are swapped!

It looks like there are different variants of the 6-digit TM1637 modules, with the digits differently wired.
I'm working on support for this additional variant of the TM1637 6-digit module.

ajithvasudevan · 2021-03-22T12:00:21Z

@sugus6 ,
You can now use the command DisplayType 1 to switch to the type of 6-digit TM1637 display you have.
Please test with the latest dev build.

sugus6 · 2021-03-22T17:33:24Z

@ajithvasudevan

Thank you for the quick fix.
With the latest version 9.3.1.2(display)-2_7_4_9(2021-03-22T15:35:22 and command DisplayType 1
my display show now 123456 for DisplayText 123456.

Well done.

lalo-uy · 2021-06-05T15:29:20Z

Is there any chance to have more than one TM1637? May be sharing the DIO pin or on 2 separated ones.

ajithvasudevan · 2021-06-05T16:40:50Z

I am not entirely sure but I think the TM1637 hardware has a limitation on sharing the DIO pin, as the protocol isn't exactly SPI or I2C. What you want should be possible with two separate sets of pins, though it will need some major changes to the TM1637 Tasmota driver and not to mention changes elsewhere, like adding more assignable GPIO Pins, etc., What exactly is your requirement? Is it to just have two sets of 4-digit displays independently controllable by Tasmota? If this is the case, you can get the same effect by simply using a single 8-digit MAX 7219 seven segment display module, separating one set of 4 digits from the module by lengthening its terminals, if needed. You can then concatenate the two 4-digit texts and send it to the MAX in one go. See attachment, for an example of what I mean. Ajith

…

On Sat, 5 Jun 2021, 20:59 Eduardo Spremolla, ***@***.***> wrote: Is there any chance to have more than one TM1637? May be sharing the DIO pin or on 2 separated ones. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#11358 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACBUVQIO27DOXIW36TVKCY3TRI7FZANCNFSM4ZI7LVAA> .

ajithvasudevan · 2021-06-05T16:54:42Z

lalo-uy · 2021-06-05T18:07:53Z

Yes, I need to show 2 temps. Weird no one build the max module as 2 x 4 digit lines. I also have a bounch of TM1637 modules arround. Now I use some rules to alternate 2 values in the same display ever 5 sec. Thanks anyway. El El sáb, 5 de jun. de 2021 a la(s) 13:54, Ajith ***@***.***> escribió:

…

[image: image] <https://user-images.githubusercontent.com/8604353/120899185-0a722900-c64c-11eb-9036-dac15a9d874d.png> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#11358 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACXBW4JKTYQCM2ZOPIWKTALTRJJF3ANCNFSM4ZI7LVAA> .

ajithvasudevan · 2021-06-06T02:38:32Z

... Weird no one build the max module as 2 x 4 digit lines ...

It does exist.
https://robu.in/product/max7219-digital-tube-display-module-control-module/
https://www.aliexpress.com/item/1005001777188350.html

This is the one I used to implement a requirement similar to yours (shown in the image in my previous post)

lalo-uy · 2021-06-06T12:13:34Z

I want it in 2 lines, like this one https://images.app.goo.gl/hcbXGceF4QfBPmug7 But with Max chip. The picture is with 74hc595. El El sáb, 5 de jun. de 2021 a la(s) 23:38, Ajith ***@***.***> escribió:

…

... Weird no one build the max module as 2 x 4 digit lines ... It does exist. https://robu.in/product/max7219-digital-tube-display-module-control-module/ This is the one I used to implement a similar requirement as yours (shown in the image in my previous post) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#11358 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACXBW4PYH73HUKYC76F27JTTRLNTJANCNFSM4ZI7LVAA> .

ajithvasudevan · 2021-06-08T10:09:45Z

I want it in 2 lines...

That was the point of the example picture I attached previously.
In the example above, I have separated the two 4-digit displays on a single MAX module by de-soldering one of the 4-digit seven-segments from the board and re-connecting it by soldering short lengths of wire between each of the de-soldered display terminals and the board. Now the 4-digit display at the end of flexible wires can be re-oriented and mounted any which way you want, including one below the other, in 2 lines.
Of course this solution requires a bit of soldering skill. You can probably take help from someone who has those skills, if you are not upto it.

ajithvasudevan mentioned this issue Mar 16, 2021

Added support for TM1638 Seven-Segment Display #11031

Merged

6 tasks

arendst added a commit that referenced this issue Mar 17, 2021

Fix TM1637 driver selection

b427267

Fix TM1637 driver selection (#11358)

arendst added bug Type - Confirmated Bug fixed Result - The work on the issue has ended labels Mar 17, 2021

arendst added a commit that referenced this issue Mar 17, 2021

Fix some display issues

2f7eefa

Fix some display issues (#11358)

ascillato2 closed this as completed Mar 18, 2021

ajithvasudevan mentioned this issue Mar 22, 2021

Added support for another variant of the 6-digit TM1637 display module #11422

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

tasmota-display build isn't enabling TM1637 driver without enabling SPI. #11358

tasmota-display build isn't enabling TM1637 driver without enabling SPI. #11358

ajithvasudevan commented Mar 16, 2021 •

edited

Loading

arendst commented Mar 16, 2021

arendst commented Mar 16, 2021

ajithvasudevan commented Mar 16, 2021

arendst commented Mar 17, 2021

ajithvasudevan commented Mar 17, 2021 •

edited

Loading

arendst commented Mar 17, 2021

arendst commented Mar 17, 2021

ajithvasudevan commented Mar 17, 2021 •

edited

Loading

arendst commented Mar 17, 2021

ajithvasudevan commented Mar 17, 2021 •

edited

Loading

arendst commented Mar 17, 2021

ajithvasudevan commented Mar 17, 2021

sugus6 commented Mar 18, 2021

ajithvasudevan commented Mar 19, 2021 •

edited

Loading

ajithvasudevan commented Mar 19, 2021 •

edited

Loading

sugus6 commented Mar 19, 2021

ajithvasudevan commented Mar 20, 2021

sugus6 commented Mar 21, 2021

ajithvasudevan commented Mar 22, 2021

ajithvasudevan commented Mar 22, 2021

sugus6 commented Mar 22, 2021

lalo-uy commented Jun 5, 2021

ajithvasudevan commented Jun 5, 2021 via email •

edited

Loading

ajithvasudevan commented Jun 5, 2021

lalo-uy commented Jun 5, 2021 via email

ajithvasudevan commented Jun 6, 2021 •

edited

Loading

lalo-uy commented Jun 6, 2021 via email

ajithvasudevan commented Jun 8, 2021

tasmota-display build isn't enabling TM1637 driver without enabling SPI. #11358

tasmota-display build isn't enabling TM1637 driver without enabling SPI. #11358

Comments

ajithvasudevan commented Mar 16, 2021 • edited Loading

PROBLEM DESCRIPTION

REQUESTED INFORMATION

TO REPRODUCE

EXPECTED BEHAVIOUR

SCREENSHOTS

ADDITIONAL CONTEXT

arendst commented Mar 16, 2021

arendst commented Mar 16, 2021

ajithvasudevan commented Mar 16, 2021

arendst commented Mar 17, 2021

ajithvasudevan commented Mar 17, 2021 • edited Loading

arendst commented Mar 17, 2021

arendst commented Mar 17, 2021

ajithvasudevan commented Mar 17, 2021 • edited Loading

arendst commented Mar 17, 2021

ajithvasudevan commented Mar 17, 2021 • edited Loading

arendst commented Mar 17, 2021

ajithvasudevan commented Mar 17, 2021

sugus6 commented Mar 18, 2021

ajithvasudevan commented Mar 19, 2021 • edited Loading

ajithvasudevan commented Mar 19, 2021 • edited Loading

sugus6 commented Mar 19, 2021

ajithvasudevan commented Mar 20, 2021

sugus6 commented Mar 21, 2021

ajithvasudevan commented Mar 22, 2021

ajithvasudevan commented Mar 22, 2021

sugus6 commented Mar 22, 2021

lalo-uy commented Jun 5, 2021

ajithvasudevan commented Jun 5, 2021 via email • edited Loading

ajithvasudevan commented Jun 5, 2021

lalo-uy commented Jun 5, 2021 via email

ajithvasudevan commented Jun 6, 2021 • edited Loading

lalo-uy commented Jun 6, 2021 via email

ajithvasudevan commented Jun 8, 2021

ajithvasudevan commented Mar 16, 2021 •

edited

Loading

ajithvasudevan commented Mar 17, 2021 •

edited

Loading

ajithvasudevan commented Mar 17, 2021 •

edited

Loading

ajithvasudevan commented Mar 17, 2021 •

edited

Loading

ajithvasudevan commented Mar 19, 2021 •

edited

Loading

ajithvasudevan commented Mar 19, 2021 •

edited

Loading

ajithvasudevan commented Jun 5, 2021 via email •

edited

Loading

ajithvasudevan commented Jun 6, 2021 •

edited

Loading