@sundberg84 - thanks, I know but this one keeps popping up and seems to hang the domoticz installation. Now running a 'fresh' domoticz installation to get to the root cause..

Sounds like I'm the only one testing the S_WIND device... another hick-up that confuses me and my Domoticz installation. It consistently hangs domoticz when the wind sensor reports itself. Two wind devices are created and 'something' goes wrong in the process. When I remove the devices which does ...

Thanks for the clarification. So for Domoticz we need to send wind_direction /16 ? I would suggest to use the 360 scale.

A full fledge wind sensor with values (V_WIND, V_DIRECTION, V_TEMP) sends all the values to Domoticz. The values are combined in a 'combined' wind device which shows all the values. Weather.JPG All values are shown but the value for direction makes no sense. The value is sent in Degrees (0..359) and ...

I built a similar device which shows up in Domoticz. Difference is that I also send V_DIRECTION from the same node. Domoticz is very creative in combining sensors (speed, direction & temp). I could well be that if there is no V_DIRECTION update the device is not shown/created. You could try to send ...

Even better (in MySensors) is to report the battery level through a S_MULTIMETER type with V_VOLTAGE. This way it will show up like

A lot has been written on the MySensors forum on this subject. It boils down to a very stable power supply for the radio. What works in most cases is a capacitor direcly on the radio of > 4.7uF, I use 47uF for a normal (non amplified) nRF24l01+. The radio is very sensitive to any disturbance in the ...

Hendrik wrote:anyone who have a working sketch, please post it here

What kind of sketch are you looking for?

I guess you can use the 5 custom variables to store/read custom things ? Like your last counter values? Like in the original 'EnergyMeterPulseSensor.ino' sketch ? As I said: would be possible to use the custom variables like the example sketch is doing. But why construct a workaround when a ...

No thats not possible, please use the VAR types (you have 5 of them, should be enough !?) Why would you want something like V_TEMP? Main reason is to allow for the reading of all sensor values from the controller for usage and display in other sensors (as in the MySensors API) and getting the ...

No thats not possible, please use the VAR types (you have 5 of them, should be enough !?) Why would you want something like V_TEMP? Main reason is to allow for the reading of all sensor values from the controller for usage and display in other sensors (as in the MySensors API) and getting the ...

extract from "MySensorsBase.cpp"... is it possible to extend this list with the other "V_" types to be read? V_WATT, V_KWH, V_TEMP, V_HUM, etc. Like with the V_VARx types, this would almost complete the implementation. else if (message_type == MT_Req) { //Request a variable std::string tmpstr ...

and the sketch underneath it (LightLuxSensor Example) uses the actual value so whats the standard ? At the moment i have implemented it as percentage, if you convert your value in the range of 0-100% then it should work. Standard should be to report in Lux. The only % value is V_DIMMER. I have ...

How to start fresh?? Erase the EEPROM? /* * * This sketch clears user EEPROM (MySensors) * load and run for > 20 secs * */ #include <MySensor.h> #include <SPI.h> void setup() { for (int i=0;i<256;i++) { gw.saveState(i, 0xff); } } void loop() { // Nothing to do here... }

I have been playing around with the frontpage. Love the simplicity and usefullness. Just for your attention: http://www.domoticz.com/forum/viewtopic.php?f=6&t=5113 and in the "last version" (22-jan) I downloaded there are a lot of missing "</div>'s" messing the whole thing up...(mainly on "page 2 ...

Just another use of Floorplan. All S0 meters are read by Domoticz (with correction via a LUA script) and with current usage displayed on the "Floorplan"