Home Assistant

@martinhjelmare This was indeed the problem. Thank you for your help.

I guess this thread should be in the hardware forum. But if someone find this thread i can share some pictures and the idea with this node. I built it as a USB-stick with a USB-connector on a prototype PCB. Not good looking but when i get my TV up on the wall you can't see it. I use it to turn on light in the bathroom at night if my kids visit the toilet. [image: 1491467717203-img_20170406_102320-resized.jpeg] [image: 1491467726373-img_20170406_102342-resized.jpeg]

@tjkerr Hi! You can add print statements of the different variables to the receive method to see more what's going on. Also, I suggest you post the serial logs and home assistant debug log and your full sketch, to help me or others to troubleshoot this better.

that is used later in the presentation

@kincaidj001 Home assistant supports serial, ethernet and mqtt gateways. You can have multiple gateways connected to home assistant at the same time. The gateway connection type decides how the controller should communicate with the gateway, but it doesn't change the mysensors serial API. Messages between gateway and controller will still have the same structure. They will just be sent over different transport protocols. The controller doesn't care about what type of device is on the other end, it only cares about the transport protocol and the serial API to use for messages. Regarding choosing gateway type, I suggest you try something and see how it works for you. Since you already have mqtt set up you could start with the ESP and try connecting it via Wifi+mqtt. A serial gateway is probably the easiest to set up. Just take care to match baud rate settings on device with controller, depending on what device you chose as gateway. Read more on the mysensors site.

@martinhjelmare Thanks for the help, it works!! I'm sorry for the late respons, I was busy

I knew that they are marked. But I didn't know the polarity. It could have been possible that Cap- goes to VCC on the radio, since in a full capacitor, there is a lack of electrons on Cap+, and very much electrons on Cap-, and also a lack of electrons on VCC, and very much electrons on GND, and the many electrons on the negative side should match the lack of electrons on the matching side of the other device - you see my point? So I was unsure. But Cap- to GND is clear and explicit, yeah.

No problem, glad to hear about user stories. Can you explain a bit more, what you mean with IR receive via dev panel? IR receive is a sensor type, right? It should be possible already to update any states in the states dev panel. Maybe I'm not following completely? Contributing in the form of feedback on what works and don't work is very appreciated. If you want to try Python, pull request for bug fixes or new features is also welcome. Thanks!

The AttributeError: V_TEXT error is solved in HA version 0.38.3: https://github.com/home-assistant/home-assistant/pull/5942 The other error seem to be from a hue device and this issue has a similar stack trace: https://github.com/home-assistant/home-assistant/issues/4994 Cleaning the hue bridge seems to be the solution. Regarding HA stopping to update mysensors after a restart of the ethernet gateway, this should be the same as this issue: https://github.com/home-assistant/home-assistant/issues/4891 We now have a fix for this in pymysensors: https://github.com/theolind/pymysensors/pull/67 HA is not updated to use this fix yet, but I'll try to do that asap. I'll update the issue and this thread when that is done. Regarding your gateway restarting when you restart a node or repeater, that sounds weird and not good. Could be a power issue at the gateway?

@martinhjelmare I made a PR. https://github.com/theolind/pymysensors/pull/80

Yes, with some imagination, you could probably make a template that would match the correct criteria, and use eg for a notification.

@martinhjelmare It works now! I think it is a hardware issue I have here, since I just put the decoupling capacitor in between the radio and the pin header socket. Checking that connection helped (pushing again in), and the presentation was correct now - including the sketch name.

@Efflon It can't be done during presentation cause the node isn't registered yet at the gateway at that time. Default settings in mysensors requires nodes to be registered before the gateway allows them to send in values. In mysensors 2.1.x setup is called after registration, so it is possible to use that for sending values, but I would still recommend to do it in the loop. Reason is, in some cases you want to resend the initial values, and then setup is not suitable as it's only called once. Eg if your're using the ethernet gateway and have local sensors on the gateway, when home assistant connects to the gateway, the gateway will re-run presentation and continue with the loop. But setup will not be called again, as it already has been called when the gateway was first started. So if you would send initial values of sensors in setup on a gateway, the sensors wouldn't show in home assistant, cause the initial values would already be sent by the time home assistant connects to the gateway. Best way, I think, is to use an if block in the loop where you send the values and then request them from home assistant. You use a boolean variable, that you can turn on/off, that decides if the if block should be entered. You have the boolean True by default, and then set it to False when you have received the initial values back from home assistant in receive. This is described in the example sketch here: https://home-assistant.io/components/mysensors/#presentation

When you invert the defines for relay, you are not only inverting how the relay will react on digitalWrite, you are also inverting how the state of the relay is reported back to home assistant. This is where the problem gets introduced. As home assistant on turn on action always sends a 1 as payload to the device, the device will now send a 0 back as state feedback. This will tell home assistant that the state should be off, instead of on. So it will be impossible to turn the relay on from home assistant. If you do want to invert the high/low behavior of the relay, you need to decouple the high/low defines from the state reporting 1/0, ie use different defines. If you want the device to be shown as a light in home assistant you need to present the device as S_DIMMER and send both V_PERCENTAGE and V_STATUS, in mysensors version 2.*. S_BINARY and S_LIGHT will be shown as a switch.

Well, the sun shines on a dogs arse some days. We've only gone and done it, HA dash with relay sw. can controll led from dash. I honestly have sticky stuff running down my leg. You have no idea how happy I am. For future reference. I was flicking the power to reset pi in between config changes. My mosquitto was not starting from boot, so nothing to connect to, hence the errors when the code was right. Also reset your nodes after a change. This my yaml for the following setup nodes are arduino nanos with nrf2401+ radio. (mysensors 2.0) gateway is esp8266 NodeMCU 1.09. Wifi with NRF2401+ Pi 3 hosts Home Assistant and Mosquitto broker. Installed with All in one image. mysensors: gateways: - device: mqtt persistence_file: '/home/homeassistant/mysensors4.json' topic_in_prefix: 'mygateway1-out' topic_out_prefix: 'mygateway1-in' debug: true optimistic: false persistence: true retain: true version: 2.0 mqtt: broker: localhost port: 1883 client_id: home-assistant-1 keepalive: 60 Righty. I'm off to play. Be back very soon when i get stuck. Cheers for now fella, thank you for all your help.

@martinhjelmare No problem, I'll try to get some more data. Regarding HA version, I'm always on the latest version (with one or two days delay).

@MaKin Hi! What arduino are you using as gateway? How have you configured the mysensors component in home assistant? So at home a similar setup is working together with home assistant, but at school it doesn't? What's the difference between the two environments, hardware and software -wise?

@abmantis I didn't make the initial mysensors implementation in home assistant that only supported sensors, but I made the refactor that laid the groundwork for multiple mysensors platforms in home assistant. About 5-10 people has been contributing to the mysensors component in home assistant over time. There's also the pymysensors package (not my creation either) that interfaces mysensors and home assistant. It's actually this package that holds most of the mysensors specific logic, like smartSleep. Here there's also about 5-10 people that has contributed. All help and feedback is welcome!

No, not directly. You have to update the sketch to use 2.0 API, according to eg this guide: https://forum.mysensors.org/topic/4276/converting-a-sketch-from-1-5-x-to-2-0-x Also take note of how initial values have to be sent as mentioned here: https://home-assistant.io/components/mysensors/#presentation If you update the example for 2.0, please repost it here, and I can update the docs, or even better make a PR directly to the docs at homeassistant.io.

@martinhjelmare Just discovered mysensors, it is pure awesomeness.