Home Assistant

Hello, finally, ... I had time to test the "Option 2". Because the stock of all shops are empty, I used my old RPI 3 B+. But after all, the CPU runs at 50%. Even the 1 GB ram is half free. The way wasn't as easy as I thought. But now the setup runs pretty good. This steps I had to make: A fresh install of Raspian Lite (I used 64-Bit, if this is needed? I dont know) Installed "Home Assistant Supervised", which runs in a docker. (I found a tutorial based on this informations: https://github.com/home-assistant/supervised-installer) Installed the MySensors Gateway with some changes! (https://www.mysensors.org/build/raspberry) 3b. The manual works fine for 32 Bit raspbian. For 64 Bit you have to edit two files bevor the compile starts. (https://forum.mysensors.org/topic/11456/is-mysensors-rpi-gw-32bit-only/8) In my case i have to change the section for the BCM2837 (= RPI3) as described in the post. Now, I have a clean setup for my smarthome with MySensors Nodes and Zigbee Nodes. [image: SmartHomeRaspi.jpg] The RFM69 ist directly connected to the GPIO of the PI. The power consumption is araound 2 W. Somewhat lower when idle.

The only think I'm able to do is to enable everything to mode "DEBUG" [image: 1672606199944-fe9fb961-e9f9-4de4-9e24-bdd609483890-image.png] I'm not able to SET specific LEVEL to DEBUG mode for MQTT, MYSENSOR, SERVICE. [image: 1672606663715-90f6b3ae-c38a-4169-b0ac-bd5f0fb0c745-image.png] [image: 1672606690740-a647993f-2143-44be-a913-10749cda33a9-image.png]

Thank. This is what I do for the receive : [image: 1672605669747-31c2265b-1a7d-4f2f-8121-d96075f7335e-image.png] So, I'm now able to SET a VALUE from HA. [image: 1672605922523-e5adb4bf-dcb8-4c64-85df-a3c28e3ef6f0-image.png] And after a pulse it is updated [image: 1672605973930-da8e2ee9-f1af-401d-b82e-7f74e02af8aa-image.png] My question is most about how to use HA to do it more easily as possible. Do you think possible to use an TEXT object which can be sent to node through the MQTT ? Second question : how do you send value to the node (MQTT or other ?)

@OldSurferDude I posted this question in the Home Assistant forum, too. I figured it out! See my post in HA OSD

@OldSurferDude The complete wipe seems to have worked. I also changed the version on HA's integration to 2.3 to match the MySensors library I use on the sketches. Thanks for the workaround.

yes HA or (Hassio ) and not very friendly with MySensors. the "Persistence" function of the sensors and the rewriting of the sketches ( for the validation of the messages) and a constraint. Persistance No MyS is not dead, we are La! and for "Do I have to rewrite all my scripts, automations, models, etc..." ... it is perhaps the safest, cleanest... give us the result! Ask on the HA/Hassio forum for a solution? you are in mode #define MY_NODE_ID "static" for the nodes??

@electrik Thanks, I think I can do the same with the MQTT integration (not MySensors MQTT) OSD

great it works! Here the steps to delete a node are described: https://forum.mysensors.org/topic/10898/can-t-remove-unused-sensors-from-ha/7

wait (5); c'est mieux ( pas d’interruption du pgm)

You can't do what you want using that sensor - The sensor is just a simple on/off type sensor that tells you if the sensor plate is wet or not, it does not measure how much rain is falling. Even if you timed how long it was activated how would you know between heavy rain and a light shower? You need a 'tipping bucket' type sensor to give you an estimate of how much rain there has been, but even then you need to do some work with experimentation to get reasonable accuracy.

Thanks for all the answers! Finally i managed to get it work. The reason for this issue was that a wrong serial port was entered in the input field of the MySensors Serial gateway setup window in Home Assistant. By default it was /dev/ttyACM0 however it turned out that it was already used by some other dongle.

Ignore me... the mysensors API version was set to 1.4 :face_palm:

Ok, I've made some digging on Home Assistant GH and found out it's not a bug but a feature, but they just haven't put any info about the change to their documentation: https://github.com/home-assistant/core/issues/62703 Long story short, to use the notation “[Sketch name] [Node id] [Child id]”, there should be no sensor description in presentation(). This is supposed to work with “[Child description]” notation: present(NOTIFY_SENSOR_ID, S_INFO, "Child description"); And this with “[Sketch name] [Node id] [Child id]” notation: present(NOTIFY_SENSOR_ID, S_INFO);

During a multiple value assignment, the ValueError: not enough values to unpack occurs when either you have fewer objects to assign than variables, or you have more variables than objects. This error caused by the mismatch between the number of values returned and the number of variables in the assignment statement. This error happened mostly in the case of using python split function. Verify the assignment variables. If the number of assignment variables is greater than the total number of variables, delete the excess variable from the assignment operator. The number of objects returned, as well as the number of variables available are the same. To see what line is causing the issue, you could add some debug statements like this: if len(line.split()) != "xx": print line This will resolve the value error.

Yes now I understand what you mean, the nodes itself don't go away on my installation either.

@Dbagioni Maybe you did not map the device file (/dev/ttyUSB0) to the container, check this: https://www.home-assistant.io/installation/raspberrypi#exposing-devices