Code Garage to the rescue.

[hlehoux]

Thank you @CodeGarage , you really thrive !

As for the suggestions, i would say most important point would be to look at the project code base.
I guess the development branch has quiet evolved since the 2.3.2 release.

Next would be to sort the features and decide a roadmap for mysensors because the project can live only if it evolves

Long live MySensors!

[TheoL]

@hlehoux As I understand the limitation of the packet size is by the NRF radio. Maybe stop supporting NRF, so that we can get a bit bigger packet size. That would help my current project where I'm using MySensors as a transport layer. I know that is easier with wifi. But I want to use mysensors.

Never mind: If I hexify everything, I can squeeze in all I need so far.

[fsgraz]

@TheoL I wish nRF will be supported for longer time. Maybe just be free to specify the payload lenght instead ?

But I am with you on wishing for MySensors protocol over wifi with extendable lenght.

[OldSurferDude]

@fsgraz As an alternative to MySensors using the nRF24 radio, look at the work that tmrh20 has done. I have used this code and found it works well enough. It's lower level than MySensors. I haven't tried to connect it to Home Assistant, but I think a determined person could make this happen.

I would say it doesn't have the support that MySensors ha,s being only one person, but there isn't much support here anymore. :(

[hlehoux]

Well, i've swiched all my sensors from nRF24 to RFM69 for longer range

[OldSurferDude]

@CodeGarage I am getting the message that www.mysensors.org is not responding (13h22 PDT 8 Aug 25) Is MySensors officially dead?

[tekka]

@OldSurferDude The website should be back again.

[fsgraz]

it is up and running

[Honk]

there is a problem with openhardware.io
The cert seems to be outdated. Is someone here who can do something about it? If not does anybody know who to ask?

[mfalkvidd]

Thanks for reporting @Honk

@hek has fixed the cert issue now