Migrating from Intel NUC to Odroid C2

Share your Projects!
1

Hey there,

I did this today and wanted to document how it went. I was seeing around 10~11% CPU use on the NUC and everything was working just fine apart from one issue; power outages. HA would fail to come back up and it seems that if the HA instance comes back up before the network is ready, the whole thing locks up.

Anyhoo, rather than try and debug, I had the Odroid C2 lying around and I wanted to try out Hassos so off I went.

I first tried a backup of the Intel NUC and a restore but this did not work. Samba failed (possibly due to a ETH port reference being different) and the frontend would not start. Luckily SSH was working so I ran hassio ha check but that came back OK. Out with the eMMC card and reflash and start again. Installed SSH and SMB manually.

This time I copied across the config files only with Home Assistant stopped. Restarted, all good except that all of my Xaiomi devices had defaulted to their factory names. Now I suspect this is because discovery is on by default and all of my Xaiomi devices had already been discovered before I copied across the files from the NUC. This seems to screw with the entity ID registry.

WORD OF WARNING. If you are doing this, TURN OFF Discovery first. Maybe that will help? The problem with the Xaiomi devices is there is no way to identify which device is which once they are installed. I have six smoke detectors, one single button, one double switch, four mains switches, two door/window sensors, four temp/humidity sensors and two motion sensors…heee! All of these had to have their entity ID’s manually updated again! Luckily, I had kept a registry in one of my yaml files that recorded the factory ID so two hours later, all back again.

A couple of other devices lost their custom configuration; my Yale deadbolt and two of my Z-wave switches.

Ah, what the heck. My config needed a tidy up anyway!

All running on the Odroid now and the CPU is sitting at 10% I’ve left the NUC intact and will spark that up again when Hassos becomes available for that platform or the Odroid poos itself. FYI, the card I used in the C2 was a 32Gb eMMC.

Thought this might help others giving this a go. Feedback welcome.

2

Thanks for the info, I’m currently rebuilding after another Samsung SD card bites the dust. I was thinking it was time for a NUC or VM but the power outages would be an issue, Odroid with eMMC is looking good.

3

Never seen an issue with the NUC

4

I invested in this UPS to be sure. There is a 3d print for it. It was in action first time last week. Flawless but costly
http://www.mini-box.com/OpenUPS2?sc=8&category=981

5

Unless he changed at some point, he was using resinos based hassio image.

6

Correct. Resin prior.

7

All is not well in the Odroid C2 camp. Can anyone who is using this platform confirm the following?

For any of your notifiers, does your message get sent if you program a file located in /local such as the following? I’ve got to use the web server as Synology doesn’t support local files any other way. It was working fine on my Intel NUC but won’t send on the Odroid. If I spin up a webserver on my NAS and use that as a file location, the message sends (current workaround).

  - service: notify.hass_synochat
    data:
      message: "Pool Gate was opened"
      data:
        file_url: http://10.0.1.200:8123/local/pool_gate.jpg

Secondly, does anyone have cURL configured in a Shell Command? I have several and none of them work but I’ve confirmed the exact command works in cURL for Windows. I’m sending the command below to pan/tilt a Dahua PTZ (preset 1) but when I call the service in the dev panel, nothing happens.

preset_1_park: curl --digest -u “admin:password” “http://10.0.1.13/cgi-bin/ptz.cgi?action=start&channel=0&code=GotoPreset&arg1=0&arg2=1&arg3=0

Any feedback welcomed if you’re also using a C2.

P.S Version is currently 0.83.3