Switch Brazil from AU915 to AU915_SB1
Switch New Zealnd from AS923_1 to AS923_1C
Configure Iraq to EU868
Configure Sierra Leone to EU868

When complete update lorawan-h3
helium/lorawan-h3#36

https://en.wikipedia.org/wiki/Ilemi_Triangle ought to be EU868 as its now South Sudan and the adjacent bit next to Kokuro
Claimed as https://en.wikipedia.org/wiki/Eastern_Equatoria and Kenya dont seem to claim it on their maps
https://en.wikipedia.org/wiki/Geography_of_Kenya

https://en.wikipedia.org/wiki/Isla_Su%C3%A1rez

from jay on discord:

following up on madninja's comment: both AU915-SB1.res7.h3idz and AS923-1.res7.h3idz contain 878b52da0ffffff.

878b52da0ffffff:
https://explorer.helium.com/iot/hex/878b52da0ffffff

AU915-SB1:
https://github.com/dewi-alliance/hplans/blob/4530fb8d7c8bab71b1d61efcd5ec31ff99577485/AU915-SB1.geojson

AS923-1:
https://github.com/dewi-alliance/hplans/blob/4530fb8d7c8bab71b1d61efcd5ec31ff99577485/AS923-1.geojson

Hello
I would like to mention that in switzerland the allowed dbm / mW-EIRP is not the same than in EU, we have more than in the EU. Its not fair to reduce even more the power of the Miner. I ask to be country, by country independent. thanks.

Hotspot b58 Addresses

11abfZZjk2VVrxA8tDUxh74ceG8F9h5G8A9WsFhUZkVpJmYqs85
112GnH9eGgCs45Z4o7ZwhR7ergcfLdoAutP7pgtFiFR7XGaD3Zrp
11XrkH21tERwFS2QmvjEq5P1agH7e73o73kmgs9DGdWLegxFnVR
11Ja3Vcssmgv3yXkacKLS55gTaN8v3bCbcLaFJ1odeHbRJEJEJD
11eGoXySt8ayDXUe8HwAawqwRzfWpppLB1daoXGaPQiRjB9y5v1
1127nwpLmiPwVjAmqEox2uHaqbEP56zHQzHoiwaUPy2PgDFBjYLk
118KYT5xvX7YVbpTtFonpziVr2iRzGnJqLMzJR34CA6ZTmE3PYk
112uB1ztBqEWNcSBsJDMMg26eNKrgUghhffzVrpr91cioMsicTP9

Discord Handle

tastaturT#1253

What regional channel plan do you expect your hotspot to be using?

EU868

Details

Hello, All hotspots located in Morocco do not send or receive beacons. Also, according to Helium, Morocco is an EU433 frequency region, although the government keeps the EU868 frequency open and allowed

To whom it may concern,
I have had correspondence with LoRa Alliance regarding the frequency use for Trinidad and Tobago. They advised the following 👍

"A foot note was lost during the editorial process of 1.0.3 which is used to indicate that US902-928 is indeed a valid channel plan for Trinidad and Tobago. The Regional Parameters workgroup continues to recommend AU915 for harmony with the other countries in the Caribbean and Central and South America, many of which do not support the 902-915 portion of the US band. "

As such, please revise the recognised Frequency to US915 for Trinidad and Tobago, as its recognized as AU915 ONLY

Hi Team,

Pakistan Telecommunication Authority has recently announced LPWAN frequency bands for Pakistan, which are 433.05 - 434.79 MHz and 920 - 925 MHz. So the LoRaWAN frequency plans can be EU433 or AS923. Details of the regulatory framework official copy can be found at following link:

https://www.pta.gov.pk/assets/media/iot_srd_regulatory_framework_01-06-2022.pdf

Can we please update the information according above changes.

Appreciate your support.

Regards,

Azam
iot_srd_regulatory_framework_01-06-2022.pdf

Aruba shows up as EU868 in the polygons even though it should be 'unknown' according to the csv. This is happening because Aruba is part of the Netherlands from the openmaps dataset.

