So this is what I am working on at the moment and I am going to try node red and see if that works!
Loxone modbus code#
But as far as I can see HA can only write using function code 6 for single registers or 16 for multiple.
Loxone modbus update#
Using write_register service I can set all of these registers individually but the inverter dose not respond to any changes! I have been advised to test writing multiple registers at once using function code 10, as per your manual snippet, to update the “Time-charging” registers as a group. So I can force it to charge but only up to 40% for some reason!Īccording to the manufacture you are meant to use the “Time-charging” discharge and charge times and rates to be able to force the inverter to charge and discharge at any time or rate. De teller kan tot 65A meten in twee richtingen (bi-directioneel) en wordt serieel verbonden met de Loxone Modbus. In a Loxone Smart Home, everything is managed and controlled from a central, intelligent nerve centre the small green Loxone Miniserver. So at the moment I can read all the registries and pull all the data documented in the modbus manual. ‘0x1 0x3 0xa8 0x85 0x0 0x1 0xb5 0x83’ - name: Solis Time Chargeing Charge Current #U16 Or in the example below changing it to “holding” gives function code 3 e.g. Yes I managed it, I had not realized the importance of “holding” or “input” register type setting and how that affects the function code.īasically I had to change the register_type from “holding” to “input” to get the correct function code which in the case of Solis and the 33k range was function code 4 or 0x4. Any insight from anyone would be appreciated! However when reviewing the HA Modbus specification at Modbus - Home Assistant (home-assistant.io) it says that by default its using 6 for a single value and not 4! So I am not sure what’s happening and why I am getting any reading at the moment. Hope that’s understandable and thanks in advance.ĮDIT: After talking with the manufacture they confirm that we need to be using function 6. So the question is, is there a way I can force the function code so I can test to see if this helps with reading the required registries. ADAM-6000 accomplishes the integration of automation and enterprise systems easily through internet technology, so that users can avoid changing the entire. RS-485: any RS-485 interface, RS-485 connections. The motion sensor is one of the most important sensors in a Loxone Smart Home it provides the. Modbus: Modbus connections Timberwolf Server, ElabNET Modbus RTU Extension, Loxone Modbus Extension. With reviewing the Modbus manual from Solis it seems that the function code for the selection of requesters which is not working is 06H (6) not the same as the ones which work 04H (4) Want to add a Modbus interface to your Loxone system. I have played with the data_type and also the count but they are listed as the same format within the modbus manual as registries I am reading correctly as above, (U16 or count:1) As seen below.īoth of the charge and discharge rates should be 50A and the hours and mins should just be integers between 0 and 60.
Loxone modbus serial#
The issue is that when reading other registries I am getting data back which I am not expecting. Simply integrated: With the serial Modbus interface and the template in Loxone Config, the energy meter is integrated into the building automation. name: solisbatterydischargecurrentlimitation * The asterisks stand for any character in the asterisk' position.- name: solisbatterychargecurrentlimitation
The documentation start with this few line, but i'm not sure if this mean BMS.
I need to figure out if my ventillation system can communicate with Modbus TCP or not (i have no Modbus RTU modul for my loxone, but with Modbus TCP i can solve my problem. Ensure the compatibility of this gateway with your AC model by visiting Hello, I would like to integrate my ventillation system to Loxone home system.
0 kommentar(er)
