@fly74 This plugin seems like something you might like 😉
Are you in, and available, for testing? I can provide a build (ESP32 based, as it's not included in ESP8266 builds by default) if needed. You'll need at least 1 HT16K33 14 segment (or 7 segment) display.

@fly74 This plugin seems like something you might like 😉 Are you in, and available, for testing? I can provide a build (ESP32 based, as it's not included in ESP8266 builds by default) if needed. You'll need at least 1 HT16K33 14 segment (or 7 segment) display.

@tonhuisman sounds good but the only 7segs I actually use are these:

I think that doesn't help.

Well, it's something new to investigate, might you need an excuse to do some lab-experiments 🤣
These 14-segment displays are quite fun, and text is somewhat better to comprehend than the limited/specially crafted fonts available in P073.

I'll try to get some.

Hi @tonhuisman mine are just arrived, which build should I use for a first test?

And what is the wiring here is one more?

@fly74 I started a test build here: https://github.com/letscontrolit/ESPEasy/actions/runs/27418494513

And what is the wiring here are one more?

The VCC is what powers the chip and the display, and Vi2c is the power that the I2C pull-up resistors are connected to. So you can use 3.3V I2C pins, and power the display from a 5V source. That's how I'm using it and it works great, as you don't need a level converter 😃
When connecting multiple displays on the same bus (with incrementing I2C addresses) you can leave the Vi2c of some display boards disconnected, as having too many 10k resistors in parallel results in a rather low value for the I2C pull-up.

@fly74 I started a test build here: https://github.com/letscontrolit/ESPEasy/actions/runs/27418494513

@TD-er

With Display B build looks really cool

I2c addresses are changed with shortcut different of the 3 solder points?

I2c addresses are changed with shortcut different of the 3 solder points?

Yes, binary counting, A0, A1 and A2, so 8 possible options.
The plugin expects displays placed from left to right to have incrementing addresses, so you can combine up to 8 x 4 digits or 8 x 8 digits. No combination of different module sizes supported though, way to complex to configure.

I2c addresses are changed with shortcut different of the 3 solder points?

Yes, binary counting, A0, A1 and A2, so 8 possible options. The plugin expects displays placed from left to right to have incrementing addresses, so you can combine up to 8 x 4 digits or 8 x 8 digits. No combination of different module sizes supported though, way to complex to configure.

But I need 2x4 digit as 2 separate line, is this possible?

<4><4> = 1st line
<4><4> = 2st line

But I need 2x4 digit as 2 separate line, is this possible?

Use 2 tasks, and change the starting address of the second task to the address of that module 🤷‍♂️
Or if you can't find your soldering iron (or are lazy 😛), configure a second I2C bus, and connect the second module to that bus 🤣

second I2C bus

but I need the 4x4 digit :) = 4 addresses

just make the addresses sequential on the same I2C bus, configure the first 2 modules (0x70 and 0x71) in the first task with I2C address 0x70, and the 3rd and 4th module (0x72 and 0x73) in the second task by selecting address 0x72 as the I2C address. Set both tasks to have 2 displays.

And to make the A0/A1/A2 addressing of the modules explicit:
0x70 = all open
0x71 = A0 closed
0x72 = A1 closed
0x73 = A0, A1 closed
0x74 = A2 closed
0x75 = A0, A2 closed
0x76 = A1, A2 closed
0x77 = A0, A1, A2 closed

just make the addresses sequential on the same I2C bus, configure the first 2 modules (0x70 and 0x71) in the first task with I2C address 0x70, and the 3rd and 4th module (0x72 and 0x73) in the second task by selecting address 0x72 as the I2C address. Set both tasks to have 2 displays.

Understood.

Since when we have 2 i2c busses ?

Since when we have 2 i2c busses ?

Hmm, about 18 months ago?

Since when we have 2 i2c busses ?

Hmm, about 18 months ago?

Oh didn't recognized it.

Oh didn't recognized it.

We should do our marketing and promotion better... 😁

Oh didn't recognized it.

We should do our marketing and promotion better... 😁

🤣

So I play a little around. In which builds is the plugin included?

Collection (not IR), Display, MAX, ESP32 only (and Custom builds, of course)

@tonhuisman 2 things, scrolling is not working and can we have a slashed zero?

Scrolling needs the content to be longer than the display can hold (hmm, I could add a setting for that 🤔).
The slashed zero is feasible, have to think about making that optional too, as it may not be appreciated by all users.

I set a long text in rule with this option

but no scrolling

ESP_Easy_mega_20260612_display_B_ESP32_4M316k

The slashed zero is feasible, have to think about making that optional too, as it may not be appreciated by all users.

What! no respect for traditions....
A 0 should have a slash through it. :)

ESP_Easy_mega_20260612_display_B_ESP32_4M316k

Here's a build that includes the option to enable scrolling, even when the content isn't longer than the display allows:
ESP_Easy_mega_20260613_display_B_ESP32_4M316k.zip

Not unimportant additional remark: Scrolling is only supported for content that is put on the display using 7dtext or 7dbin commands, not for 7dn, 7dt, 7ddt, 7dst or 7dsd...

Sorry @tonhuisman you get me wrong. I don't really need an option for scrolling smaller text as display width. What I've tried to say was that the option "Scroll text > display width" don't work. The slashed zero works great!

I have a 4 digit display configured and the rule command 7dtext,"AAAA-BBBB" is not scrolling.

That seems the problem:

and the rule is setting the text every second, so it is not reaching a scrolling?

The default setting starts scrolling after 1 second (10x0.1), but it's restarted when new content is set using 7dtext or 7dbin command. Setting the content every second will definitely interfere with that. You might want to lower that frequency, or increase the scroll frequency (f.i. lower the speed to 1 so it can do at least 9 steps)

To be able to exclude any content that measures less in width that the display width, I've added this scroll always option, as that seems like a good idea useful feature to me.

but it's restarted when new content is set using 7dtext or 7dbin command.

@tonhuisman but can we stop restarting when the new content is the same as set before?

can we stop restarting when the new content is the same as set before?

Hmm, wouldn't have thought that would be needed, but I'll see what I can do about that

So nobody have to care if the scroll interval is longer than the content setting.

This build shouldn't restart scrolling when the content is the same as the previous:
ESP_Easy_mega_20260613_display_B_ESP32_4M316k-a.zip

(Appended -a to the .zip file name so your browser will download the new file. The .bin files have the same name though.)

No. Don't work. Setup is:

Task with:

Rule:

On System#Boot do
     LoopTimerSetAndRun,1,1   
endon

On Rules#Timer=1 Do
   7dtext,"AAAA-BBBB-"
Endon

ESP_Easy_mega_20260613_display_B_ESP32_4M316k-b.zip

This should fix it, and nice advantage, now also works for the 7dbin command 😃

Perfect. Now I have to test my 2 line setup with 2x4 digit each line.

But scrolling ist not an endless loop. The scrolling starts again when the display is running empty.

"AAAA-BBBB-____" and then again, not "AAAA-BBBB-AAAA-"

Easy to wire.