@marceloaqno I am also recompiling and testing.
thanks for the (hopeful) fix
I will report back with my status in a few days

happy to test.. alpha1 still running on my VM

And the winner appears to be flaky sensor.
I replaced for a 3rd time and it seems to be working correctly now.

for me these PIR's fall in to 1 of 3 categories.

1. works correctly
2. only works when time out is turned all the way down to 0 (so it constantly sets and resets, any amount higher and it doesn't trip at all)
3. hardware timeout works, but sensor trips right after it's un-set

I guess i'm glad i bought these in bulk.. i will replace the other 3 or 4 that are not working as they should.

looking for some help with OTA and a sensebender board.
if i manually reset the board, then it will take the OTA and that works fine.
however, that's the only way i can get it to work.
it doesn't respond to a reboot command (I assume this is because it's sleeping)
and even if i select the battery/sleeping option, when a transmission does come in, it doesn't reset or start an OTA.
the only way so far is to physically PF the device and then the OTA works.
what am i missing?
thanks!

EDIT: so this does seems to work.. i spent all morning trying to come up with hack-y ways to get this to work.
using the default sensebender sketch the OTA wait time is set to 300 milli seconds. which is like .3 seconds.
i changed that 3000 (3 seconds) set the FW and waited for the next transmission..boom off it went (the OTA).
so for anyone running into this issue. try this solution.
I cant imagine 3 seconds vs .3 seconds is going to make a huge difference in battery life.

@jkandasa

Thanks for the info. I'm not sure what was wrong. when i looked at my password, it was the encrypted one you posted above.
i ended up just removing everything and copying up the files from scratch. and it's working now.
thanks!!

https://forum.mysensors.org/topic/2759/mysensors-raspberry-port-suggestions/12

what about that one?

@peerv said in sendBatteryLevel not showing up in HA dasboard:

@mfalkvidd
Thanks, yes your solution could work. Also a voltage divider with a seperate child-id could work.

But my point is that the Arduino battery_level value is already available in the mysensors.json in Home Assistant.

"type": 17,
        "sketch_name": "N60Breed",
        "sketch_version": "1.0",
        "battery_level": 91,
        "protocol_version": "2.3.1",
        "heartbeat": 0

I just don't know how to get the battery_level value presented in the HA UI.

you have to use a template.
under the sensors section

• platform: template
  sensors:
  computer_room_15_0:
  unit_of_measurement: "%"
  entity_id: sensor.computer_room_15_1
  icon_template: mdi:battery
  value_template: >-
  {%- if states.sensor.computer_room_15_1 != None -%}
  {{states.sensor.computer_room_15_1.attributes.battery_level}}
  {%- else -%}
  0
  {%- endif -%}

@Dreded thanks for the link. i wish it had a spot for an external antenna but i suppose it would be good enough to get it out of the way.

@mfalkvidd @Nca78 I already have the Rpi 3 as a gateway, I also have a serial gateway (arduino) not in use.
my goal is/was to combine tasks. i have several intel nuc type PC's that have free resources. so i wanted to eliminate the uni-tasker and move it onto an existing pc.
at $9 cost is not a factor.
is the gateway code ARM only? or would it compile on x86?
if it's going to be a huge under taking, i won't mess with it. i have to many other projects at the moment.
i just didn't know if it would be an easy conversion.

currently i'm using an RPI3 for mysensor gateway, i would like to move the gateway off the pi and to a small linux pc that i have. but it has no gpio ports for the NRF module.
does anyone know if i could use something like this instead?
https://www.amazon.com/NOYITO-CH340T-Adapter-NRF24L01-Wireless/dp/B07DQBRBCM

@peerv in my situation, if i click on any of my child devices, like temp, lux, humidity, etc. i can see the battery level. so i have to create a new sensor, in this case i'm creating computer_room_15_0, and i pull the value from child 1, i could pull it from 2,3 or 4, but i chose 1. and the value that i'm pulling is an attribute of child 1 called battery_level
now that i have created that sensor. i can place it where ever i want.
so the newly created sensor computer_room_15_0 is my entity_id that can go in a card or whatever.
before you do that, i would trouble shoot in the following way.

1. pick a child device and open it, ensure you can see the battery level.
2. create a new sensor based on the template above (restart after)
3. go into the the states dev tool page and ensure it's there and has the correct value.
4. if yes, then open the standard states based screen see if it shows up at the top in the circle.
5. if yes, put that entity in your lovelace ui as you see fit, if no, go back and figure out where it's not working.
   you can also tail the log file and you restart and look for any error messages that may offer a clue to why.
   here is my states screen for the battery sensor.
   

then under groups
computer_room_group:
name: Computer Room
entities:
- sensor.computer_room_15_0
- sensor.computer_room_15_1
- sensor.computer_room_15_2
- binary_sensor.computer_room_15_3
- sensor.computer_room_15_4

@peerv said in sendBatteryLevel not showing up in HA dasboard:

@mfalkvidd
Thanks, yes your solution could work. Also a voltage divider with a seperate child-id could work.

But my point is that the Arduino battery_level value is already available in the mysensors.json in Home Assistant.

"type": 17,
        "sketch_name": "N60Breed",
        "sketch_version": "1.0",
        "battery_level": 91,
        "protocol_version": "2.3.1",
        "heartbeat": 0

I just don't know how to get the battery_level value presented in the HA UI.

you have to use a template.
under the sensors section

• platform: template
  sensors:
  computer_room_15_0:
  unit_of_measurement: "%"
  entity_id: sensor.computer_room_15_1
  icon_template: mdi:battery
  value_template: >-
  {%- if states.sensor.computer_room_15_1 != None -%}
  {{states.sensor.computer_room_15_1.attributes.battery_level}}
  {%- else -%}
  0
  {%- endif -%}

FYI looks like on the 2.3.1 beta the transport has been changed to rf24 instead of nrf24

@mvader said in queuing and sending messages:

I want to be able to issue commands (reboot, firmware update, etc) and when they wake up to transmit via motion or ti

can anyone point me in the right direction?

I have several battery powered nodes. I want to be able to issue commands (reboot, firmware update, etc) and when they wake up to transmit via motion or timed sending of data. they receive and execute whatever command i have sent. so far i can't get this to work. if i send a reboot command from the controller during the OTA wait period. the node receives the request and reboots.. if the OTA period is over, then the node never follows the command. even after waking up. it still never executes said command.
so it seems the gateway is not queuing up the command or it's not sending when the node wakes up.

what is the correct approach to implement this and how can i troubleshoot if the GW is receiving, queuing and sending commands for a sleeping node?
running lib 2.2.0
and the gw is 2.2.0 on a RPI3

Thanks!