I have a MAX! Maxcube ELV system.
The temperatures do not appear to me. The ELV software is closed.
openhab V 1.7.1 MaxCube V 1.4.1
My Config:
openhub.cfg
################################ MAX! Cube Binding ############## #######################
#
# MAX! Cube LAN Gateway IP Address (Optional, can be auto-discovered)
Maxcube: ip = 192.168.188.222
*.items
Group All
Group gEG (All)
/* Gang */
Number Heating_Max “Thermostat Gang [%.1f °C]” (gEG) {maxcube=“JEQ0386989”}
What am I doing wrong?
The log: C: \ OpenHub \ logs \ Maxcube is empty.
Unfortunately, no does not work
I think that the configuration is correct.
The “Maxcube” Log in “C:\openhub\logs\maxcube” is still empty, is this normal?
Why are you looking in a folder named maxcube for log details? It should be a file named maxcube.log.
And the log goes only in a file maxcube.log if you changed logback.xml to do so.
If you didn’t change logback.xml the log of the maxcube binding goes to openhab.log.
According to your screenshot you get humidity and temperature on your openhab bus. Are those from your maxcube or do you have any other weather service enabled?
If this comes from your maxcube, your config is allright, then you have to look for your items and/or sitemap definition for the problem.
Because I don’t use maxcube I cannot help you with your item definition, but it looks okay according to the binding page.
sitemap stoffl label="Stoffl @ Home"
{
Frame {
Group item=gEG label="Erdgeschoß" icon="firstfloor"
}
}
stoffl.items
Group All
Group gEG (All)
/* Gang */
Number Heating_Max "Thermostat Gang [%.1f °C]" (gEG) {maxcube="JEQ0386989"}
I do not know what I’m doing wrong … I think openhab not komuniziert the Maxcube. I can ping the Maxcube - so do not have a Duty - Cycle achieved.
When I close openhab and Max Softare open, then I see the values - the sensors to talk to the Maxcube
I do not know what I’m doing wrong … I think openhab not komuniziert the Maxcube. I can ping the Maxcube - so do not have a Duty - Cycle achieved.
When I close openhab and Max Softare open, then I see the values - the sensors to talk to the Maxcube
New: logback
<configuration scan="true">
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5level] [%-30.30logger{36}] - %msg%n</pattern>
</encoder>
</appender>
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${openhab.logdir:-logs}/openhab.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<!-- weekly rollover and archiving -->
<fileNamePattern>${openhab.logdir:-logs}/openhab-%d{yyyy-ww}.log.zip</fileNamePattern>
<!-- maximum number of archive files to keep -->
<maxHistory>30</maxHistory>
</rollingPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5level] [%-30.30logger{36}] - %msg%n</pattern>
</encoder>
</appender>
<appender name="EVENTFILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${openhab.logdir:-logs}/events.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<!-- weekly rollover and archiving -->
<fileNamePattern>${openhab.logdir:-logs}/events-%d{yyyy-ww}.log.zip</fileNamePattern>
<!-- maximum number of archive files to keep -->
<maxHistory>30</maxHistory>
</rollingPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss} - %msg%n</pattern>
</encoder>
</appender>
<appender name="MAXCUBE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${openhab.logdir:-logs}/maxcube.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<!-- weekly rollover and archiving -->
<fileNamePattern>${openhab.logdir:-logs}/maxcube-%d{yyyy-ww}.log.zip</fileNamePattern>
<!-- maximum number of archive files to keep -->
<maxHistory>30</maxHistory>
</rollingPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5level] [%-30.30logger{36}] - %msg%n</pattern>
</encoder>
<logger name="runtime.busevents" level="INFO" additivity="false">
<appender-ref ref="EVENTFILE" />
<appender-ref ref="STDOUT" />
</logger>
<logger name="org.openhab" level="INFO"/>
<!-- this class gives an irrelevant warning at startup -->
<logger name="org.atmosphere.cpr.AtmosphereFramework" level="ERROR" />
<!-- looger MAX Cube -->
<logger name="org.openhab.binding.maxcube" level="ALL">
<appender-ref ref="MAXCUBE" />
</logger>
<!-- temporary workaround for https://github.com/openhab/jmdns/issues/12 -->
<logger name="javax.jmdns" level="OFF"/>
<!-- temporary workaround for https://bugs.eclipse.org/bugs/show_bug.cgi?id=402750 -->
<logger name="OSGi" level="OFF" />
<!-- temporary workaround to circumvent error messages with any obvious effect -->
<logger name="org.atmosphere.cpr.AtmosphereFramework" level="OFF" />
<logger name="org.atmosphere.cpr.DefaultAnnotationProcessor" level="OFF" />
<root level="WARN">
<appender-ref ref="FILE" />
<appender-ref ref="STDOUT" />
</root>
That logback.xml looks some sort of strange to me, do you have two files or did you just apply a wrong format for “preformatting text” in this forum software?
Take this and replace it with your logfile.xml, it is the default logback with added maxcube logging in a separate file under /logs/maxcube.log
<configuration scan="true">
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5level] [%-30.30logger{36}] - %msg%n</pattern>
</encoder>
</appender>
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${openhab.logdir:-logs}/openhab.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<!-- weekly rollover and archiving -->
<fileNamePattern>${openhab.logdir:-logs}/openhab-%d{yyyy-ww}.log.zip</fileNamePattern>
<!-- maximum number of archive files to keep -->
<maxHistory>30</maxHistory>
</rollingPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5level] [%-30.30logger{36}] - %msg%n</pattern>
</encoder>
</appender>
<appender name="EVENTFILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${openhab.logdir:-logs}/events.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<!-- weekly rollover and archiving -->
<fileNamePattern>${openhab.logdir:-logs}/events-%d{yyyy-ww}.log.zip</fileNamePattern>
<!-- maximum number of archive files to keep -->
<maxHistory>30</maxHistory>
</rollingPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss} - %msg%n</pattern>
</encoder>
</appender>
<!-- put maxcube log in separate file maxcube.log -->
<appender name="MAXCUBE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${openhab.logdir:-logs}/maxcube.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<!-- weekly rollover and archiving -->
<fileNamePattern>${openhab.logdir:-logs}/maxcube-%d{yyyy-ww}.log.zip</fileNamePattern>
<!-- maximum number of archive files to keep -->
<maxHistory>30</maxHistory>
</rollingPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%-5level] [%-30.30logger{36}] - %msg%n</pattern>
</encoder>
</appender>
<logger name="org.openhab.binding.maxcube" level="ALL">
<appender-ref ref="MAXCUBE" />
</logger>
<logger name="runtime.busevents" level="INFO" additivity="false">
<appender-ref ref="EVENTFILE" />
<appender-ref ref="STDOUT" />
</logger>
<logger name="org.openhab" level="INFO"/>
<!-- this class gives an irrelevant warning at startup -->
<logger name="org.atmosphere.cpr.AtmosphereFramework" level="ERROR" />
<!-- temporary workaround for https://github.com/openhab/jmdns/issues/12 -->
<logger name="javax.jmdns" level="OFF"/>
<!-- temporary workaround for https://bugs.eclipse.org/bugs/show_bug.cgi?id=402750 -->
<logger name="OSGi" level="OFF" />
<!-- temporary workaround to circumvent error messages with any obvious effect -->
<logger name="org.atmosphere.cpr.AtmosphereFramework" level="OFF" />
<logger name="org.atmosphere.cpr.DefaultAnnotationProcessor" level="OFF" />
<root level="WARN">
<appender-ref ref="FILE" />
<appender-ref ref="STDOUT" />
</root>
</configuration>
But anyway, according to your screenshot of the openhab startup process you have your temperature on your openhab bus and I cannot find any problems in your sitemap or items file.
Have solved the problem, you must also install the correct Addon among addons, then does it all =)
A few questions remain unanswered:
How can I add a eco switch?
How can I send the thermostat a value? - I found this a bit, unfortunately very little with it
For the ecoswitch there is little to control. I think you can add it, but It does not send it’s status information with any meaningful information (outside battery level). Therefore even in the original application of the vendor you can’t see the ecoswitch status
