@waspie I like it when people come back and share their experience. It's helps newbies like myself get direction in our own projects. So thank you :)

@skywatch hah, tell me about it. it went through battery and all. Still dutifully reporting every 3 minutes.

@nca78 If you're talking about the basic motion sketch - I've tried it and it doesn't work The node checks in when initially powered but i can't seem to trigger it...

Make sure you don't have two controllers running. That will split the messages between them randomly.

Is this possible?

@yveaux Thanks for the hint and explanation. I appreciate that! I always used the search term: "conversion" (English is not my native language). I tried "casting" in combination with "c#" and I was almost immediately directed to my favorit c++ internet source (cplusplus.com) http://www.cplusplus.com/doc/tutorial/typecasting/ Many thanks! :+1: Boozz

@timo said in Questions regarding smartsleep/request heartbeat/request ack?: I'm using rules to detect if a thing changes its status to offfline You wrote the 2.4.0 binding, right? If so...I'm getting this error if I add a Mysensors MQTT GW while mysgw is not running: 12:51:49.096 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - 'mysensors:bridge-mqtt:13cd0a37' changed from INITIALIZING to OFFLINE 12:52:02.804 [ERROR] [ransport.mqtt.internal.ClientCallback] - MQTT message received. MqttMessageSubscriber#processMessage() implementation failure java.lang.NullPointerException: null at org.openhab.binding.mysensors.internal.protocol.mqtt.MySensorsMqttConnection$MySensorsMqttSubscriber.processMessage(MySensorsMqttConnection.java:134) ~[?:?] at org.eclipse.smarthome.io.transport.mqtt.internal.ClientCallback.lambda$3(ClientCallback.java:90) ~[207:org.eclipse.smarthome.io.transport.mqtt:0.10.0.oh240] at java.util.ArrayList.forEach(ArrayList.java:1257) ~[?:?] at org.eclipse.smarthome.io.transport.mqtt.internal.ClientCallback.messageArrived(ClientCallback.java:90) [207:org.eclipse.smarthome.io.transport.mqtt:0.10.0.oh240] at org.eclipse.paho.client.mqttv3.internal.CommsCallback.deliverMessage(CommsCallback.java:499) [206:org.eclipse.paho.client.mqttv3:1.2.0] at org.eclipse.paho.client.mqttv3.internal.CommsCallback.handleMessage(CommsCallback.java:402) [206:org.eclipse.paho.client.mqttv3:1.2.0] at org.eclipse.paho.client.mqttv3.internal.CommsCallback.run(CommsCallback.java:206) [206:org.eclipse.paho.client.mqttv3:1.2.0] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?] at java.lang.Thread.run(Thread.java:748) [?:?] This is a quite vanilla install with only the Mysensors binding for testing.

@olka Can't say I remember what I did anymore. Probably suppressed sending in the case of 85 degrees.

@waspie almost. The gateway does not store anything though. Storage is handled by the controller.