UI Update

I’ve been busily beavering away at a commercial project for the last couple of weeks but that ends at the weekend and I hope to soon have some more reviews of new and interesting products for you including some surprisingly cheap SBCs.  Meanwhile, close to the heart of many of use – the IOT user interface remains a challenge. There are several of course – the dashboards are great unless you want to control something – and you will know that in this blog I’ve discussed the Node-Red UI and Blynk to name but two.

I dismissed Blynk because the interface though beautiful was simply too buggy – or rather a combination of that and the Node-Red interface. Well, the good news is that part of that problem is solved. TZAPUs new web sockets code seems to be rock-solid. The only bit of the puzzle that needs fixing is the actual Blynk App. For reasons beyond me no-one seems to have noticed that if you PAUSE the APP and then continue, it knows nothing of any changes that happened while it was paused. Come out of it and go back in and fine – it picks the info up from the server – but simply pausing is an issue – maybe no-one thought that something other than the APP might be controlling your IOT – yes, hard to believe. However this morning I got acknowledgement that this will be fixed on the next sub-release – which means that by the look of it we have a fully working interface.

Meanwhile node-red-contrib-UI is due a facelift and Andrei has been working on that – sadly despite spending ages on this I’ve been unable to get the new upgrade to work – I’m confident however that this will be resolved.. and then we will have at least two decent, easy to use interfaces between Node-Red  (and hence most if not all IOT) and our phones.

Time will tell. This weekend we’re off to visit friends, next week I’m putting my office together and hopefully collecting some PCBs to control Nextion displays and as soon as my new office is in a state to do some R&D, expect to see new reviews and more info.


6 thoughts on “UI Update

  1. Pete,

    I’m curious what you are doing to expose your RPi driven UI to the internet when you want to access the interface from outside of your local network?

    Are you opening a port in your router and redirecting it to your Pi? And if so, do you have a static IP for your router or are you having to use some dynamic DNS type service?



  2. Hi Pete. I follow this blog everyday and thanks for share your work. I’m searching a easy and beautiful UI for my esp8266 mqtt board and I have the same problem. I try Openhab, domoticz, evothings, thingstud.io, freeboard.io, …….. Finaly blynk or node-red-contrib-iu can will be my choice, but the world of IOT needs a really usefull and easy UI framework.
    Jaume Nogues
    RPrim tech scholl Barcelona

    1. Yes it does – just about to test the Blynk server update to see if it will now allow change to states while thw APP is paused to be represented by the App when it is then restarted. More later.

      1. Sadly the latest update to the BLYNK server did not work – I’m convinced the issue is with the APP itself. Stop the APP with the square button on top right of screen – change the state of a pin externally, resume the APP with the triangle button – and it has NO idea that the pin status has changed… but if you STOP the App completely – change the state of V1 and then log in – it knows the correct state. Clearly the server is aware of the change – but the App on resume is not going of to the server to check..

    2. Problem is – everyone has their own view. For me – I do NOT want to rely on someone elses server – neither for the UI or for controlling things. I’d rather have the whole lot controlled on my own – preferably a little Raspberry Pi. Getting there.

Comments are closed.