Hello, sorry to bring this topic back from the grave, but did you managed to do this! I also have a use case for a raspberry pi zero w as node! Is this possible? And will I be able to react to a mysensors income message with a scrip in the pi? I want to send some tcp packages by wifi when a specific message arrives. If this is not possible I will need to make this kind of solution but with a esp8266, but since I have some pies already doing this job I would prefer to do with them! I want to bypass the need to have the controller online to this specific message!

Thank you

Yes it is! I use I'm using it as a MQTT gateway for some time

@tbowmo yeh I know that! The main purpose of this topic was to give out my thank you to all the community. I remembered the "subscription" (I didn't wanted to use this work because it sounds like obligation, and that is not what I intended... but I think that my English vocabulary is starting to fade out... ) because I had a active role one a community a long time ago and from my opinion it was always better to have a 10 users subscribing 1 dollar monthly, that 1 user donating 50 dollars randomly! Membership its always a way to bring people closer to the projects and helping out

I've been on MySensors for some time now, and during this time I "evolved" from a guy that normally added a new outlet to my house, to someone that now understands a "bit" more of electronics and even developed and build my own IOT devices/nodes. This has been a hell of an experience, and I only have to say thank you to all the staff, developers, and community members that help not only this project grow but also all of us (intellectually and in this hobby).

I know that the main focus of this community is not to make a profit, but lets face it, every thing in this world needs a bit of juice ($$$) to make it flow. So I came up with an idea, why not add a way to sponsor this project? Something like Patreon or a membership? It would be totally optional, but the members would have access to for example give aways or something. And what would you guys do with a money? Easy free beer... ...

The money could be used to pay for hosting (damm this things can get expensive when a community grows... respect @hek) or to help guys like @tbowmo (sorry to all others just the first name that got to my mind when I was typing) to develop new prototypes and get them at low prices to all of us!

Basically this post is only to say thank you to all of you guys that helped this community get where it is, by developing the software or by developing the hardware (too many people to name in openhardware.io.

255;255;3;0;18 (this is nerd...)

I'm having difficult finding the IC4 ACS712_5A, if I search for "ACS712 5A" I only get the assembled unit. Can I get one of this and unsolder the IC and use it?

Thank you @David-Muller

Hello all, I'm using Nodered with a MQTT Gateway, and I'm planning on changing to a TCP Gateway, does the Mysensors node support TCP Gateway? I would like to remove MQTT from the mysensors equation to remove some complexity (on less service running and depending on), but On the Mysensors Node on NodeRed it seams that only supports MQTT!

Thank You

Thank you @martinhjelmare it was that! One last question that I don't know if it's related! The first time that HA discovered my nodes (power cycle) the created items where with a toggle switch and under a card named lighs (I think that it was that). Now I deleted the mysensors.json file and added the items again, and now they are detected as interruptor and the switch is a lightning bolt. No major problem in that, just trying to understand the reason... It's the same nodes, no code changes.

Thank You

Ok, I made a test adding manual, and it works... the problem is in the auto added switches

switch:
  - platform: mqtt
    name: "My Light"
    command_topic: "mygateway1-in/1/2/1/0/2"
    payload_on: "1"
    payload_off: "0"
    optimistic: false
    qos: 2

All works ok! With the auto added switch I click on... the light comes on, and immediately the switch goes to off... Only 30 seconds later (my node sends a updated status message every 30 seconds) the node goes to ON (the real state)

Hello, I was planning to move away from OpenHab to Home Assistant and I started configuring my nodes in HASS. I have the MQTT up and running, and I have it configured in HASS, they appear and I can controll them. The problem is a lot of miss messages. In OpenHab I was able to do ON OFF ON OFF fast and the lamps would go on off, "never" (rarely) missing a cycle. In HASS I turn on the lamp, but when I go to put off it fails.

I remember in OpenHab I had to make a small tweak to the config to make this work, QOS 2 and turn off asynchronously.

What are your experiences with MQTT GW and the response time and viability?

Thank you