Topics created by Strixx

Well. It was the radio that caused this false triggers. The final placement of the node must be in a radio shaddow. I really "funny" thing is that I solved this problem by changing the radio. I had a NRF24L01+PA+LNA for better range. This was for future project (node in my greenhouse) which would need this node as a repeater for shore. But by replacing the radio to a "normal" NRF24L01+ made the problem go away. I did not change the location!

@pjr I am still a noob when it comes to C. And I have not had the time to examine the Domoticz source code. But at first glance those lines seems as V_PERCENTAGE, V_SCENE_OFF, V_STOP and V_RGBW that updates the last seen on heartbeat. I have had my node running now for 2 days just checking this heartbeat. And I can for shore sasy that is only working for the door sensor. Which presents it self as S_DOOR and sends V_TRIPPED messages. It is not working for the motion sensor presenting it self as S_MOTION and also sends V_TRIPPED messages. And one more really strange thing is that it is only working on the door sensor when the door is open. Not closed!

@Flyer Sorry, but I can't remember if I had any more problems after I manually fixed the database. And just a couple months after I had this problem I switched to Home Assistant instead.

@strixx make sure you flash the correct bootloader for the crystal frequency of your pro mini (3.3V 8Mhz vs 5V 16MHz) and select the correct pro mini target in the Arduino IDE. Any errors will cause baudrate deviation in the serial bootloader communication, causing sync errors.

@strixx you are welcome. The simple flag is designed to be as simple as can be. So it enables everything. On development it is slightly refactor ed, so it is possible to use simple signing, simple encryption or simple "both" (which if I recall is named SIMPLE_SECURITY_PASSWD or similar.

@strixx yes

Ok. So my strange error was due to connecting GND to the wrong PIN. I was connecting GND next to VCC on the side of the Pro Mini. Accordning to pics on the MySensors homepage and to the marking of my Arduino that pin is GND. But when connecting the FTDI with jumper cables I notice that PIN was marked with CTS. So instead I connected GND to the pin one step out. This PIN is also marked GND on my Arduino, and on the FTDI. But marked BLK on the pictures on MySensors home page. So it seems that both these pins are GND on my board, because everything else was working fine except the reference for analogue pins. So topic solved. Thanks for all input. And specally @gohan that made me use the jumper cables and therfore found the error.

It for shore is. And what is even more strange is that adding a new manually assigned IP now is working. Can't explain it. The router is a Asus RT-AC66U.

@dbemowsk Thank you! This is what I was looking for. Especially the code in your thread.

@strixx BEFORE YOU USE analogRead() You need to be aware that the MySensors core Ver 2.2 has code to support sensors reporting the chip VCC voltage. As I recall, this code is enabled by default and all readings of the analog port will return 65,535, -1 or hex FFFF, depending on the type of variable you read the value into regardless of what voltage is applied to the analog pin. MySensors has changed the 8266 configuration to read the chip VCC and ignore the analog input and I gather the MySensors coders decided to return 65,535 as an indicator. You will need to do a search for "ESP analog read" or similar, to find the correct syntax of the special command to change the 8266 mode to re-enable reading of the analog input pin. Note: this analog mode command must be placed at the top of your script before any other functions. DIFFERENT NodeMCU BOARDS Please be aware the analog pin 'hardware' varies with different NodeMCU devices and you need to understand how the MySensors restricts how you can use this pin. First, I have encountered three different 'NodeMcu Ver 1' boards. Traditionally the analog pin expects a range 0V to 1V max. Some docs state going over 1V can destroy the pin, others state it can tolerate 0V to 3.3V but the anagloRead() for voltages of 0V to 1V are as expected, but 1V to 3.3v returns the same value. On the earlier boards I received, the analog pin of the PCB was wired direct to the 8266 chip (in the metal can) and not connected to anything else. About a year ago, the boards I received had additional circuitry to protect the analog pin from excess voltage. More recently I have received a batch of 20 boards which returned values lower than expected? Suspecting a board problem, I traced the circuit and confirmed there is a voltage divider which scales an input of 0V to 3.3V to become 0V to 1V at the actual 8266 chip. I.e. these boards requiire a 0V to 3.3V input on the analog pin. If you code reads values about one third of what you expeted, you may have a 0V to 3.3V board. VALUES NOT CONSISTENT As a final tip, I have noticed that no two NodeMCU's return the same value from the analog port. I.e. five 'identical' boards from the same batch will return slightly different values, unlike the Arduino devices, which I find all return accurate readings. My assumption is, this is due to the 8266 using a different analog to digital conversion method, and the errors are 'possibly' due to some capacitive effect. The differences or minimal, can can be confusing and may need special attention if you are checking for a 'specific' value. Hint: always code analogRead comparisons to look for different 'ranges' of values, rather than "if analogRead(A0) == 350", because the value you get today could be different tomorrow or next week. This is good practice because the value read will vary slightly as your project's supply voltage changes due to changes in load (e.g. several LEDs turned on vs off), or even if your battery or even mains voltage is unstable. Hope this saves someone banging their head against a brick wall for hours like I did. Paul