@skywatch Can you post the top of your sketch (the mysensors stuff)... I had the same issue some time ago where the sensor names that I had set in mycontroller got overwritten, most probably when I upgraded to a new release.. I fixed this by hard coding the sensor description names into the sensors presentation loop: See: https://www.mysensors.org/download/sensor_api_20#presentation (copy of the most important part below) Presentation The sensors should present themselves before they start reporting sensor data to the controller. Do these calls in your presentation()-function void present(uint8_t childSensorId, uint8_t sensorType, const char *description, bool ack); childSensorId - The unique child id you want to choose for the sensor connected to this Arduino. Range 0-254. sensorType - The sensor type you want to create. description An optional textual description of the attached sensor. ack - Set this to true if you want destination node to send ack back to this node. Default is not to request any ack. Description is the one for investigation..

@saturn house-out/#, house-in/# You should add this to both subscribe and publish topics. Can you show your MQTT client code?

@aliasjim I noticed the MYSbootloader defaults to PA level MAX. When i use this PA level with my nodes in normal operation they don't function eigther. I might try with a bootloader compiled with lower PA level, maybe, just maybe i will get lucky. Now i only need to find someone who is willing to compile it for me

@jkandasa I have fixed this. available in the docker container(2.1.0-devel). yet to update in executable.

@andyphan Are you receiving other messages from that node? recheck the node id once again

@jkandasa The purge in the Snapshot is working great.

@benya If I have two nodes (#1 and #2) and each has sensor with ID '21' and each node calls request(21, V_STATUS), which sensor values they will get from controller? Node #1 will get his node_1/sensor_21 value and node #2 will get his node_2/sensor_21 value? Yes, You can have any number of nodes with the same sensorId. When MyController receives a request from a node, it knows node Id too. node id will be added on behind the scene when you raise a request.

@jkandasa You fixed it!!, just tested, and gauges work perfectly again... Thanks!!

Thanks!!!

@Stephan35 Great!! good luck!, orangepizero is really great, and is powerfull enough to run mycontroller

@benya have a look on http://forum.mycontroller.org/category/24/scripts and TAG with SCRIPT

@njbuch Have you had any success?

@jkandasa Ah!, okay, missed that one, thanks!!

@anduril There is no direct options available. Let me have a look and update you

@Emenike https://forum.mycontroller.org/topic/371/json-parser/10 This is all I know about it so far.

@jkandasa I finally had the chance to test the SNAPSHOT and it works ! Now I have just to remember how to send the sensor states. Thanks a lot !

Works perfectly! You rock!

@TomG Thanks - I have a few pi2 running like that as they can't boot from SD, so I know how you do that. I have thoughts on what I can do next, but it is Mothers Day here tomorrow and I will be busy all weekend

@JeeLet said in vokoscreen: 2nd part of the video : non functional sorting column for the Nodes This issue has been fixed

back after tests with Hassio. Yes MyController in central core of my MySensors network, Motioneye for the Cam, Grafana (soon to be installed ) for value tracking. A solid choice ----> Video <----