Closed H-K-47 closed 11 months ago
@H-K-47 The script does not disable MQTT. Maybe there is a side effect inside the firmware, but that can only be answered by the shelly developers.
@H-K-47 maybe you provide soom more infos so that I can reproduce your problem
@H-K-47 what firmware version do you have? I have 1.1.0-beta2
V10.16.1 should improve uninstallation: just set mode to none and redeploy
@H-K-47 I just activated MQTT and callback mode: works.
It is strange that the MQTT does not deliver all received bluetooth messages... even if I deactivate my node.
Sorry I'm new to shelly just toying around with it.
I can see the scripts in the shelly APP and edit/delete them there. But as you said they are not visible in the browser.
My Shelly Plus Bluetooth Gateway is Version 1.0.8.
Curiously - i enabled MQTT over the webinterface, and restarted the browser. Debug log didnt say anything about sending (MQTT explorer also didnt show anything neither my node red debug) - Then i went to the app and it said MQTT wasnt enabled?! I enabled it from there again and restarted and now its working.
So, it seems the fault is 100% with shelly new device.
As a final suggestion / answer - when/how does this node remove the uploaded scripts at all? does it detect when no callback is used anymore in node red and will remove it? otherwise a doc entry or warning would be good!
Thank you for your work
On every redeploy of your nodes the script is removed or added depending on the mode.
Thank you - btw since you work with shelly blu - do you know if it is possible to have each blu device as their own topic/msg in MQTT ? right now everything is overwritten because its just sent as rpc and they overwrite each other
Using a tasmota device, will correctly sent an individual topic for each device/msg.
Is it possible that the uploaded callback script disables MQTT?