I am currently running hassio on resinos on a rpi 3b and have a rpi 3b+ has anyone moved to this newer pi and noticed any performance increases with it running hassos?
on a 3b (not 3b+) I find ResinOS was much faster than HassOS. YMMV
(and before anyone asks, that is with both 32bit and 64bit versions of HassOS) Once it’s up and running it seems just the same though (although restarts are also slower)
having a regular pi3b with hassio and pi3b+ with hassos, i’m slowly rebuilding the setup on the new system. Experiencing the new setup to be much smoother and having far few errors than the hassio setup, running side by side.
Possible cause could be the fact that the mosquito broker is setup on the regular pi3b/hassio system, and that’s causing a lot of processor activity , hence resulting in timing errors on that setup. Not sure. Just what I am seeing.
Must admit the new system isn’t fully loaded yet, but all in all, it seems an improvement id surely recommend testing in your setup.
Cheers,
Marius
Thanks for the reply,
I have decided to run 3 pi’s leave my existing one with all sensors, runa dedicated hassio with my addons for mqtt, grafana etc and run my essentials packages for automations on the new hassos 3b+. I am going to use the MQTT Eventstream to keep the states upto date with the automations server.
My CPU runs at over 35% consistantly so making the move is to make my automations snappy once again.
Interesting but as you say not really comparable until both have the same setup. Processor use will vary as well…
In any case, HassOS is the future and there won’t be ResinOS updates so you really need to update sooner or later.
How did you configure the sensor for processor use? What is Verbonden? (Is it Dutch or German?)
cool, the exact thing Id like to do. If your ready for it, please share how you synchronize between the 2, and have mqtt setup, since I am a bit in limbo about that…
for example, have a set of mode switches/settings on the first system Id like to read off of that into the second system, instead of having to copy the exact logic and switches on the second system.
Dutch 
meaning Connected, on or online …
- platform: systemmonitor
resources:
- type: disk_use
arg: /
- type: memory_use_percent
- type: processor_use
- type: last_boot
- platform: command_line
name: CPU Temperature
command: "cat /sys/class/thermal/thermal_zone0/temp"
unit_of_measurement: "°C"
value_template: '{{ (value | multiply(0.001)) | round(1) }}'
- platform: filesize
file_paths:
- /config/home-assistant_v2.db
1 Like
thanks… I had the CPU temp one.
You only need to send one way, I have it semi setup already will post all of my code and readme on my repo once complete. The family are heading on holiday and I’m coming back 2 weeks earlier so I can take care of the renovations which is the perfect time to take the system offline.
same temp sensor here.
Ive already discussed this elsewhere on this forum, the latest heatwave we’ve been experiencing caused my attic to be rather warm, up to 40 celsius. The Pi3 became so hot, almost up to 83 degrees, it became unresponsive and faulty.
Bought the cooling fins, which did relieve some 10 degrees or so, , but finally decided ti take it out of the attic, which seems to have solved the heating issue.
Never would have thought that environmental temperature could be of such influence on a system… A Pi must not be the most fail safe of systems around…
lol my Pi constantly gives me heat warnings of over 85 degrees and it is only winter here summer is going to kill it might have to move it out of the comms rack.
1 Like
most remarkable system difference though is this:
Hassio/Pi3B
Hassos/Pi3B+
the Hassio system has never shown any swap use at all…
what would be the main difference between eventstream and statestream for this use case?
My hope was to setup statestream on the Pi1 and then read those states on the pi2, but since you write about eventstream, im confused again…
I’d be interested more when they are configured the same… my perception is that ResinOS was a lot faster… to the point where I was sure the HassOS setup had crashed and I almost flashed again… it’s also way slower when I restart the HA server…
That’s mine… (HassOS)
My understanding is statestream is what you want if you have unique entity names across the 2 instances of HA if you can’t ensure that you have that then eventstream is what you’re looking for.
@Mariusthvdb I have completed the transition to 3 separate Raspberry Pis 2 x 3b+ running hassos and my original 3b running resinos. I was using statestream and moved autations to the new pi however the resources from original were still causing lag. So I decided to move 90% over to node red and all of my automations are now snappy and I have saved on resources across the board.
1 Like
wow, that s mighty impressive!
makes me think though… since you’re using 3 pi’s and then some, why not use 1 more capable machine and be done with it. Thinking of one of these intel NUC’s or the likes. Might be cheaper and more robust, no? Not sure yet.
Had several (independent, non HA related) hardware issues the last few months that made me reconsider the Pi as a life supporting device… let alone the documented flash card deficiencies.
It sure is cool for experimenting and educational purposes, but maybe not so for commercial alarm- and life-guarding installations.
Any ways, since i have 2 in place now, I will certainly see how to setup the P1 as a server, and P2 as a machine reading the states and act/automate with that.