New images, based on HassOS


I got mine defined with:

# RFXcom 433 transceiver
  device: /dev/ttyUSB0


There is no such device in my /dev, I even did a reboot:

core-ssh:/dev# ls -l
total 419
lrwxrwxrwx    1 root     root            13 Jul 22 23:21 fd -> /proc/self/fd
crw-rw-rw-    1 root     root        1,   7 Jul 22 23:21 full
-rwxr-xr-x    1 root     root        428228 Jul 16 00:23 init
drwxrwxrwt    2 root     root            40 Jul 22 23:21 mqueue
crw-rw-rw-    1 root     root        1,   3 Jul 22 23:21 null
lrwxrwxrwx    1 root     root             8 Jul 22 23:21 ptmx -> pts/ptmx
drwxr-xr-x    2 root     root             0 Jul 22 23:21 pts
crw-rw-rw-    1 root     root        1,   8 Jul 22 23:21 random
drwxrwxrwt    2 root     root            40 Jul 22 23:21 shm
lrwxrwxrwx    1 root     root            15 Jul 22 23:21 stderr -> /proc/self/fd/2
lrwxrwxrwx    1 root     root            15 Jul 22 23:21 stdin -> /proc/self/fd/0
lrwxrwxrwx    1 root     root            15 Jul 22 23:21 stdout -> /proc/self/fd/1
crw-rw-rw-    1 root     root        5,   0 Jul 22 23:21 tty
crw-rw-rw-    1 root     root        1,   9 Jul 22 23:21 urandom
crw-rw-rw-    1 root     root        1,   5 Jul 22 23:21 zero

There is a reference in /proc, not sure if that one can be used:

core-ssh:/dev# ls -l /proc/tty/driver
total 0
-r--r--r--    1 root     root             0 Jul 23 15:06 ttyAMA
-r--r--r--    1 root     root             0 Jul 23 15:06 usbserial


Hows gpio errors? Any one have solution to use rpi rf addon???

Thank You


I’ve been running Hassio on RP3B. Currently on 0.74.2
Series of questions:
1- Do I gain anything from formatting and installing the new image with etcher?
2- In that case would I restore the full backup or everything but the HA checkbox?
3- 32 bits or 64 bits?


If you’re still on ResinOS I would update (I did update). There won’t be any more host resinos updates.
32 or 64… I went 64 and have seen no issues but the recommendation (unexplained) is 32bit.
Make a full snapshot and then restore it. It was pretty painless. You may need to delete the database after you restore the snapshot if you get lots of errors in the log. Also if you go 64 you will definitely need to delete database… my history had flatlined until I did that.


64 bit is still being developed. So there is an explanation.


So is the 32bit. Unless you are one of the devs that’s just your speculation, not an explanation.


Well that is the explanation I have seen given.

Yes everything is in development, or we’d be using win 3.1 and linux 1.0.


I’ve heard there are issues with the 64bit version in discord but that’s just hearsay as well. As I said I’m using the 64bit with no issues - haven’t seen any reported either. There’s nothing I have seen anywhere that is an explanation for a recommendation. Maybe there are issues with some components but I have no idea.


SD card access is slower than 32 bit, there are conflicts with some addons, and there’s no real point to running the 64 bit as none of the boards have +4GB of ram to take advantage of. So there would seem to be no advantage to running the 64 bit. It isn’t some “rumor”.


Well this is the first real explanation I’ve seen so thanks. Makes you wonder why they made one for a RPi at all. Do we know which addons conflict?


My thoughts too, perhaps it falls into the same category as the front end automations UI :slight_smile:


Has anybody managed to get the hassos images to boot from usb yet? I.e. not require an SD?


Work in progress. This is how software is developed.


I’m aware of how software is developed. I was referring to the Pi not having the memory to take advantage of 64bit and seemed seemingly offering no advantage.


I have seen reports of 10-15% performance boost from 64 bit pi kernel+userland.

But I have also seen people claim that there is very little difference, or even a penalty.

I’m all for squeezing what we can from the pi, but then again I don’t have to support yet another platform.


Is it true the current version is slower to load?


It is for me.


Doing some hunting around on info for 64bit distros on the PI it appears to come down to optimization.

The 64 bit builds can be MUCH faster for crypto libraries but many standard libraries that have been fine tuned and optimized are still faster on 32bit.

The main drawback regardless of optimization is cache and memory… 64bit code seems to use about 1.5x more memory than 32bit code and since the PIs have a fixed amount and it isn’t a lot it could be the one thing that won’t improve.

A lot of benchmarks I found for like for like tests didn’t show huge differences in ether direction on average.


Hey talondnb, can you tell me where you got the resin img from please?