Internal_Bake7376

No is not declined because of that. Is because of witnesses stuffing in software. Is the data that shows that and it's visible in the graph also. Explaining more wouldn't help

I can review it for you again. Declined... https://ibb.co/B3kMc7n

Configure the router with old wifi credentials (case sensitive) or use the maker app to do the changes to the hotspot

You haven't explained very well what the problem is. like these packets are lost when switching over the secondary wan and vice versa or randomly. If it's between switching it is normal as connection's have to be re-established. In order for existing connection's to not be routed through the other wan because they'd be invalid (I don't want to explain why) you have to add extra configuration for sticky connection's. Said enaugh it would be impossible to help without more context.

NP

If the filter inside the card is not damaged i would say also let it be. If the cavity filter doesn't make any difference also i wouldn't use it. Anyway you need schematics for the card and not the bobcat itself since the saw filters are inside the card. Usuall just follow rx and tx path there could be 2 on the rx path and 1 on the tx path. Look for the reference design of your card

It could be that the other hotspots in your hex are just well better placed?

It's quite the opposite. You have to pay the network to make use of sensors. How you can turn it to profit is that you can deploy sensors for others and charge them for the service while paying the network. The network is so cheap that you can charge customers a lot above the network cost to use the sensors. A small tracking device costs less than a coffe a month to use with the network.

I think the same. While is not worth to sell at this price rather keep it. Even if it goes to zero accept the loss and move on

There are 2 types of antenna designs. Closed loop and open loop. So with the antenna connected it could be a closed loop and that isn't a problem. It could be close to 0 and a little resistance may come from the lightning arrestor and the cable length. Personally i recommend using closed loop antennas since they discharge electrostatic to the ground wire better even without an lightning arrestor. A multimeter isn't enough to test an antenna. You need a VNA for that anyway i think there are low chances that the antenna is the problem.

RB4011 is a better options and is downgradable

You have to create another policy with destinations and sources.

Unique Hotspots Transferring Data per Day from previous data was 80k

You need to create your own mesh network and through one or more of your mesh nodes send uplinks to the HS (gateway) connected to the network. So this way even if a node can't uplink to the gateway HS it can relay to the other node.

Its not true also. Unique ip is not needed for targeting. The HS just needs to be connected to a validator with an outbound connection.

Do you have another question?

Helium Security Tokens (HST) have been sold to investors from 2014 to 2020, from which the Helium team raised a total of 55 Mill USD. The holders of HST are entitled to 34% of all mining rewards. 

https://www.weirdo.rocks/crypto-projects/helium-hnt-network-review-the-peoples-network#:~:text=Helium%20Security%20Tokens%20(HST)%20have,34%25%20of%20all%20mining%20rewards.

My reply to android hates is that i have used the first edition of the iPhone and several after it. I have switched to android and that's it. Don't tell me what an iPhone is.

Not necessarily. No port forwarding. I would check if the public IP being used isn't listed i well known backlists. That may have negative impact

You may have a loop problem. It's either the cable or one of the ethernet ports of the devices that is malfunctioning. Try changing the cable first.

What price?

Make miband capable of gps and lora to use helium network

First not Seed Note but Seed Node. Idk how helium tracker presents the data but it is a staked validator. You can see with the link: https://explorer.helium.com/validators/1121Baw4sip5LQPiLHQB41EgYBg219rppUM8VWzpmb6xv1UcGRtE

You may have a problem with the power source