I am having a similar issue trying to use the minecraft:redstone_conductivity component in block permutations by a custom state.

I have attached a small addon that demonstrates the issue.

In the picture, the custom block is lit and should also be conducting redstone.

Utility Blocks.mcaddon

I can confirm that custom blocks do not conduct redstone signals and that this is still an issue in Preview 1.21.20.22, and likely in the most recent release as well.

I can confirm. None of the custom blocks can receive or conduct a redstone signal. Use the attached .mcaddon

Steps to reproduce:

1. Load a world in creative with both the RP and BP enabled (use the .mcaddon)
2. Pick one of the custom blocks from the creative menu.
3. Place it down and place a button on it, alongside with redstone surrounding the adjacent blocks. (see the video)
4. Press the button.

Observed results:
The block won't activate the surrounding redstone dust.

Expected results:
The block should be able to receive and conduct a redstone signal.

I'm still not sure what I'm doing when compressing to an add-on file, so I've also included the behaviours and resources separately to import manually if this doesn't work. To clarify, ALL of the blocks are supposed to carry redstone. I've tried multiple solutions, so some of their code may appear different. Minecraft_Party.mcaddon Minecraft Party BP.zip Minecraft Party RP.zip

Thank you for your report!

However, this issue has been temporarily closed as Awaiting Response.

The attached addon appears to be missing dependencies and/or resource packs. Could you please attach them? Also, could you please specify which of the custom blocks are meant to transfer Redstone signal?

This ticket will automatically reopen when you reply.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📓 Project Summary – 📧 Suggestions – 📖 Minecraft Wiki

This is the add-on I've made and am using. I hope it works, but I've never converted to an add-on before

Minecraft_Party.mcaddon

Could you please attach a sample add-on, so that others can reproduce the bug? I had to use the add-on provided in MCPE-168998, which also appeared to describe a similar issue, that has since been fixed. From my tests, custom blocks from the aforementioned add-on do interact and work properly with redstone in 1.20.51 as long as they receive a strong enough signal or direct input from a button (for example).

Since in your case, the custom block won't receive or conduct a redstone signal, I'm under the impression that this could be an error in the code or that the behavior and functionality of the block was configured incorrectly.