miscellaneous question

[JeeLet]

Re : Field Label SensorID and spaghetti

miscellaneous question ???
yes the other post is overflowing

Hello jkandasa

as you may have seen, I am still active with MySensors and MyController
This is with the CAN-Bus ..CAN bus... a very useful thing that MySensors and I miss

So I test and test, I add and remove regularly nodes and gateway, MyC and put to the test, but it holds good
Well, today I had to start over on a clean beach, a clean reinstall, the ghost nodes did not want to leave

Questions :

can we improve the selection of resources?
yes the problem is that the frame is too small ( see the 1st image of the file )

and why sometimes some sensors don't want to remobter on MyC
( see the 2nd image of the file )
pdf dessin

autre lien pdf

thanks

Re-
after 2 hours still nothing on the node55 (test reset reboot)
I reloaded the sketch and MyC recognized the 55!

I don't understand

[jkandasa]

@JeeLet

can we improve the selection of resources?
yes the problem is that the frame is too small ( see the 1st image of the file )

It is limited to display only 10 response, if you want to narrow down the result you can use different filter, for example, If you want to filter a node with id 56 and gateway id GwCan. in the filter box type gateway=GwCan,nodeid=56
you can filter with any available keys,
some of useful keys

• gatewayid
• nodeid
• sourceid
• fieldid

and why sometimes some sensors don't want to remobter on MyC
( see the 2nd image of the file )

For some reason, the name of the node is not received and kept it empty, I have fixed this in MyController, now if name not received by MyController, will be displayed as unknown

Re-
after 2 hours still nothing on the node55 (test reset reboot)
I reloaded the sketch and MyC recognized the 55!

On this gateway you see the problem only with the specific node(55)? If you receive nothing from the gateway, just reload the gateway and see how it goes?

[skywatch]

@JeeLet said in miscellaneous question:

So I test and test, I add and remove regularly nodes and gateway, MyC and put to the test, but it holds good
Well, today I had to start over on a clean beach, a clean reinstall, the ghost nodes did not want to leave

after 2 hours still nothing on the node55 (test reset reboot)
I reloaded the sketch and MyC recognized the 55!

I have had 'ghost nodes' in MC ver 1.6.0 - These are nodes showing in the list that do not exist in real life. I am hoping that a new SSD sata to USB adapter has cured this for me. Note I also went from 2 gateways back to one. Even with external power supply there was still an issue on booting with both gateways attached.

If you are testing a lot of things please remember to use the mysensors 'clear eeprom' before reusing a node or gateway, it can cause issues if previous data stored in there (like routing table) are not removed before re-flashing. Maybe you already do this, but is worth mentioning anyway.

[JeeLet]

I took my time to answer you, test and verify before .

skywatch

• Yes, deleting the EEprom is something I do.
• and for the ghost "elements", it's because sometimes I physically delete an "element" before deleting it in MyC
  (but even then it's not sure, to check)

jkandasa

• thanks for the solution : ".... use a filter .... gateway=GwCan,nodeid=56 "

• "...you see the problem only with the specific node ( 55) "
  The problem is solved ( it was on MyS_CAN side )

question (again )

here is a screen shot of the problem, the status of the gateways. screen

they are well functional, in the page Gateway the visual status is well in green (activated") but in the page of the Nodes, the gateway are in red.

after a command : > Action > Reboot of the Gateway and they become green again ( but not for long )
(in the logs there is nothing )

Edit
I think it's the presentation void in the Gateways sketch that MyController doesn't like

void presentation()
{
	 sendSketchInfo("GatewaySerial-CANbus", "2.0");
}

Re-edition
no it wasn't that, I deleted that part

But the problem comes back to the goal of half an hour

[jkandasa]

@JeeLet said in miscellaneous question:

they are well functional, in the page Gateway the visual status is well in green (activated") but in the page of the Nodes, the gateway are in red.

The page of the node, it is a status of the node. not the gateway. The default inactive interval is 15m,
But you can update the global inactive interval in Settings >> System >> Edit

You can also update this interval for a specific node by adding a label in that node. example: inactive_duration: 5h, == 5 hours,

If there is no message received in a specific period(aka inactive_interval) from a node, that particular node marked as Down. When new message arrives in that node, again the status changed to Up.

[JeeLet]

I have nothing, not understood everything.

so the Arduino that I connect to my Odroid
is not only a gateway (a bridge)
but it's also a Node, but that is not used ?

you can give me a small piece of sketch that I place in the "gateway" for me MyC think that the Node 0 is used for what things.

But maybe I will test the node to node (0 with 55) to check the reliability of the CAN bus, a cyclic thing.

question:
there is a LOG file to recover the information of Active/Inactive ???

Thanks

[jkandasa]

@JeeLet This is just an indicator that your node didn't send data for a specified period of time and marked as Down. But nothing affected in functionality. It is just a visual indicator, MyController assumes that your node is Down, as it is not receiving any data for a while. This status will not impact anything.
Please let me know, if still, this is not clear, I will try to explain in different way.

there is a LOG file to recover the information of Active/Inactive ???

There is no log for this

[JeeLet]

Hello jkandasa
thank you for your pedagogical patience

But the gateway, basically, its primary function is a bridgehead between the constellation of sensors MyS and MyC.

it doesn't have to be a node,

and for "This is just an indicator" for me Green=cool, Red=danger ..... an Orange for "you have seen"

on the other hand not being able to use this feature of the "no data" indicator routine is a shame.

Can you use it for a time stamp to monitor the nodes?

Yes MyController is good ... More questions soon

Thanks

[jkandasa]

@JeeLet said in miscellaneous question:

But the gateway, basically, its primary function is a bridgehead between the constellation of sensors MyS and MyC.
it doesn't have to be a node,

MySensors gateway can be a node too. So we have created a node with id 0. Example: https://forum.mysensors.org/topic/4765/the-sensor-network/41

and for "This is just an indicator" for me Green=cool, Red=danger ..... an Orange for "you have seen"

To understand quickly I mentioned that it is just an indicator. beyond this, you can trigger a task based on the node status change.
example: perform gateway reload if there is a node status changed to down(in mysensors node 0), send telegram, etc.,

on the other hand not being able to use this feature of the "no data" indicator routine is a shame.

I do not get this question. Can you please elaborate?

Can you use it for a time stamp to monitor the nodes?

Node status updated using lastSeen. When there is a message received for the node, LastSeen has been updated.

[JeeLet]

Ouch
the translation of the languages, or the puns are not clear

I simplify my text, and also you have partly answered my question.

how to use "LastSeen"
. to make an action. but how?
. the value can it be put in a widget, for a synoptic with the dashboard
( to have a dashboard of some elements of the system, monitoring on a single page of several different families, states and temperatures

the concept of
synoptic
supervisor

to have on the same page, an overview of the important elements.
. System alarms (MyS, status of nodes and other elements)

• Equipment alarms (house, temperatures, intrusion ...)