For the people who encounter the same problem or just stumble on this post by coincidence:

UniPi tech wrote: “We know the firmware update, especially of the extensions, is a sort of Achilles heel and we are thinking about some concept of dual firmware to which you can revert to if the flashing of the new firmware fails.”

I also would like to mention the excellent support from UniPi! I’ve received a very fast and meaningful response from both the technical as commercial team, and they are moving heaven and earth to provide me the fastest possible solution.

I didn’t experience such a personal approach from an international company since a long time.

Just wanted to say the same, after reading your e-mail :-)

pro-side : Really fast answer from unipi; I like this kind of good customer service !

Down-side I am wondering (and also replied on the e-mail):

• Isn't there any error-checking on the firmware upgrades ? is this technically possible ? Or a fall-back switch to revert to previous firmware ?
• Sending the unit in snail mail and waiting for repair is a lengthy process, especially when half of the house is in the dark and there is no other option to switch the lights. Maybe temporary replacement parts could be handy ? Maybe from local resellers ?

Hi there,

I just upgraded my M203 (fwspi) without any problems, but xS10 won't come up after upgrade with fwserial.
I received some Flashing errors on the cli during the upgrade (timeout & invalid data), and after that the unit was unresponsive.
Since I did this form work, I restarted the unit when I came home (after more than one hour). Before I had 4 LEDs lit up permanently: PWR (red), RUN, RX and TX.
After reboot only PWR is lit permanently (red).

Does this mean my unit is toast ? Can this be fixed in a timely manner ? Half of our house is now without lights...

Thanks for any advise.

Steven

Follow-up on this one:

• Bullet 1 and 2 are still a problem. Unipi people, can you please comment on this ?
• Bullet 3: When changing a relay state I get an array back with all relay states of that group. This was a problem because I wanted to propagate the state change to MQTT. I solved this by looping over the array and returning every state. Although this creates a little overhead, MQTT is fast enough to handle.

Hi Martin,

A late thank you for your answer !
I found 2 different solutions for my problem, the second being the best:

1. Running Home Assistant on the Unipi, creating 2 new Modbus drivers (only one is provided out of the box and not sufficient to both access the local TCP-Modbus and the RTU Modbus of the extension.
   Sadly this was not very stable and too slow to detect push-buttons

2. I created a layer between EVOK Websockets and MQTT, which is a lot faster than when HA did the polling. You can find the project at https://github.com/StevenBrs/evok2mqtt. (first baby steps in Python, needs some improvements!)
   It probably is fairly similar to the one from Martijn you linked in your previous answer, only that my thing is running on Python, so does not need a lot more libraries than already available in the EVOK RPi image.

I think it would be nice if Unipi had some more attention for Home Assistant, since it's a wide-spread and popular platform.

I'm still a beginner with both Neuron and HA (and Python), but if I can be of any assistance I'd be glad to help you out !

Oops, the "Exc SB : full"... error message should be "Exc : full"...
I added my initials to the code to make sure I was looking in the right place :-)

Hi there,

I'm trying to do some evok websocket stuff in Python, but encounter some problems:

• I can change states with "set", but when I change the function to "full" I get the error:
  evok - ERROR - Exc SB : full() takes exactly 1 argument (2 given)
• If I'm toggling UserLEDs within EVOK webUI, I see the changes appear in the websockets for 1_01 to 1_04, but for my extension (xS10) only the first led appears in websockets. The other leds don't show up, although they light up correctly.
• When I'm listening to the websockets and toggle a relay in the evok webUI, I get an array with all relays instead of the one toggled. The one toggled is neither the last one or first one, so very difficult to get the changed one

Can somebody please tell me what I'm doing wrong, or how I can work around these issues ?

P.S. Using a M205 + xS10, with default Evok rpi image from unipi website (and added some stuff like docker)
P.P.S. I'm not a programmer, but I know my way around in PHP and Delphi. Python is new for me though…

Thanks !
Steven

Re: Unipi neuron home assistant setup

Hi all

I succeeded in controlling my M205 unit with home assistant following the topic above, but I also have to address an extension module xS10.
Am I right that the extension is also available through the modbus on localhost port 502 ?
How can I address those other inputs/outputs ?

Or do I have to find a way to add a second modbus definition ?

Another thing: My first test seems that reading the inputs is not so fast, and I'm afraid that a toggle switch will not be detected by Home Assistant. Maybe I have to work with websockets ? Any idea how I can do that with HA+EVOK ?

Our house is almost rebuilt; we have to move in in less than 2 weeks, and the lights aren't working yet !! :-). So it is quite an issue for me at the moment...

Thanks for your answers!
Steven

Hi there,

I ordered a M203+xS10 some months ago, and I'm finally ready to start using them in my rebuilt house.
Testing with the EVOK image and measuring the devices, I notice a permanent 1-2 volts between the DOGND and DO1.1 - 1.4. Enabled the voltage drops to 0,599 V.
I expected measuring 0V when they are inactive, and something between 10-24Volts when they are active.

Am I wrong ? Did I misunderstood the DO's ? Or do I possibly have a faulty unit ? Or could it be a software problem ? (Running UniPian-Neuron-OS-2018-03-09)

Thanks for your answers!!