-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MQTT_Port not working #49
Comments
Let me check that. The local MQTT is needed e.g. for homeassistant integration. Generally the --online mode gets not much attention anymore as offline mode has a lot more advantages. |
Yeah i already fixxed the problem with this config Sadly it can be just used with the main account where you have linked the HUB the first time. Shared devices arent working with the json {"code":400,"success":false,"data":{},"msg":"Please bind the device first"} So its not usable as im using the App on my phone. I guess i have to setup something similiar as the statuspage with ioBroker/VIS |
Who wants to fiddle with a mobile app anyways. That SFHub should do it's work without maintenance in the best possible way without interaction...that's at least the intention of these projects... |
The password env variable is MQTT_PWD not MQTT_PASSWD |
Use your main account to bind and the secondary account to connect via the status page. Works for me too. |
When i use the main account to get my mqtt data i cant use it on the phone |
Use your main account to bind (curl) and the secondary account to connect via the status page. |
Hi guys,
i have the statuspage running on my Synology NAS. Sadly this MQTT_PORT env isnt working
Dont know why this is the case. Problem is that i have multiple MQTT Server on my nas. I dont even know why i have to set a MQTT as i use --online
The text was updated successfully, but these errors were encountered: