@electros I just realised that the flickering means that the module tries to switch to the sender but the mplayer process runs into an error.
Does it work if you run the command directly in the shell?

@electros
Sorry for that.
I will check it tomorrow. It is curious because I did not change anything in the backend.

Found a hack:
You can create an own m3u file which contains this url “http://stream.laut.fm/magicfm”. This one is working fine with mplayer

                                       {
						title: "Test",
						url: "/home/pi/test.m3u",
					}

I tried this link on the command line:
mplayer -cache 256 -playlist http://www.surfmusik.de/m3u/magicfm,14949.m3u

Mplayer complains that the station is to slow. It doesn’t even start playing in my case.
It looks like mplayer has some known problems with aac.

But you are right. If i use xmms2 it works.
The problem is, that xmms2 uses a totally different interface.

But also some good news. I released a new version 0.0.2 which adds two volume buttons.

@electros I will check if I can include two control buttons to increase/decrease the volume by sending notifications to MMM-Volume.

Description:

This is a simple module which uses external scripts as data source to display the temperature and humidity of different sensors.
As i use an HTU21 sensor a script to read the values is included already. There scripts to read data of DHT11, DHT22, BME280, DS18B20 included as of version 0.0.2.

Download:

MMM-Temperature
[card:Tom-Hirschberger/MMM-Temperature]

---

Version 0.0.10

• added a wrapper script to call the Python scripts within a virtual environment
• updated the instructions and default values to use the new wrapper script

Version 0.0.9

• added support for SHTC3 sensors

Version 0.0.8

• use spawnSync instead of execSync to call the scripts now. execSync caused “Error: write EFAULT” exceptions so this change was necessary

Version 0.0.7

• The values send via notification now can be parsed if they are in JSON version 5 format, too

Version 0.0.6

• the bme280 scripts now supports setting the I2C address via command line

Version 0.0.5

• additional values like wind speed, uv and rain can be displayed now
  

• modified some of the examples to get a more reliable wifi connection on the esp32 boards and added a new example
  

Version 0.0.4

This new version 0.0.4 provides the following features:

• the values of sensors no can be updated in a single notification which has an json structure as payload. if the keys “temperature_c”, “temperature_f” or “humidity” are present the values get updated. if either “temperature_c” or “temperature_f” is missing but the other one is present the missing value is calculated automatically.

Version 0.0.3

This new version 0.0.3 provides the following features:

• it is now possible to specify a useValueCnt for each sensor. If the sensor provides data less periodically than the updateInterval (i.e. because the sensor sends the data via MQTT less frequently) the data can be used multiple intervals before it gets invalidated and “na” will be displayed.
• added an example of howto provide data of an DHT11 (or DHT21, DHT22) sensor connected to an ESP8266 board which uses MQTT and deep sleep.
• added an example of howto provide data of an DHT11 (or DHT21, DHT22) sensor connected to an ESP8266 board which uses plain tcp

Version 0.0.2

This new version provides the following improvements:

• The values of sensors now can be updated via notification now.
• It is possible to hide the temperature and humidity section for either all sensors or specific ones.
• There are now scripts included to read values of DHT11, DHT22, BME280, HTU21 or DS18B20 connected to the Raspberry Pi.
• There are different examples of howto read values of sensors connected to micro controllers via plain TCP or MQTT (with help of the MMM-MQTTbridge module).
• As every wrapper now gets specific css classes assign you can customize the colors more easy

Version 0.0.1

The initial release provides the following features

• read temperature of sensors by calling scripts with arguments
• multiple sensors with different data scripts can be added
• sensors can be displayed with or without name
• an example script to read the data of an HTU21 sensor attached to the I2C bus of the raspberry is included and will be used as default data source
• an example of how to connect an HTU21 sensor to an ESP32 micro controller with build-in wifi is included also

Screenshots

Hi,

i wrote an complete example recently and added it to my module:
HC-SR501 PIR Example

I translated it to german language as well: HC-SR501 PIR Beispiel

Hi,

normally mplayer is very fast. Can you try to reduce the caching with the “mplayerCache” option either for one station or globally for all. The default value is 512 and may be a little high.

There already exists an module to control the volume MMM-Volume which i use in my setup.

Sorry if it look liked i am taking the things personal that wasn’t my goal.
I want my modules to work and not to cause problems…

Could it be that you run two Browser (maybe build in and a second head) because the notifications get fired twice?

Edit: The delay seems to work. Because there are 20 seconds between the first time the gpio fires and the second time.

Maybe the problem is not the GPIO. Did you find same useful information in the log. Is the GPIO module fireing that often?

If an delay is configured in the GPIO module any events within this time range will be ignored. It is a simple mechanism and does not depend on the sensor. I use it with three PIRs in my setup without any problems.

Edit: There should be some entry like “MMM-GPIO-Notifications: : Skipped notifcation…” in the log if the delay works and the sensor fires