Topics created by fleinze

I guess the atmega328pb needs a board designed for it, though, if you are to get the benefits of the atmega328pb? If it's just behaving as a regular atmega328p, I'm not sure there's any point to it. https://exploreembedded.com/wiki/Tit,_a_supercharged_Arduino_Pro_Mini_with_Atmega328pb

@fleinze interesting experience. Thanks for sharing.

Non-invasive current measurement with HMC5883L is as good as mosquito killing by the hammer - can be done but an overkill! Non-invasive current measurements are greatly done with wire clamp/loops. HMC5883L is highly sensitive and low noise digital compass. It can be used in drones, smartphones, VR sets - any applications that needs to know change of physical object orientation in 3D space. We use it for vehicle detection sensor. Did a benchmark on RMS on temperature stability with half a dozen of other sensors, ST, NXP, Bosch. HMC is the best!

Well actually i didn't. Thanks a lot!

Yes. There also exist a function for it in development branch in the MyHwxxx implementations. But it does not seem to be available for use so I am guessing it is a feature in developing stages. I think the SenseBender sketch also makes use of it since the SenseBender is a hw that can capitalize on such a feature. I also have it in my sketch for my MySensorsNode board but I have not published a finished sketch. But on the openhardware.io entry for it, there is a codebender sketch that can be examined (very much work in progress).

I built something similar here, but it just displays its 'own' values rather than getting them from Domoticz with V_TEXT.

I got hit by this as well. They're fakes: http://www.lungstruck.com/electronics/counterfeit-ds18b20-temp-sensors/ Mine are exactly as described in the linked article.

Me neither. I care about security, not obscurity. I see no reason to encrypt a '1' or a '0' and digital streams like audio and video is not supported anyway. But exchange of constant (but random) data is already used and supported since signing is based on nonce exchange. But I believe IV:s "evolve" with the messages encrypted which implies the messages need to be exchanged trustworthy and sender and receiver need to be om sync. But I know to little about that to be sure. In any case, I welcome any development that adds to security, and will happily review such code, but I don't have the bandwidth nor motivation to "drive" the development of encryption in the core library as I don't feel it adds enough value to be worth the effort.

It was merged a long time ago in the development branch. Add #define MY_RF24_CHANNEL 76 in sketch

Hello fleinze, What about this project? Your sensors still working? I'm trying to build the same but I have some problem to change the efuse value: "I changed the efuse value to 0x07 (BOD off)" I' dont know how to edit the boards.txt file and how to install it in the arduino pro mini. Could you explain the procedure step by step or link me a good complete tutorial ? Thank you very much

Hi @sbackaer ! The version 1.5 does not have the gateway class. I currently work with the development branch and I didn't use the 1.5 for quite some time; but I think it is enough to remove the mygateway.h include replace the mygateway contructor with a mysensor constructor replace gw.processRadioMessage with gw.process() Take a look at the serial gateway example.