Aruba and Curacoa are the only two cases where this happens that i know of. They are a different channel region from their region as downloaded from openmaps.

Hans island has US915 and EU868 regions assigned.

https://www.businessinsider.com/canada-and-denmark-whiskey-war-over-hans-island-2016-1

Prior to changing the whole region to AS923_1 there were quite a number of external territories and countries that implement Australian standards on AU915.

The rollback seems to have considered only Australian mainland.

The prior list

Australia                     AU915
NewZealand                    AU915
Tokelau                       AU915
PapuaNewGuinea                AU915
NorfolkIsland                 AU915
Niue                          AU915
HeardIslandandMcDonaldIslands AU915
CookIslands                   AU915
ChristmasIsland               AU915
CocosIslands                  AU915
TimorLeste                    AU915
Tonga                         AU915

Generally these are considered with AU regulations:

• ChristmasIsland
• NorfolkIsland
• TimorLeste
• CocosIslands
• HeardIslandandMcDonaldIslands
• PapuaNewGuinea

Whereas these with NZ regulations:

• Tonga
• Tokelau
• Niue
• CookIslands

Can this please be fixed as part of the rollback.

LoRaWAN® Regional Parameters RP002-1.0.4 was published Sep 2022
Update Helium's Regions to conform to RP002-1.0.4
https://resources.lora-alliance.org/technical-specifications/rp002-1-0-4-regional-parameters

Changes identified
Mauritius - EU433 -> EU868
Guyana - US915 -> Unknown
Bonaire, Sint Eustatius and Saba (BQ) - EU868 -> Prohibited
Algeria AS923-3 -> EU868

Crimean peninsula has both RU864 and EU868 channel plans currently.

The latest version of lorawan regional parameters - 1.0.4 has Kazakhstan as IN865

There are polygon rf regions within other regions

Netherlands uses EU868 but Curaçao is AS923-1 in the semtech regional parameters

I've created this repo based on these geojson files: https://github.com/helium/lorawan-h3

We're still not 100% sure how we'll ship the serialized regions, but I added a self-contained binary for testing lookup speed on various systems. Worst case scenario on Raspberry Pi 4 is about 10 ms to check a location's LoRaWAN region.

After the POCv11, hotspots in the Philippines (AS923-3) suddenly got ALL invalid beacons and witnesses. There was no change in the frequency when the upgrade to POCv11 happened. It was still the the same AS923-3 uplink frequencies but those are now incorrect_frequency. Did we missed something in the config file or something related to that?

https://explorer.helium.com/txns/HnsJUI1mtfFbs-A-wAAIxPoWK6slCuybLhXOUmuz93A

Here's the screenshot of the frequency and the invalid witnessing caused by incorrect_frequency.

I hope the helium team can have a look and make the fix soon.

Vatican is in list twice.

Under (H) Holy See as EU868
Under (V) Vatican as Unknown

As the Vatican is only 1km wide and in the middle of the EU868 Italy region I would think EU868 Is correct.

We can either switch Brazil to the AU915_SB2 region. In other words just copy AU915_SB1 to AU915_SB2
Or we can add Brazil back into the AU915 region.

Afterwards the plan is to run a "vote" with Brazil for the change sponsored by BrDot.

Antarctica is under (A) with unknown Region yet is also at end of list as

Chilean Antarctic AU915
Australian Antarctic AU915
British Antarctic EU868
Argentine Antarctic AU915

In the list twice

Under (B) British Virgin Islands as Unknown
Under (V) Virgin Islands UK as AU915

AU915 assumed correct but not sure of best naming convention https://en.wikipedia.org/wiki/British_Virgin_Islands

Hi gradoj,

Miners were working until poc v11 second day, the first day it still was EU868 the second day it was a update or something it changed all to Region Undefined !! ALL miners not working In Kosovo , i got litterly over 40 miners with region undefined , this issue been like this for a couple of days , talked with javier from bobcat suport team he asked me to contact the helium team !!

