Thats a bummer! I had read that somewhere too way back.
Using Myscontroller and it used to work OK but now it never reports messaging. In the debug it always reports:
27/05/2018 14:24:42 INFO Connected to 192.168.1.9:5003
27/05/2018 14:24:43 ERROR Error on connect: connection refused
I have a username and password set on the mosquitto server. Should these be entered to the Myscontroller.ini file? And if so how is it done?
Yes I definitely built another MySensors gateway...trying to access a back shed with a metal roof...radio just not making it.
I attempted to create separate mqtt devices in Home Assistant (controller I am using) under the MySensors gateway component but it complains.
Do you have any suggestions there?
Thanks again for your help.
How many MySensor servers are allowed in the network?
I have added a server to an existing working installation on a different channel and now it seems nothing is working!!
Both servers are RPi based and the original one was an ethernet based one and worked fine.
I have changed both servers to be MQTT and they are based on 2.3 development branch. I've also changed all nodes (there is only 3 of them) to a fixed Node_ID.
I will post logs etc if someone can indicate whether multiple servers are valid. I thought it would be OK based on the use of a separate RF channel but I think the problem might lie in the routing table and it's interaction with the MQTT server. In other words there are two Node 0's in the network.
Installed development version and all working 100%. Thanks for the help.
I had a perfectly working MySensors Pi Gateway working on Ethernet alongside a Home Assistant install on the same Pi.
I decided to upgrade the Home Assistant to the latest Hassbian image which meant reinstallation of MySensors. Everything installed OK however now MySensors fails to talk to the radio. Nothing was physically changed on the Pi so I'm reasonably certain the radio and wiring are OK although I have since added a cap on the power supply pins.
Here is the debugging output:
pi@ShedHA:~/MySensors $ ./bin/mysgw -d mysgw: Starting gateway... mysgw: Protocol version - 2.1.1 mysgw: MCO:BGN:INIT GW,CP=RNNG---,VER=2.1.1 mysgw: TSM:INIT mysgw: TSF:WUR:MS=0 mysgw: !TSM:INIT:TSP FAIL mysgw: TSM:FAIL:CNT=1 mysgw: TSM:FAIL:PDT mysgw: TSM:FAIL:RE-INIT mysgw: TSM:INIT mysgw: !TSM:INIT:TSP FAIL mysgw: TSM:FAIL:CNT=2 mysgw: TSM:FAIL:PDT mysgw: TSM:FAIL:RE-INIT mysgw: TSM:INIT mysgw: !TSM:INIT:TSP FAIL mysgw: TSM:FAIL:CNT=3```
@gohan the benefits are probably marginal if you are competent in linux and have been using HA for a long enough period. In my case I only come back to it occasionally. It means some re-learning is necessary every time. The Hass.IO setup is relatively painless (although not perfect) and then there is a lot more intuitive control of what is happening with the controller.
@martinhjelmare is spot on with his description of what Hass.io is for. I suspect this, in the long run, will be the best way for controllers to work - gradually automating the automations - so the middle of the road hobbyist will be able to stay in the game.
I've setup the MySensors server on a spare Pi and that is good for me. I think it would be nice to have the server available as an add-on in the Hass.io server if anyone was up to the technical challenge.
Thanks for your input.
I have been happily running a Mysensors ethernet gateway on a PI that also hosted my Homeassistant server. I decided for various reasons to change over to Hass.io to host the Homeassistant server. That is all set up and working nicely.
I would like to re-install the Mysensors ethernet gateway on Hass.io
For those that don't know Hass.io is built on Resin.io which uses Docker containers to run applications. There is detailed information on how to access the GPIO pins. That suggests applications like the Mysensors gateway might not run out of the box.
Has anyone had experience with this? I'm happy to experiment but it would be nice to know it can be made to work before I embark on the exercise.
As a suggestion could the documentation be changed from:
By default, the gateway is built for ethernet and it listens on port 5003:
By default, the gateway is built for ethernet as a server and it listens on port 5003 for controller connections: