[Bug]: Compatibility broken between OG (Mesh Chat v1.02) & (Mesh Chat v2.9) Lu #11
Comments
|
Hey there @mathisono! Thanks for the bug report. I am just getting back from traveling across the US with the RV to final locate it in its new home. So it may take a couple days to really dig into this. I can assure you that the method in which the message database is transferred between nodes is identical and fully interoperable between the 1.x and the 2.x code bases. The first thought that I have on the problem you are seeing is that the time between the two instances running MeshChat is wildly different. I would have to look at the code to verify the exact time difference that is acceptable, but I think it is on the order of 30 days. In other words the time on the two nodes is greater than 30 days apart. This was written in by MeshChat's original author and I don't yet have an explanation as to why it is about 30 days. I would refer you to the original issue that was created where this was discussed quite a bit, but it looks like @aanon4 has turned off issues on the old repository and that entire history and discussion is now lost. When you have a moment can you determine what the time is set to on Also, I suspect that |
|
The cloud node kj6dzb-cloudhub1 is a hap light, and WEG is a RPi.
Time look fine on my nodes status page, Wed Nov 1 2023 23:32:11.
Im missing the time discrepancy.
If we figure this out, at a minimum, It would help me to gain some insight,
for an updated wiki.
A little off this topic, but I would like to verify, and write setup
instructions to add additional storage for mesh chat on hAP light/ hAP ac2
/hAP ac2 light/ RPi systems. It was done before the lua code was written.
Proper instruction for the rpi setup is needed. Nothing official. Wiki so
a user adding storage to an existing system gets it right on first setup.
Minor changes may be needed the temp directory and fs permission for rpi
os.
Safe travels
73 mathison
…On Wed, Nov 1, 2023, 7:00 PM Gerard Hickey ***@***.***> wrote:
Hey there @mathisono <https://github.com/mathisono>! Thanks for the bug
report. I am just getting back from traveling across the US with the RV to
final locate it in its new home. So it may take a couple days to really dig
into this.
I can assure you that the method in which the message database is
transferred between nodes is identical and fully interoperable between the
1.x and the 2.x code bases.
The first thought that I have on the problem you are seeing is that the
time between the two instances running MeshChat is *wildly* different. I
would have to look at the code to verify the exact time difference that is
acceptable, but I think it is on the order of 30 days. In other words the
time on the two nodes is greater than 30 days apart. This was written in by
MeshChat's original author and I don't yet have an explanation as to why it
is about 30 days.
I would refer you to the original issue that was created where this was
discussed quite a bit, but it looks like @aanon4
<https://github.com/aanon4> has turned off issues on the old repository
and that entire history and discussion is now lost.
When you have a moment can you determine what the time is set to on
kj6weg-rpi and kj6dzb-cloudhub1?
Also, I suspect that kj6dzb-cloudhub1 is a Linux box/VM running v2.9 of
MeshChat (at least that is what it looks like from the images). Is that box
configured to point to and actual AREDN node that also has the
meshchat-api installed?
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEW6LEPEBSEK5DYDMX6GETYCL5CFAVCNFSM6AAAAAA62DXNS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBZHE2DCNZQHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Any help is always welcome. I believe that @csadams also had some thoughts/desire on developing documentation. You might want to reach out to him and sync up a bit. I would really like to see the documentation in the repo and maybe published with GitHub Pages? Definitely feel free to create a feature request for collecting information and working on documenting external storage. |
|
l did write up instructions for installing MeshChat on a Raspberry Pi, including the fact that you have to install the old version (v1.02) on the Pi, and the new version (currently v2.9) API package on the connected node. It's currently this Doc: https://docs.google.com/document/d/1VEi6Moj8f4eBRtRizGgVMKeNO_EUr-Fdw2wJyFaq130/ |
|
Here's an example of MeshChat v1.02 running on a Linux laptop (with v2.9 API on the hAPac3), vs MeshChat v2.8 running on a hAP. The messages synchronize, but the channels don't seem to: |
|
@patruchon I believe that this is a known problem. I would have to go look at the code to be 100% certain, but the Since this is not exactly the same sync problem that started this issue, I would suggest creating a new bug report so that the problem can be tracked and discussed further without confusing this issue. |
|
Please check issue #15 for a possible behavior that I reported in that issue. |
|
Glad to know every one is finding the new rep!!! Hope all the bug reporting, it can produces a new release, across all the deployment platforms. I will check on how USB storage adoption might fit into a later RC. Im looking to prolong the meshnodes flash memory, with a usable amount of data storage. |
Contact Details
mathisono@gmail.com
Version
v2.9
System Type
AREDN node
What happened?
Compatibility broken between OG (Mesh Chat v1.02) for RPi & (Mesh Chat v2.9) Lua.
(Mesh Chat v2.9) Lua loaded on a Mesh node fails to display messages. Based on the attached photo (Mesh Chat v1.02) for RPi, dose receive the message. (Mesh Chat v2.9) Lua, fails to acknowledge.
Will not add Existing channel. on first message on a new node. Other meshchat nodes do recognize the message Channel.
Originating Meshchat web ui.
What browsers are you seeing the problem on?
No response
The text was updated successfully, but these errors were encountered: