cbrherms
cbrherms
@bitglue that's related to [home assistant cloud](https://home-assistant.io/components/cloud/). The paid for feature that's currently in beta and at the moment only available for testing by people who use American Amazon accounts....
Thankyou for opening my eyes! The term look before you leap springs to mind. Actually hadn't looked in to HA's implementation of cloud yet. Deeming it irrelevant for the time...
Do you think HA will merge a PR that bypasses their paid for method though?
@Reidar6 If it's a fresh setup it may be due to payload version. Haaska uses V2 and AWS is now v3 by default. There's a way to change it to...
No problem. I was unsure whether to report it as bug or feature so thanks for clarifying.
I would like to third this, for the same reason as @mtabo - press to trigger an on action and hold for a few seconds to trigger an off action.
> you guys could use the toggle command instead. Using a system action with the following command. > > ``` > /home/pi/oprint/bin/octoprint plugins psucontrol:toggle > ``` Yeah, that is what...
I have run in to the same issue also with 3 separate machines of various models on v1.2.2 with HA 2024.4.3. Appears all entities are associated with the final server...
> Alright lads, I managed to reproduce it through mocking and fixed the issue in v1.2.3. > > Please report back. :) Yup, can confirm creating separate devices now. Did...
Just to add, i've noticed as well that if a device *becomes* unreachable at some point, the particular device errors and then no longer updates.