• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. robinr1
    3. Posts
    R
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 4
    • Best 0
    • Controversial 0
    • Groups 0

    Posts made by robinr1

    • RE: Evok & NodeRed backup/restore

      I performed an update today to the newest nodered OS image.
      I took a OS backup using the service mode, to be safe
      I took a file copy backup of /home/unipi and /etc
      I flashed the new image
      boot into the new image
      set timezone

      $ sudo timedatectl set-timezone Europe/Brussels
      

      installed latest updates

      $ sudo apt-get update
      $ sudo apt-get upgrade
      

      updated unipi firmware:

      $ sudo /opt/unipi/tools/fwspi -u 1 -v -P -U
      

      Stopped node-red

      $ sudo systemctl stop node-red
      

      moved /home/unipi/.node-red to /home/unipi/.node-red.old
      copied /home/unipi/.node-red and /home/unipi/node_modules from the file-backup to the current system
      rebooted unipi

      Node-red came up with correct config. Inside Node-red I had to update the @unipitechnology/node-red-contrib-unipi-evok node-palette to v0.0.8 and then had to replace all unipi-evok inputs and outputs by their respective unipi-evok-v3 counterparts.
      After that everything seems to be up and running again. (apart from my 1Wire temp sensor which seems no longer be detected by Evok.. but that is out of scope here, I assume)

      Possibly you may have to configure more and or re-apply changes you did on previous OS image. (I had to also install and configure mosquitto mqtt for example.)

      posted in Official API - Evok
      R
      robinr1
    • RE: Message was not properly evaulated on every DI

      Seems that this was a newbee error. I had the example flow still active in the project, and used a second instance of the websocket in my own flow. But seemingly, those instances conflict with each other causing only parts of message to arrive.
      If I have only one instance of the listening websocket in the project, everything seems to work smoothly.

      The firmware upgrade problem, however, remains. I have fw 5.58, the OS has upgraded the firmware package to 5.60 but I can't upgrade the actual firmware as the fwspi --auto command doesn't start the upgrade.

      posted in Node-RED
      R
      robinr1
    • Message was not properly evaulated on every DI

      I finally bought myself a Unipi (Patron S207) and since I don't have any Windows machine, Mervis was not an option. So I installed the Node-Red image 20220427.0
      Up until now, everything went smooth.
      As I'm completely new to both Node-Red and Unipi, I added a ws node connected to a DI node and then attached a debug node to it to check what the DI node exactly would return when triggered.
      When I now trigger the DI, I get the message

      7/5/2022 01:17:44 node: DI 1.1
      msg : string[34]
      "Message was not properly evaulated"
      

      and nothing else.
      In Linux syslog, I see this message also appearing.

      May 06 23:29:45 S207-sn320 Node-RED[373]: 6 May 23:29:45 - [warn] [unipi-input:DI 1.1] Message was not properly evaulated
      

      What is wrong here ? It looks to me that the websocket sends a message to the DI node that the DI node does not understand? Or the message json is invalid ?

      I did update @unipitechnology/node-red-contrib-unipi-evok from v 0.0.2 to 0.0.4
      And also did apt-get upgrade on linux which upgraded unipi-firmware from 5.58 to 5.60 and displayed a warning that I should upgrade the firmware using the command sudo /opt/unipi/tools/fwspi --auto .
      If I do that however, it doesn't do anything:

      # sudo /opt/unipi/tools/fwspi --auto
      Board on /dev/unipispi firmware=5.58  hardware=1.1 (E-8Di8Ro) (spi 6MHz)
      

      and nothing more.

      What can I do to fix this Node-Red problem? And why is the firmware not updated with that command ? (could the Node-Red problem be fixed with the new firmware ?)

      posted in Node-RED
      R
      robinr1
    • Replacing custom PLC based home automation with Unipi Neuron?

      I currently have a own-made PLC based home automation system using a Siemens PLC S7-200, a Siemens SITOP 10 24Vdc/10A Power supply and a bunch of Siemens Sirius Contactor relays, 4 NO 24V . But due to the closed nature of Siemens PLC's, the current absence of network connectivity and limited interoperability possibilities without resorting to expensive commercial/industrial closed products. And also the fact that this PLC seems to be discontinued and I'm planning to do some home renovation soon and will be needing more I/O than I currently have available, but won't be easily find extra extensions for it.. I am looking for an open alternative to replace this PLC with.

      I was first looking at railduino as a possible replacement, but then bumped on Unipi Neuron. I don't find much english info beside the extensive info on the Unipi website itself. But from what I've read there, Unipi Neuron looks to be an ideal replacement, as it looks to be pretty robust and has integrated direct switching for basic functionality as a safety.

      So I am strongly considering buying a Unipi Neuron.
      Currently I have 40 inputs and 35 outputs. So a Unipi Neuron L203 in combination with a Unipi Extension xS11 should be able to do the job ?
      And I can re-use my current 24v power supply to both power the Unipi, the extension, the input signals, a few motion detectors and a LED strip ?
      And as I understand correctly I can even bypass the current contactor relays by switching the 230Vdc current (with 16A circuit breakers) of the lights/shutter motors/etc directly with the relay outputs ?
      I would also like to add remote control using smartphone, IFTTT, etc.. So was looking to openHAB and/or Node-Red.. Any recommendations on that?

      posted in Neuron Series
      R
      robinr1