Development

i had my answer on ahtxx issue Hi, ...figured out that the _address is messed up (i guess by mysensors). It is impossible, because _address is private variable. The private data members cannot be accessed from outside the class (mysensors can not see it). Сan you try my original library but with class initialization line AHTxx aht10(0x38, AHT1x_SENSOR); //sensor address, sensor type

@gulshan212 how can i do this by using mysensors library coz i need also to save battery power.

I would recommend to switch to a nrf24l01 or rfm69/95, where you will have bidirectional communication and you can use the mysensors framework

Wow - given the age of the most recent messages on here, I wondered if I would get a response. Many thanks for responding so quickly and my problem is resolved. [ Note I now also have PlatformIO installed and that compiled the sketch at the first attempt. I can't work out which version of the board it is using, as it uses different naming conventions, but I think it is the most recent. ]

@electrik upload_port does not specify the target. It just selects if you'll use the gdb port or the uart port from the BMP. The target I'm talking about is what comes up when trying to do upload. Configuring upload protocol... AVAILABLE: blackmagic, cmsis-dap, jlink, nrfjprog, nrfutil, stlink CURRENT: upload_protocol = blackmagic Looking for BlackMagic port... Auto-detected: COM2 Uploading .pio\build\MyBoardNRF5\firmware.hex Target voltage: 3.45V Available Targets: No. Att Driver 1 Nordic nRF52 M3/M4 2 Nordic nRF52 Access Port 0x000020d8 in transportProcessFIFO() () Loading section .text, size 0x895c lma 0x0 Loading section .ARM.exidx, size 0x8 lma 0x895c Loading section .data, size 0x23c lma 0x8964 Start address 0x32e0, load size 35744 Transfer rate: 42 KB/sec, 916 bytes/write. Section .text, range 0x0 -- 0x895c: matched. Section .ARM.exidx, range 0x895c -- 0x8964: matched. Section .data, range 0x8964 -- 0x8ba0: matched. Kill the program being debugged? (y or n) [answered Y; input not from terminal] If I don't do #define MYBOARDNRF5 then PlatformIO complains about undefined reference to 'g_ADigitalPinMap', which is in compat_pin_mapping.h and is called from MyBoardNRF5.cpp when MYBOARDNRF5 is defined. But I see that your variant.h/.cpp is different than the ones coming with ArduinoHwNRF5, which I'm using. Maybe try your version instead and see what happens...

the Node To Node must be seen as a Gateway to node :) the controller is not mandatory. so we rethink the topology. Gateway (node0) <---> Node1 <---> Node2 <---> 3.. 4... The Gateway in 2022/2023 must be used, how to do!!?!! ...... a Node Useful :) (yes an old message, but to refresh the ideas ) happy holidays to you all

@Stig I wouldn't bet on anything soon.

@briseis I would just switch back to 2.3.2 I also believe 2.4 on the gateway should work with nodes on 2.3.2. what kind of errors did you get when doing this?

Hi @Soloam, not sure if you managed to solve your problem. I would recommend using Mosquitto MQTT broker open source or Pro version since they both support all MQTT QoS levels (including QoS 0, QoS 1, QoS 2).

Hello CAN Bus is still functional, and no problem. a question : is it possible to implement the use of 2 CAN Module on the same Gateway. 2 CAN bus or RS485 + CAN as for the RS485 in example for a Mega2560 board MyConfig.h ...... * Example: @code #define MY_RS485_HWSERIAL Serial1 @endcode */ //#define MY_RS485_HWSERIAL (Serial1)

@ncollins Impressive! Looks as though you even modeled the exact shape of the coincell holder. And you apparently designed the 3D printer snap enclosures as well. Even just the 3D printed enclosure modelling is quite a task all by itself. I hope to one day evolve into doing that too, but for now the Hammond enclosures are going to be my short-term solution. The smallest Hammond is still not as small as what you've managed to produce, but at 36mm wide for an off-the-shelf ABS enclosure, it's too wide by only about 10mm. Still.... one day I want to 3D print an enclosure to be as small as possible.

@mfalkvidd Thanks, I didn't see that! OSD

Great, thanks for your reply and help. I was able to do what I wanted, I give you some code snippets to make several messages via a for loop, I'm not a code proffesional but this works: // Initialize messages MyMessage msgInA(0,V_CURRENT); MyMessage msgWhA(0,V_WATT); #define NSENSORS 6 //used current sensors void setup() { //initialize energy monitor CurrentSensor for (int i=0; i<NSENSORS; i++) { wh[i] = { 0.0 }; //initialize wh lwhtime[i] = {0}; //initialize time present(i, S_MULTIMETER); } for (int i=0; i<NSENSORS; i++) { present(i, S_POWER); } } void loop() { for (int i=0; i<NSENSORS; i++) { send(msgInA.setSensor(i).set(Irms[i], 1)); send(msgWhA.setSensor(i).set(wh[i], 1)); } } Thanks

maybe this can be useful : https://forum.mysensors.org/topic/6948/synchronising-light-switch I use it with version 1requestState or 2 requestTime() on some sketches (I modified the structure, moved some parts to functions to make it more readable )

@alowhum Sorry, I have abandoned this project. It didn't garner the interest I hoped it would, and I’ve moved on to other microcontrollers/radios/networks since then. This is hosted on GitHub’s free static hosting, so it should continue to work as long as they are in business, and it should work on devices as it was 5-6 years ago. But I won’t be supporting it and won’t continue to build on it. Glad to hear that you like it!

@NeoX maybe your existing serial gateway connected to one of the servers, with usb over ip to your HomeAssistant controller would work?

Thanks for this interesting information!