Kosovo is surrounded by Serbia,Maqedonia, Albania and Montenegro, all around my country are working fine just not kosovo !!

I hope this get resolved as soon as possible !!

government page:

http://www.arkep-rks.org/?cid=2,236
The list of radio equipment without restrictions
The list of radio equipment which can be placed on the market and be put into service without restrictions based on article 30 of Regulation No.31, could be downloaded here.
http://ec.europa.eu/docsroom/documents/26843
All frequency laws and frequency is same from european commission , here is a link direct from european commission to download:
https://ec.europa.eu/docsroom/documents/26843
some you see kosovo use same link and docs from there site.
EU 868

So :

Kosovo indeeds follows CEPT/ERC/REC 70-03 in its frequency table at 868 MHz (source: http://www.arkep-rks.org/?cid=2,51,193)

I also talked with @hashc0de in discord he was gonna take a look what is happening !!

Here is one of my wallet : https://explorer.helium.com/accounts/1379kCowr6zna446KMgykLVdQBrrJDbxmWNUni75jJYvy9sfyWu/hotspots

You can see it worked before perfectly and just stopped all my miners , got over 40 miners with region undefined

Got alot of screenshots how it was befor with eu868 my miners then after when it changed if needed !!!

Hotspot b58 Addresses

NA

Discord Handle

NA

What regional channel plan do you expect your hotspot to be using?

No response

Details

Malaysia is to be changed to a new region called AS923-1B.

Eswantini is in list twice, under their current name and old name

Under (E) Eswatini as Unknown
Under (S) Swaziland as Unknown

Only one line required?

Brazil will use AU915_SB1
Australia will use AS923_1C
New Zealand will use AS923_1C

See PR for futher details - helium/sx1302_hal#36

csv has Armenia as EU868 and geojson appears to be present but no lorawan-h3 hexes

We do not currently support EU433 hardware

1. This hardware requires a different antennae compared to 800 Mhz and 900 Mhz hardware
2. 433 Mhz SRD regulations limit 433 to very, very low power limits thus making EU433 not useful for Helium.

Remove any and all references to EU433 in hplans, such as Gambia. It is OK to include EU433 in the "Region2" category.

DualPlan is a feature which enables a Helium Gateway to concurrently support both AS923_1 and AU915 devices on a single set of 8 channels. For AU915's DualPlan we've switched from SB2 to SB6.

After the successful conclusion of a Beta test, the Helium Foundation has announced:

DualPlan will be deployed to the following ANZ countries:
AU, CX, CC, CK, HM, PG, NU, NZ, NF and TK

Update Australia to the AU915 SB2 region.

Rollback is due to Australia's Vote:
https://heliumvote.com/13F5AWLhxwTjhDMnZ6ww4oJWgRkBoW9ji4JnDzwQXjsQhiT2kcX

Discord Discussion on Vote:
https://discord.com/channels/404106811252408320/778989538755346442/1094035893003751474

British Virgin Islands & Virgin Islands UK are two separate entries for the same place
they should be on as one entry for AU915 region.

Suggested placement is moving them and U.S. Virgin Islands to be as in LoRa Alliance RP1.0.4 doc both under V
Virgin Islands, UK (VG)
Virgin Islands, US (VI)

Hotspot b58 Addresses

119QLi6AZuhizziKGG4WEECmXyCYHjwsaRnT2Z1zxvws3RoJF87
11syAuBuxhu2UBe4SiwgUm2amv3fCk48y1P8oZpK1RptbMaeRWc
1124qLC1hrC47yU2RFqTT4NHHYCEaEJujkeN3hH3RTaj7K23fGJx

Discord Handle

el69#6601

What regional channel plan do you expect your hotspot to be using?

AS923-4

Details

Hotpots in Israel in the West Bank have a major issue where their country returns null from the Helium API:
https://api.helium.io/v1/hotspots/1124qLC1hrC47yU2RFqTT4NHHYCEaEJujkeN3hH3RTaj7K23fGJx

The value is null because the West Bank area is not recognized to be in Israel.
Because country is null, hotspots cannot assign frequency and can't participate in Proof of Coverage at all.

Potential reason
Since this is the West Bank maybe some political reasons are in play and the location is not identified as Israel, but for all things matter at this point this is part of Israel and should be recognize so for any miner to be able to work there.

Hotspots example
Note that there is no country:

Example hotspot with country (not in the West Bank):

Problematic area
As described all of the hotspots in the west bank are not being allocated to Israel as they supposed to.
Higher view, in red - Israel border line, In blue - the area which Helium not recognize to be in Israel:

Any hotspot inside the blue line are not allocated to Israel, even though this is the center of Israel.

Impact
Helium is growing rapidly in the last couple months in Israel and there are many cities in the west bank (no matter the ethnic relation) that will not be able to participate as any hotspot won't have any country allocation.

Testing
I placed 3 hotspots in this area and asserted the location - none of them could identify the region or participating in PoCs for 2 weeks.
After 2 weeks of no activity I took 2 of the hotspots and asserted them to a new location very close (but this time not on the west bank area), without changing any actual configuration or setup, and right after 1 hour the region appeared as Israel and they started to witness beacons and being challenged.

Some more examples
https://explorer.helium.com/hotspots/hex/882db07329fffff
https://explorer.helium.com/hotspots/hex/882db0701bfffff
https://explorer.helium.com/hotspots/hex/882db00837fffff
Curved Ebony Cobra Sensecap dashboard:

How can we solve this problem for the benefits of everyone?

Thanks,
Elad.

I recommend that the community provisionally sets the currently unspecified countries in Africa to the EU868 frequency plan to match with what we understand from local authorities and deployers. The LoRa Alliance doesn't currently specify regional parameters for these countries so this would be an addition that we are proposing for Helium-network specific devices.

Most relevant here is Liberia who the Foundation is working with on the ground through the OPEN team to establish local LoRaWAN connectivity.

This frequency selection here would be subject to future government or regulatory updates, or an update from the LoRa Alliance. Since this a local initiative, it's assumed that Hotspot owners are going to deploy Hotspots on their own behalf and not on behalf of the Foundation so this guidance is based on our understanding of the local rules through conversations with the community. Ultimately, Hotspot owners are the ones who are assuming the risk of deployment, assertion, and ongoing operation. If a Hotspot owner has specific questions or concerns, they should seek local regulatory or legal advice.

Currently the island is configured for eu868 but is unknown in version 4 of the regional parameters

Helium had Cayman Islands as US915 in the original countries.csv so revert back to US915 from Unknown.

Hotspot b58 Addresses

112fadfeetw433tgfgr45yrgbrg

Discord Handle

handle

What regional channel plan do you expect your hotspot to be using?

EU433

Details

i am right on the border of...

There is overlapping regions and r7 may not be high enough resolution.

The 2 letter code for Sahrawi Arab Democratic Republic is EH from investigation

https://laendercode.net/en/country/eh

For some reason since the 14th of December, all hotspots in Malta (EU) have simply stopped sending out beacons and witnessing eachother.

Chilean, British and Argentine territories overlap.

Are we now referencing 1-0-4 for the regional parameters mentioned in the readme.md?
https://resources.lora-alliance.org/technical-specifications/rp002-1-0-4-regional-parameters

Move Pakistan from IN865 to AS923-1

This border in Serbia might have some gaps even though both sides of the border are EU868. The polygons could be merged before to help with some of these issues where the regions are the same.

While the RP2-1.0.3 LoRaWAN® Regional Parameters are currently silent on Guyana, the National Frequency Allocation table permits amateur use on 902-928 MHz. Update Guyana frequency from unknown to US915.

https://telecoms.gov.gy/resources/National%20Frequency%20Allocation%20Table%20for%20Guyana.pdf

As part of Spain it should be EU868 but has EU433 overlapping.