More complete testing thoughts ...

[Apollon77]

Hey Sebastian,

I have checked a bit. "Complete" testing for CUL-Net is kind of easy. Setup Net-Server and communication can be handled from both sides.

For serial it is more interesting:
One option is to use the Mock-Features from Serialport ... but as I tested for this we need access to the serialport instance of the cul instance ... because of strict mode and such it is not accessible directly, it would be needed to add some kind of "getSerialport" method ... for testing only ... not great :-(
But only alternative I found would be some kind of virtual serialports using socat or something like this. But this would be needed to be installed and started anytime tests are executed. Not very comfortable

What do you think about the options ?! ;-)

[hobbyquaker]

To be honest - CUL doesn't play a big role in my smarthome anymore. Only 3 temp/humid sensors, a EM for gas and a doorbell sensor are left atm. This is working "rock stable" for years now, so I don't have that much motivation to put much time into the cul module ;)
If you have motivation and time - do it like you think it's best, I will not stand in your way as long as we try our best to keep the module stable and backwards compatible :)

[Apollon77]

I personally still have the CUL stick on my CCU with cuxd :-) Other prios till now than change this "running system" :-)
I will postpone the topic for now I think because other things are more important. You could leave this issue open, so we can continue later if needed. There were requests in ioBroker community to maybe add missing stuff ... but don't looked deep into it till now.