MQTT cloud (cloud.shiftr.io) does not work

Tags: #<Tag:0x00007f70354cb128>
#1

Hello! cables.gl’s recommended MQTT platform, shiftr.io, has been upgraded → https://next.shiftr.io/
The original broker.shiftr.io still works with the MQTT nodes, however the MQTT nodes throw an error when the information needed for the upgraded cloud.shiftr.io are plugged into the node.

It would be great to be able to connect a cables.gl designed website, with the new cloud shiftr! Please see https://next.shiftr.io/cloud

An easy way to reproduce the bug, is to replace “broker.shiftr.io” in a copy of the MQTT example (https://cables.gl/p/_IZUSv → Broker URL inlet), with “cloud.shiftr.io” (as would be required), then the patch crashes. It also does not save/reload.

Hopefully it will be possible to have cables.gl working well with both broker.shiftr.io (original), along with the newer, faster cloud.shiftr.io!

#2

hey,

i tested this by cloning the example patch and then following this:

https://next.shiftr.io/try

works fine for me, what am i not getting? any screenshots of the errors?

here is my patch:

best,
stephan

#3

Really glad you got it working! Still weird for me though.

recording
recording1108×960 831 KB

Above is a gif of what happens on my end, looks like some weird behavior and it happens every time. You see me trying to change the Broker URL (by adding a ‘s’), then it appears as NaN. I try to change it back to public.cloud.shiftr.io, and it remains as NaN. If I save the patch, I’m not able to load it and receive this error upon editing:

image

But since you were able to get it working, what steps did you take for it to work? As mentioned, the above behavior happens consistently for me. Weird, but I’m glad that it’s ultimately possible.

#4

hmm, i saw this as well, will put working on mqqt ops onto the backlog of cables. changing and saving every field one by one did the trick for me, eventually.

#5

we just did a quick update with some fixes to the mqtt ops. try deleting your mqtt ops and get the new version that should work better.

#6

Aye, it works great! Thanks.