Open christoph-morrison opened 3 years ago
See also the missing FVERSION
(and other) internal.
It is not intended that the same sensor is displayed in several devices. The slave sensors are not displayed in the master device. This follows the principle that a source generates only one event in the FHEM. If more than one device is needed, this can be derived with readingsProxy.
Now there are two possibilities.
I would prefer the second option.
I didn't know about that principle and there is at least one module that does not follow this principle (HMCCU). I would expect the module to behave in such a way that I can define any devices that can combine any selection of sensors of a master device and can also multiply sensors if I as a user wish so.
A workaround for using LuftdatenInfo with local sensors alltogether is using JSONMOD, e.g. for a SDS011_P1
value the following JsonPath expression will receive the dust sensor PM10 value:
$.sensordatavalues.[?(@.value_type == 'SDS011_P1')].value
A slave device gets no data, even it's a copy from another slave device and the master is getting data.
Master:
Slave (with data):
Slave (no data):
defmod
ing the slave without data didn't help, also didn`t renaming it.