💬 Serial Protocol - 2.x

[siod]

@gvorster Thank you for explanation!

One more thing: I wanted to implement a sendHeartbeat() into a Repeater node (which should never sleep!), where should I put this function and how? When putting it just into the loop it is of course spamming my gateway with heartbeat messages...Is it possible anyway?

[gvorster]

@siod said in 💬 Serial Protocol - 2.x:

@gvorster Thank you for explanation!

One more thing: I wanted to implement a sendHeartbeat() into a Repeater node (which should never sleep!), where should I put this function and how? When putting it just into the loop it is of course spamming my gateway with heartbeat messages...Is it possible anyway?

There are many examples code how to do this. One Timer library I use myself is this https://playground.arduino.cc/Code/Timer

e.g. for a repeater you could use this:

#include "Timer.h"

Timer t;

void setup() {
    t.every(60000, sendImAlive);
}

void loop() {
    t.update();
}

void sendImAlive() {
    sendHeartbeat();
}

[shabba]

What is the best for a push button? I have a button to open a lock. The button cannot lock the lock however. So binary is not really a proper option?

[hek]

ATM scene controller is probably the best option.

https://github.com/mysensors/MySensors/issues/724

[dmurphy]

S_SPRINKLER is defined as having V_STATUS and V_TRIPPED - no V_ARMED....but V_ARMED says it is in S_SPRINKLER...Which way should I code this up for my controller??

[jjk]

Hi there,
do you know that, you've built a node like a 100 times and I think it's all routine and then something that completely bluffs you? I happened to me with a simple Temp/Hum node (DHT22) that keeps sending me messages that I can't seem to figure out: 43;255;3;0;33;300000 and 43;255;3;0;32;500 - They seem to show up in the frequency that other nodes send a heartbeat signal, but no heartbeat is sent from this node. The regular DHT22 datapoints are sent as normal. Anyone knows what this means?

[gohan]

Are you using smart sleep?

[jjk]

yes, I do - like on every other DHT node as well, but never had that...?! Plus, I can't seem to figure out what the messages mean.

[gohan]

I assume the 300000 is the sleep time you set while the 500 is the smart sleep embedded 500ms wait that lets the controller know the node is about to go to sleep but it is going to wait for 500ms for queued commands to be sent to the node

[jjk]

hm, you might be right on the 300000 as that#s indeed the smartsleep wait time I'm setting. Not sure about the 500, but certainly possible (is that documented somewhere?) I'm wondering, though, why this node is sending this info, but not the other ones?! I don't think I have changed anything t the sketch other than the node-id and node name...

[gohan]

500ms is the default setting when using smartsleep

[jjk]

o.k., fair enough, that's a great explanation! - I'm still struggling, though, with why this node is sending this (but no heartbeat), but none of the previous ones I did...

[gohan]

Try reflash the older node, maybe you updated library or else. Why do you need heatbeat if the node is sending every 5 minutes?

[jjk]

@gohan fair question, I don't need it, it's just still in the code and besides, the 5 min message from smartsleep seems to show up every two mins (the heartbeaat rate)
And yes, I did indeed update the library, so maybe that's why. Turns out, the bigger problem is that these message seem to cause an exception in the openhab mysensor binding, so at best I'd like to figure out how to stop the node from sending them... Will do some digging

[gohan]

Are you sure it is the smartsleep? Since you are debugging, use https://www.mysensors.org/build/parser to decode messages to a more human readable format

[jjk]

yes, I am sure now: https://forum.mysensors.org/topic/8933/mysensors-2-2-0-released/27

Looks like the only way to eliminate the messages is to not use smartsleep ;)

[gohan]

You may need to get in touch with openhab binding developer to fix that

[jjk]

@gohan yes, have done that. Thanks for your time and support!

[itbeyond]

I am investigating a problem I have found with I think openHAB but I am not sure if this issue is not related to the Gateway code of 2.3.0.
When a node performs a requestTime() I am seeing this reported:

2018-10-09 10:47:13.337 [INFO ] [rs.internal.gateway.MySensorsGateway] - I_TIME request received from 2, answering...

Looks perfect and the node receives the time however I was curious as to why sometimes the node would receive GMT and at other times my local timezone GMT+8. I decided to run the gateway via MYSContoller so I could monitor and log the traffic and I have found the problem. When the Gateway receives the request it responds twice within a few ms of each other, for what reason I do not know but the first response send the local time zone response (GMT+8) and the second is a GMT response. The logs from MYSController for the above report are as follows:

318857 9/10/2018 10:47:19 RX 2 - Irrigation Ctrl (2) INTERNAL C_INTERNAL NO I_TIME
318858 9/10/2018 10:47:19 TX 2 - Irrigation Ctrl (2) INTERNAL C_INTERNAL NO I_TIME 1539082039
318859 9/10/2018 10:47:19 TX 2 - Irrigation Ctrl (2) INTERNAL C_INTERNAL NO I_TIME "1539053233

"
Note the quotes where picked up in the copy and paste (I did this several times) so it looks like the body was changed to a string type but I also caught this in the MYSController Debug:
9/10/2018 10:47:19 RX 2;255;3;0;1;
9/10/2018 10:47:19 INFO Reply time request
9/10/2018 10:47:19 TX 2;255;3;0;1;1539082039
9/10/2018 10:47:19 FWD 2;255;3;0;1;1539053233
9/10/2018 10:47:19 TX 2;255;3;0;1;1539053233

So I am curious as to where the FWD comes from and why the response body has changed between the TX, FWD & TX?

[tonbor]

Is there a type to present in mysensors for solar radiation w/m2. Got a veml6075 sensor. And domoticz has a solar radiation sensor type.