Internet Monitor

[ronny3050]

@pjkoeleman remove all margins from the custom.css (or remove just the top and adjust the right as needed).

[pjkoeleman]

@ronny3050 said in Internet Monitor:

remove all margins from the custom.css

I have been testing for some time and found a solution !
My custom.css looks like this now

.wifi-symbol-1 [foo], .wifi-symbol-1, .wifi-symbol-2 [foo], .wifi-symbol-2, .wifi-symbol-3 [foo], .wifi-symbol-3, .wifi-symbol-4 [foo], .wifi-symbol-4 {
position: relative;
float: right;
margin-top: -30px; 
margin-right: -20px;
}

The result on the screen looks like this

Now it looks like this I took out the header of Internet-monitor, now it belongs to the header with my status. Didn’t now negative numbers in margins were also possible till I tested it.

[ronny3050]

@pjkoeleman That’s correct since you float it to right, but then half of the symbol will be out of bounds on the right, so you can indeed use negative margin-right. :)

[pjkoeleman]

@ronny3050 Never to old to learn.

[mg_switch]

Thanks for the great module. I can see that it will be a fine product once I have one little issue sorted.

The verbose display shows that the speed test is always referencing one specific server in China (not in my home country) and as such the meter readings are showing at 1/10th of what a manual speed test shows (using ookla to a local server in another browser).

Is there any way to specify the server in use or at least limit the servers to a local list or “geofence”?

[bhepler]

According to the documentation, it pulls down a list of servers and their associated ping times. The default is to pick the server with the smallest ping. This is quite curious.

It does look like you can pass in a serverID and have it use that server. You can get the ID of a specific server here. I think with a little editing of the node_helper.js file, you can pass in an object that specifies a particular server.

For bonus points, make the server ID and/or server URL a parameter that you can specify in the config.js entry for the module. Test it and then submit a pull request to the module developer.

Huh. I just tried this and it’s picking servers in Norway, which is very much not nearby.

ETA: Looking at it, it doesn’t seem to be terribly hard. The Start() function sends the socket notification that gets it all going, passing in the config argument. The only option passed in is maxTime. If you can figure out the format that speedtest wants, you could pretty easily pass in whatever you wanted to extract from the config object (payload in the node_helper.js).

I may play with this later myself, just to learn some things.

[bhepler]

Well. That was frustrating. I’ll spare you the details, but I modified the module and submitted a PR. Hopefully @ronny3050 will fix my amateurish code and accept it.

Anyhow, if you want to try it before then, you can clone from my fork of ronny3050’s module. Remember to run npm install.

[nickthebeer]

Hi, only just discovered this module and it seems like a great idea however I cannot get the wifi symbol to appear.

Here’s my config for the module:

module: “internet-monitor”,
position: “bottom_center”,
header: “Internet Monitor”,
config: {
type: " ",
maxTime: “20000”,
updateInterval: “0”,
verbose: “false”,
displayStrength: “true”,
displaySpeed: “false”,
strengthIconSize: “80”,
maxGaugeScale: “100”,
wifiSymbol: {
size: “50”,
fullColor: “3afc25”,
almostColour: “#ffff0c”,
halfColor: “#ff8c00”,
noneColor: “#ff1111”
},
}
}

Am I being thick and have missed something?

Additionally is the wifi symbol a measure of internet speed on the pi or wifi strength to my AP?

[bhepler]

@nickthebeer - The WiFi symbol is actually a ping test to the testing server. Ping times > 150ms are marked as no signal, ping < 70ms is full strength.

Looking at the speedtest documentation, the API returns a “list of closest servers” after testing. Who knows how long that takes, especially if you’re using the original code without my updates. The node_helper.js then pulls the closest server and does a ping test.

I think this is just going to be a patience thing. Watch the console log for the line: ping. That’s the notification from the node_helper.js that the ping is complete. If the Wifi symbol doesn’t appear after that, come back and we’ll look at it.

[mg_switch]

@bhepler Confirming…100% working as suggested. I have included the local speedtest server to the config (serverID), the verbose now displays this server…and the speed gauges show the expected speeds, DLs and ULs. Nice work.