Modbus is a data communications protocol originally published by Modicon (now Schneider Electric) in 1979 for use with its programmable logic controllers
Since Modbus was designed in the late 1970s to communicate to programmable logic controllers, the number of data types is limited to those understood by PLCs at the time. Large binary objects are not supported.
Thanks for your suggestions, I have created a package[1] that breaks down all values. Unfortunately I need an additional variable (_raw values) for some values. I haven’t found a way to automatically hide these values. Suggestions and PRs are welcome.
This is such amazing work. Thank you for that! That package feels almost like a full integration and it’s definitely worthy of one. It feels like there only those 10% left to do to make it a full integration now.
Is there anyone feeling able to give it a shot or lay down the ground work so all of us can jump in and integrate all the functionality?
Is it possible to change prmBypassTmax by modbus? I’d like to change temperature between summer and winter.
Or is it possible to disable bypass by modbus?
Then I could stop the bypass in winter, when heating is enabled.
Pluggit has released a new firmware late september, version 3.14
To install it, the also new V3 of Pluggit iFlow must also be installed on your computer, and previous iFlow versions MUST be uninstalled prior to upgrading the firmware.
A new Modbus documentation has also been released. Everything can be downloaded after registering an account on https://inside.pluggit.com
To find the updated Modbus documentation, go to Pluggit Inside and search for “Modbus”.
The changes since V2.68 are:
the following parameters have now write access:
prmDHCPEN
prmCurrentIPAddress
prmCurrentIPMask
prmCurrentIPGateway
prmBypassTmin
prmBypassTmax
prmRamIdxBypassManualTimeout
prmRomIdxRhSetPoint
In the filter surveillance section, Servoflow has been added.
Alarm list updated.
Following parameters added:
prmBypassTmaxSummer
prmBypassTminSummer
prmRHSetpointSummer
The most interesting changes for me are that we can now modify the manual timeout duration and the Tmin and Tmax values for piloting the summer bypass. Also, there are now different Tmin and Tmax values for Summer and Winter times. Sounds cool!
After I like to to change this new writable float32 registers.
Try to set prmBypassTmaxSummer register, first try use a “call service” in developer tools
service: modbus.write_register
data:
hub: pluggit
address: 764 or 765
value: [30,0] or [0,30] or [11110,0] or [0,11110]
After can connect to iFlow3 tool to reset to default.
It’s a Settings → Accessory → select bypass ->save.
0 (wrong) value change to deselect bypass any time.
How to write a float32 register in modbus service?
Hi, I think I could need some help.
I must have made a mistake with the registers and now my pluggit is confused with its bypass-state. Wenn bypass is open it thinks it’s closed and when it’s closed it thinks it is open. I can open and close bypass via Home Assistant or the phone-app, but it ist always the wrong way. I tried to get rid of this error by restarting the pluggit and even by physical deinstallation and reinstallation of the bypass, but the error still is there. Has anyone an idea of how to tell the pluggit, that the bypass is open when it really is open?
So far I have only managed to edit values for prmBypassTmax (Tmax winter) - trying to write to the other 3 registers Tmin (winter), TmaxSummer and TminSummer always fails and sets them to 0 or the lowest possible value.
The example below is an automation triggered by a slider (input_number) entity to change values of Tmax winter:
Unfortunately the settings in accessories don‘t change anything. If you deselect Bypass you just can’t activate it via the App. You still can activate it via modbus, even if it is deactivated in the settings. But I found the solution. If you log into iFlow 3 as admin you find an endless register of values. One is called „prmNeedInverseBypassState“. This was set to 1. I changed it to 0 and now it works perfectly.
I happened to stumble upon this thread and noticed a striking similarity between the Modbus descriptions in both this threads and this one.
As the author of the Dantherm integration, I don’t see any reason why it shouldn’t also work with Pluggit units as well as the Dantherm units. Even the apps from both brands show a noticeable resemblance.
Check out the linked discussion, and if anyone is interested in testing the integration, I’m considering creating a separate Pluggit integration using the same code.
Hi neotigger,
Thank you for confirming. Would it make sense to adapt the integration for Pluggit, or is there already an existing solution for Home Assistant? I have tried looking around, but didn’t find anything.
No, there is nothing else in existence for Pluggit and Home Assistant. Great to hear that Dantherm and Pluggit are mostly the same thing.
Can we do anything to help adapting your integration for Pluggit? You can have me (and most likely neotigger) for real-life, real-device tests. I also happily provide you pcapng packet captures from the Pluggit App and the Pluggit AP310 device, if needed.