Thomas Hollstegge

To chime in on my colleague @skorth, here is a minimal test case to illustrate this issue: ```ruby class FooBar include AASM aasm :funny_state end AASM::StateMachineStore.fetch(FooBar, true) # => #...

It looks like Vicare had some kind of server-side issue this afternoon, and the integration doesn't cope too well with that. I've added a (non-debug) log here, for further investigation:...

> So what are the possibilities? Remove the integration from HA for 24 hours and retry to set it up? How has everyone else tired to solve the issue? A...

Could you provide a dump of your SysAP configuration as described [in the README](https://github.com/jheling/freeathome#1-dumping-freehome-configuration)?

Hi, thanks for the detailed dump. According to the monitor output, you switched the device with serial number `6000EA57FCF0`. This corresponds to a device called `virt_licht_garage` in your config. As...

There should be another way to do this, by using the [emulated_hue](https://www.home-assistant.io/integrations/emulated_hue/) component. If you configure `emulated_hue`, Home Assistant will appear as a Philips Hue bridge for other devices on...

> as the emulated-Hue way to work between HA and F@H is currently (6 months I guess) broken Why exactly is emulated_hue broken? It works fine for me.

Thanks for your detailed report. Could you try my code from PR #136? The sensor should be exposed as a binary sensor, with an extra attribute `window_position` that should read...

@colinwilke @n3m3sis1983 Could you try to setup the integration manually, i.e. click "Add integration" in the bottom right corner, search for free@home, and enter the details there. I suspect that...

> If I enter a non-existing username it says user not found so it must be somehow connecting. However there is no message when entering a wrong password. Yeah, the...