I cannot select a custom sensor setting
I see that in the screen shots on the 1st page of this thread they are defined as "General, Custom Sensor".
In my Domoticz i can select "Dummy (Does nothing, use for virtual switches only)" in settings -> hardware
So i created 3 dummies, but when i try to create a Virtual Sensor i canot find a Custom Sensor.
I did tried some of the given sensors, but they don't look right.

If i create Decibel sensors and if i use those IDX i can see that the correct vallues are passed on to Domoticz by the script.
I only need to find a way to create an custom sensor.

Just wanted to say thanks for this. Had to go from a stable to Beta release to get the custom sensors, but works a treat. Well, I say that, but it initially worked for about a day before the script couldn't retrieve any information about servers from speedtest.net. No obvious reason why, but installing a Python version seems to have gotten round it. Script is running every half hour and I'm wondering if it was getting blocked somewhere.

I think they are both Python scripts, but the one in the repo and the one you install manually uses different url's to fetch the serverlist from. I believe its http://www.blabla and http://c.blabla. The www-one sometimes doesn't return the serverlist. Seen that as well.

Anyway, glad you like it!

I don't know if you noticed or not, but I'm an extremely arrogant man who tends to think all of his plans will work ...

mikeoo wrote:
I know the Rasp have only 100 Mbps connection so that part i understand.
But ping is way different every time.

My Raps and PC are connected to the same switch and same type of network cable.

Any ideas why this is so different.

See here
Essentially, system load of the Pi at the exact time the ping is received / responded to will have dramatic affects on the ping time. The same applies to your NAS. These are not devices with dedicated processors - these are embedded low power devices.

"The Raspberry Pi Model B has a Fast Ethernet port with a nominal transfer rate of 100Mbps, which restricts the throughput to about 10MBps. Because the corresponding chip resides on the USB bus, it shares its throughput with other connected devices, such as USB hard drives. Also, the fairly simple module causes a higher CPU load than its contemporaries on typical desktop boards.”

Just the CPU load increase of running the test will be enough to impact on the test’s results.

Last edited by Marci on Friday 04 November 2016 19:37, edited 2 times in total.

So question on the dummy sensors, I have created a dummer sensor in the hardware but when I go to devices which sensor type do I select? counter? I have tried this and it appears to be kw/h
Would it be text then?

lol well I am idiot I appreciate that. I was thinking "custom" was referring to with in specific sensor.
annnd just found out it won't give me accurate results because I am running on the original rpi which is 10/100 and it doesn't give me correct results
tested the cmd line and it only gives me 50mbs yet I have 200 and on lan with laptop I get full 200.
might have to find a small 10/1000 module somewhere and run it as a external sensor that my existing pi queries

hi to everyone.
i take some test and i don't know why, but in the same time i have 2 different result from the test from pc and from rpi.
rpi give me download 4.84, pc 10.84, while for the upload is the same rpi 0.82, pc 0.87, and the ping is the same 33 ms on rpi and pc.
why the download test is so different ????

guantolento wrote:hi to everyone.
i take some test and i don't know why, but in the same time i have 2 different result from the test from pc and from rpi.
rpi give me download 4.84, pc 10.84, while for the upload is the same rpi 0.82, pc 0.87, and the ping is the same 33 ms on rpi and pc.
why the download test is so different ????

If you had read 8 posts up in this thread, Marci gives a very good explanation and a link why RPI's have shitty results. Cheap and fun, but not built for speed.

Marci wrote:
See http://www.raspberry-pi-geek.com/Archiv ... (offset)/4
Essentially, system load of the Pi at the exact time the ping is received / responded to will have dramatic affects on the ping time. The same applies to your NAS. These are not devices with dedicated processors - these are embedded low power devices.

"The Raspberry Pi Model B has a Fast Ethernet port with a nominal transfer rate of 100Mbps, which restricts the throughput to about 10MBps. Because the corresponding chip resides on the USB bus, it shares its throughput with other connected devices, such as USB hard drives. Also, the fairly simple module causes a higher CPU load than its contemporaries on typical desktop boards.”

Just the CPU load increase of running the test will be enough to impact on the test’s results.

It can probably handle 4.84Mbps throughout the whole system, because it's slow AND has to share resources with other hardware as well.

Therefore, the upload is well within the ~5Mbps it can handle, so it's about the same result (you have 10Mbps down / 1Mbps up?) and the ping is a whole different story alltogether.

I made this to monitor an internet connection, so run it on a machine that can handle at least the bandwidth you want to measure and expect, it's not an RPI benchmarking tool

Good luck!

Last edited by safi78 on Thursday 03 November 2016 19:45, edited 2 times in total.

I don't know if you noticed or not, but I'm an extremely arrogant man who tends to think all of his plans will work ...