I get this message (**S&F - Not available on this channel. ) back from my T-beam supreme when I set it to perform Store and Forward and send it the direct message SF from another node. As far as I can tell the settings I am using are the same as others people’s who report, using a normal T-beam (not the Supreme), that Store and Forward works. Is there something I am missing?
Update: moving to firmwear 2.4 rather than 2.5 solved this problem.
You can’t use store and forward on the default key.
Thanks. Can you please exaplain what the “default key” is. All I changed to make the error go away was was the firmwear and then it worked. I am not aware of using a “default key”.
In Munich we are using a channel with a certain name
say
Channelforchatting
and it has a PSK we shared and all know,
which results in S&F working fine for everyone who knows the name of the channel and the entry for the PSK box (Android)
Is the PSK the “key” and if so, what is the default so I can say if we are using the default or not. Is the ‘default key’ the PSK entry as in Longfast ?
In which case I am surprised because in 2.4… it works fine according to our tests.
Thanks.
Yes, it’s the key used by default on LongFast and the restriction was only added recently.
Aha. You mean in 2.4 one can use the default PSK but in 2.5 not?
In principle, yes. However, it’s highly recommended to not use it on the public channel to avoid spamming it with potentially a lot of packets.
But the name of the channel is special
Channelforchatting
and the PSK is perhaps “default”
but it is still a private channel not the public channel
because one needs to know the channel name, which not everyone does.
There is no public channel being used… though perhaps your comment implies that use of the “default” PSK means that the S&F node DOES repeat / forward messages to the public Longfast channel though this should not happen. On Reddit people are reporting their surprise that S&F forwards messages that were destined for public Longfast to Longfast: when the docs say this is not possible.
It should work if your channel name is not derived from the modem preset (e.g. LongFast).
However, if you also have the public channel (LongFast), it might be it’s requesting it on LongFast and that is no longer permitted.
On Reddit people are reporting their surprise that S&F forwards messages that were destined for public Longfast to Longfast: when the docs say this is not possible.
I don’t understand what you wrote here. The docs say it’s not allowed to request history from the S&F server via the public channel anymore (since 2.4.x).
The requesting node requests it via a direct message only. But the S&F re-sends / forwards messages, so that they appear in the the requesting node’s messages, that are messages not only to the secondary channel Channelforchatting but also Longfast (the default public channel)
I thought that this was not allowed / possible.
Not sure if they really mean the public channel (LongFast with AQ== PSK) with “channel 0”, it might be he has a different primary channel.
But, as per the docs, the request cannot be on the public channel, but yeah, it would still return packets from the public channel if you requested it via another channel.
