Open TheGrumpyBadger opened 11 months ago
I guess that would be possible, but just iterating over multiple ahoy or opendtus
I guess that would be possible, but just iterating over multiple ahoy or opendtus
Hi, I would appriciate this too. There is an additional reason. Hoyemiles HMS Inverter need another RF Module instead of the NRF24L01+ for the HM series it uses CMT2300A for the new one. I have the "old" RF module running for my two HM Inverter and a device with CMT2300A for one HMS Inverter. I don't necessarely want to combine them because I can place the new one closer to the actual inverter.
Is this already possible or how do I itarate across two instances?
I keep this in mind when it comes to refactoring the base. For now, you can simply copy opendtu to opendtu2 and start it. So you will have 2 instances of it. This is how it runs in my installation.
I keep this in mind when it comes to refactoring the base. For now, you can simply copy opendtu to opendtu2 and start it. So you will have 2 instances of it. This is how it runs in my installation.
so you mean the folder /data/dbus-opendtu to /data/dbus-opendtu2 right? ... and make sure the DeviceInstance ID's do not get in conflict with to original config.. after that start the service for the second folder .. right?
Yes, that's right. It works very well. Give it a try. I've got ahoyDTU and openDTU running this way. Different folders, of course, and different instance IDs.
I would be nice to have the ability to add multiple openDTU at once.
Usecases: