You probably have stand-alone wifi-devices? I did not have those when I started on the library. @jarnsen has provided me access to one, so I can add it soon. Maybe next week, but I’m also working on other things.
The camera is a separate thing, the x-sense api retrieves some access keys and then a different API is used. It will probably take longer to implement that, but it should be possible. I think that a separate library for the camera would make sense. Maybe such a library already exists.
Thanks for all your work on this. I have three of the stand alone smoke detectors which sound like are not working yet. However, this is the message I get from the integration if that helps.
yes, but I’m curious about which devices are currently in use that are not supported. In other words: for which devices is support needed that we do not support yet.
Thanks Theo for your quick reply, in fact i have both the smoke detectors (XS01-M) via the base station (SBS50) and standalone (S01-WX), furthemore i have the CO-detector (XC01-R). I receive the same error message as @komtx . The “coroutine message bug”.
I also did understand the cam integration (i use the SSC0A) is another story Thanks for all your efforts !
1.: who has another device running with the integration 2.: who has another device that doesn‘t work with the integration and needs support fort it 3.: best way for testing is to share the device via the X-Sense app
In my case, the base station is located fairly centrally in the kitchen, but I can reach all smoke detectors in the 120 m² house, including those in the garage, with full reception
I’ve got the XS01-WX working now, the code needs some cleanups, but I will push it soon. Hopefully it will also support the other stand-alone devices, but wasn’t able to test that yet.
Also moved the serial-number to device info. I think it belongs there, because it will never change.
Just updated the xsense-lib and the component. It should now support the stand alone smoke detector XS01-WX. If we are lucky, the SC07-WX works as well, but I have not been able to test it yet.
If fields have a slightly other name (the API is not very consistent), some data will be missing from the untested devices.