- Posted on
Fri Oct 06, 2023 5:30 pm
-
GlennNZ
offline
-
- Posts: 1578
- Joined: Dec 07, 2014
- Location: Central Coast, Australia
Hi
The error message seems to describe it well - surprisingly for an exception message - Office fan doesn’t respond to any of the usual Indigo commands as it is not an Indigo device. It (presumably) is a plugin custom device for the SenseMe plugin. As we discussed without it being an Indigo device support will vary depending on how the plugin behaves. It this case it seems even a Homekit switch (On/off) device will fail as it appears it doesn’t support those commands.
This comes back to the core issue at hand here which is you are trying to add Plugin custom device (not standard Indigo devices) to homekit, having used a Plugin to get them into Indigo in the first instance.
This Custom/External Device —> Indigo Plugin —> into Indigo and then use HKLS to publish this device out of Indigo into Homekit. And then Homekit then reverses this process. This is convoluted and not ideal or a focus of HKLS.
Add a masquerade device (if possible - but the same problem exists for masquerade plugin) or a Virtual Device with action groups giving on/off. Add as switch device and within the Home app can change it to a Fan icon/type I believe.
Alternatively would be to add a HomeKit Senseme plugin to your other homekit/HomeBridge install via a plugin (a quick google suggests that might not exist though, which probably highlights how fringe this case is.)
Supporting plugin custom devices fully was never on the cards, nor would it be possible, and the impact of all this back and forth problematic to say the least. Particularly in the current scenario where Apples HomeKit just stops responding without error messaging if unhappy about anything within the bridge.
And if the reply to that is - Homekit Bridge supported/did this that.
Well -
1. That is all well and good, and well done C4W!
2. I would comment that it only supported plugin devices that it was interested in/or had, and was no means all
3. And given was trying to take the convoluted pathway as above, with changing plugin’s was trying to support a house of cards with any plugin change potentially being breaking, and breaking Homekit silently and for all devices.
4. HKLS supports every sensor device (Temperature, True/False etc) as every HomeKit sensor device. And most Indigo devices as any HomeKit device. This x! type factorial end result means hundreds of possible devices/combinations. This means a whole host of temperature sensors, pool temp sensors, occupancy sensors, motion sensors, even weather websites (via GhostXML) are all customisable and publishable in Homekit versus older solution which had limited support. Either not being able to get it in at all, or one homekit device type only.
Hopefully the solution in the SenseMe thread is an updated plugin with seperate Indigo devices for the Lights/Fans which will resolve this issue for you, or a virtual device meanwhile. The combined device grouping now possible would seem a good way for this plugin to go, and did check out the fan website as have a fan I could upgrade….
Glenn
Sent from my iPad using Tapatalk
Last edited by
GlennNZ on Sat Oct 07, 2023 1:05 am, edited 1 time in total.