mentalinc: Wow that map provides very accurate looking location data!

scottjpalmer: Good to see https://meshmap.net getting more populated.

The relatively new Meshtastic NZ Facebook group is growing fast and getting some interesting posts and discussions.

A domain has been registered https://meshtastic.co.nz I'm sure the owner would be happy to take your suggestions on what you would like to see there. I can pass them on until contact details appear.

I still haven't been able to work out how to configure my Rakwirless kit to update the map, I'm in Titahi Bay.  Any tips on the config?

rp1790:

scottjpalmer: Good to see https://meshmap.net getting more populated.

The relatively new Meshtastic NZ Facebook group is growing fast and getting some interesting posts and discussions.

A domain has been registered https://meshtastic.co.nz I'm sure the owner would be happy to take your suggestions on what you would like to see there. I can pass them on until contact details appear.

I still haven't been able to work out how to configure my Rakwirless kit to update the map, I'm in Titahi Bay.  Any tips on the config?

I should probably look at Geekzone more often.

I have been involved with Meshtastic from a few months after its founding that previous record was mine. I have a fair few nodes and have done some design EDA design work on some custom boards using various microcontrollers.

Hawkes Bay anyone want to link up let me know I have all the hardware and even a few possible repeater locations.

I have mostly messed around with 865mhz stuff but its exactly the same hardware (aside from the antenna) for most of the SX1262 modules and premade dev boards. (we can use 864mhz-868mhz for LoRa here too) 

Worth noting as well we are fortunate here to have very relaxed (in comparison to most other countries) rules around our output power and duty cycle

https://rrf.rsm.govt.nz/ui/licence/radio/view/238648

The amount of hours of passion that has gone into this project by all the community volunteers from around the world is really quite something they are all really great people.

Hey, perhaps a noob question from someone that does not have much experience with radio comms but is a programmer... I know that in order for messages to be sent and received, a packet exchange is necessary between two devices, through one or more nodes. I never used Meshtastic, so maybe some of these answers will be obvious to you, but I was wondering if it would be at all possible to use it to enable HTTP protocol in a specific node to host web pages that other devices could access in some sort of "private internet" or "intranet" if you will. Does anyone know if that would be possible using the current version of the firmware? Does it allocate IPs to each one of the devices connected?

In my opinion, having information hosted through a service like Kiwix to enable access to Wikipedia and other informational resources in an emergency situation would be great value to the network.

znx:

I was wondering if it would be at all possible to use it to enable HTTP protocol in a specific node to host web pages that other devices could access in some sort of "private internet" or "intranet" if you will. Does anyone know if that would be possible using the current version of the firmware?

Does it allocate IPs to each one of the devices connected?

Its far too slow for IP over it. Would be like dialup, but worse because its a party line.

Message packets are fully received by a node before it sends them on. There is not exchanges of them, you either get the packet, and rebroadcast it with the counter decrimented, or you dont get it. IP would be a constant stream of packets and just cause collisions. Not to say that there isn't IP over Lora done by someone, but its a terrible idea unless it was all pre-configured UDP stuff where you were not wasting many timeslots before you even got around to sending your actual message. You would not want to do a mesh with IP over something so collision prone and slow as Lora.

Yeah, it makes sense.

I wonder if any of the folk here more up with the meshtastic play than I can offer some wisdom on the initial setup?

I'm just playing around with some old TTGO Lora V1 boards (I know these are having support phased out) while I wait for some newer V2 boards to arrive. I can get them to talk to each other up here, but to date haven't once seen any messages pop up from other users. I'm up in Hawkes Bay so that could be because there aren't many people within range of me, but i've even tried enabling one of them to talk mqtt and don't see anything in the messages from there either when I was sort of expecting to be so flooded with messages that the thing would crash.

I have basically set almost everything to be the defaults - so i'm wondering if there's some base config needed that isn't detailed in the getting started guides (perhaps because some of the settings are specific to the region?). I've now tried changing the name of the Primary channel from blank to 'LongFast' but still not seeing anything show up though watching the mqtt server with a desktop app (MQTT Explorer) I can see new messages showing up in that topic so would have thought they might show up on one of my devices :)

Anybody got any detailed guide or advice on what I might be missing?

Which region did you set? It should be ANZ (not NZ_865) to ensure you're in the right band. The frequency slot should be 20 (aka 919.875MHz), which will be the default unless you messed with the channel order or renamed LongFast to something else. If you did, then you'll need to manually set the frequency slot back to 20.

Wow, thanks for replying so quickly!

I have set ANZ as the region, but I left everything else as it was on both of the nodes I have - one I access with the built-in web client, the other with the iOS app & bluetooth.

In the LoRa settings it shows Frequency Slot 0, in the web client it has no other comment, but on the iOS client it notes "if set to 0 this value will be calculated automatically based on the primary channel name." Both of them are using the modem preset Long Fast.

As far as the channel goes - on both this came up by default labelled as Primary, but neither of them were named so I set the name "LongFast" on each to see if that would help get messages to arrive.

Anyway, given your note about the frequency slot I guess i'll try setting that to 20 on both and see what happens. Would this impact whether the node sees MQTT delivered messages as well as LoRa ones?