Open FraatTailscale opened 11 months ago
as far as I understand this from the README, this is one single API to connect to all CCU devices, instead of e.g. 5 RPC connections for different device types. This would then be better an adapter request for a adapter, because hm-rpc of course is focused on RPC only and the concept also does not fit in this adapter.
as I have understood CCU-Jack is creating Homematic devices like CUxD is doing this, just with another interface category.
@FraatTailscale Yes but also cuxd is offiéring all details on a special port but reuses the official protocols that hometaic uses too. But CCU-jack is a bridge to bring in devices buzt in fact control them via REST or MQTT ... so the goal is better to connect to these interfaces directly.
For the case where CCU-Jack "adds virtual devices into CCU" they come from other sources via CCU-jack ... honestly, also connect to these devices directly.
yes, this would be indeed of great help to get the states directly into ioBroker. This add-on is getting more and more popular in the HM world.
Currently it's at least possible to use @ptweety/node-red--contibute-ccu to read/write CCU-Jack states. This, however require usage of user variables.
Is your feature request related to a problem? Please describe. I cannot see virtual CCU-Jack devices in RPC-Virtual devices. https://github.com/mdzio/ccu-jack
Describe the solution you'd like I would like to be able to see CCU-Jack devices in RPC-Virtual devices
Describe alternatives you've considered Don't found a alternative