candstand

Tak Anton. Det virkede perfekt.

Burde det ikke være muligt at sende en temperatur fra Homeassistant over i rumtemperatur indgangen i varmestyringsfunktionsblokken. Indgangen er manuelt oprettet som en sensor i configurations.yaml Jeg har også prøvet ihc id i i Entity. Samme fejlkode.

Thank you Pauli. That made a big difference. The logfiles is growing fast, and my old computer is choking. I copied log files to a text-file from just before i restarted the IHC binding. Now i succeeded making a Enum channel, but not a floatiog point real decimal number. Thank You. 201812151909.txt

Sorry, I'm no Linux expert at all. But hopefully learning. Deleted all other bindings, and restarted IHC/ELKO binding, and hope this is the log that explains what happens. I believe that 2017/34 is the production date of the IHC controller. Forgot to mention that the temperatures from the temperature-sensors didn't show the dot and the digit after the dot. (with org.openhab.binding.ihc-2.4.0-SNAPSHOT ) Log 20181215_1514.txt

I'm not sure i did it right, but here you get the file: "org.ops4j.pax.logging.cfg" from /var/lib/openhab2/etc I have no Linux skills, and don't know how the log is made, but it seems that the logfile is timestamped only when i run the log:set trace command. Is it the right file? # Common pattern layout for appenders #log4j2.pattern = %d{ISO8601} | %-5p | %-16t | %-32c{1} | %X{bundle.id} - %X{bundle.name} - %X{bundle.version} | %m%n # Root logger log4j2.rootLogger.level = WARN log4j2.rootLogger.appenderRefs = out, osgi log4j2.rootLogger.appenderRef.out.ref = LOGFILE log4j2.rootLogger.appenderRef.osgi.ref = OSGI # Karaf Shell logger log4j2.logger.shell.name = org.apache.karaf.shell.support log4j2.logger.shell.level = OFF log4j2.logger.shell.appenderRefs = stdout log4j2.logger.shell.appenderRef.stdout.ref = STDOUT #Â Security audit logger log4j2.logger.audit.name = org.apache.karaf.jaas.modules.audit log4j2.logger.audit.level = INFO log4j2.logger.audit.additivity = false log4j2.logger.audit.appenderRefs = audit log4j2.logger.audit.appenderRef.audit.ref = AUDIT # openHAB specific logger configuration log4j2.logger.openhab.name = org.openhab log4j2.logger.openhab.level = INFO log4j2.logger.smarthome.name = org.eclipse.smarthome log4j2.logger.smarthome.level = INFO log4j2.logger.smarthomeItemStateEvent.name = smarthome.event.ItemStateEvent log4j2.logger.smarthomeItemStateEvent.level = ERROR log4j2.logger.smarthomeItemAddedEvent.name = smarthome.event.ItemAddedEvent log4j2.logger.smarthomeItemAddedEvent.level = ERROR log4j2.logger.smarthomeItemRemovedEvent.name = smarthome.event.ItemRemovedEvent log4j2.logger.smarthomeItemRemovedEvent.level = ERROR log4j2.logger.smarthomeThingStatusInfoEvent.name = smarthome.event.ThingStatusInfoEvent log4j2.logger.smarthomeThingStatusInfoEvent.level = ERROR log4j2.logger.smarthomeThingAddedEvent.name = smarthome.event.ThingAddedEvent log4j2.logger.smarthomeThingAddedEvent.level = ERROR log4j2.logger.smarthomeThingRemovedEvent.name = smarthome.event.ThingRemovedEvent log4j2.logger.smarthomeThingRemovedEvent.level = ERROR log4j2.logger.smarthomeInboxUpdatedEvent.name = smarthome.event.InboxUpdatedEvent log4j2.logger.smarthomeInboxUpdatedEvent.level = ERROR log4j2.logger.events.name = smarthome.event log4j2.logger.events.level = INFO log4j2.logger.events.additivity = false log4j2.logger.events.appenderRefs = event log4j2.logger.events.appenderRef.event.ref = EVENT log4j2.logger.events.appenderRef.osgi.ref = OSGI log4j2.logger.jupnp.name = org.jupnp log4j2.logger.jupnp.level = ERROR log4j2.logger.jmdns.name = javax.jmdns log4j2.logger.jmdns.level = ERROR # This suppresses all Maven download issues from the log when doing feature installations # as we are logging errors ourselves in a nicer way anyhow. log4j2.logger.paxurl.name = org.ops4j.pax.url.mvn.internal.AetherBasedResolver log4j2.logger.paxurl.level = ERROR # Filters known issues of pax-web (issue link to be added here). # Can be removed once the issues are resolved in an upcoming version. log4j2.logger.paxweb.name = org.ops4j.pax.web.pax-web-runtime log4j2.logger.paxweb.level = OFF # Filters known issues of lsp4j, see # https://github.com/eclipse/smarthome/issues/4639 # https://github.com/eclipse/smarthome/issues/4629 # https://github.com/eclipse/smarthome/issues/4643 # Can be removed once the issues are resolved in an upcoming version. log4j2.logger.lsp4j.name = org.eclipse.lsp4j log4j2.logger.lsp4j.level = OFF # Filters known issues of KarServiceImpl, see # https://github.com/openhab/openhab-distro/issues/519#issuecomment-351944506 # Can be removed once the issues are resolved in an upcoming version. log4j2.logger.karservice.name = org.apache.karaf.kar.internal.KarServiceImpl log4j2.logger.karservice.level = ERROR # Appenders configuration # Console appender not used by default (see log4j2.rootLogger.appenderRefs) log4j2.appender.console.type = Console log4j2.appender.console.name = STDOUT log4j2.appender.console.layout.type = PatternLayout log4j2.appender.console.layout.pattern = %d{HH:mm:ss.SSS} [%-5.5p] [%-36.36c] - %m%n # Rolling file appender log4j2.appender.out.type = RollingRandomAccessFile log4j2.appender.out.name = LOGFILE log4j2.appender.out.fileName = ${openhab.logdir}/openhab.log log4j2.appender.out.filePattern = ${openhab.logdir}/openhab.log.%i log4j2.appender.out.immediateFlush = true log4j2.appender.out.append = true log4j2.appender.out.layout.type = PatternLayout log4j2.appender.out.layout.pattern = %d{yyyy-MM-dd HH:mm:ss.SSS} [%-5.5p] [%-36.36c] - %m%n log4j2.appender.out.policies.type = Policies log4j2.appender.out.policies.size.type = SizeBasedTriggeringPolicy log4j2.appender.out.policies.size.size = 16MB # Event log appender log4j2.appender.event.type = RollingRandomAccessFile log4j2.appender.event.name = EVENT log4j2.appender.event.fileName = ${openhab.logdir}/events.log log4j2.appender.event.filePattern = ${openhab.logdir}/events.log.%i log4j2.appender.event.immediateFlush = true log4j2.appender.event.append = true log4j2.appender.event.layout.type = PatternLayout log4j2.appender.event.layout.pattern = %d{yyyy-MM-dd HH:mm:ss.SSS} [%-26.26c] - %m%n log4j2.appender.event.policies.type = Policies log4j2.appender.event.policies.size.type = SizeBasedTriggeringPolicy log4j2.appender.event.policies.size.size = 16MB #Â Audit file appender log4j2.appender.audit.type = RollingRandomAccessFile log4j2.appender.audit.name = AUDIT log4j2.appender.audit.fileName = ${openhab.logdir}/audit.log log4j2.appender.audit.filePattern = ${openhab.logdir}/audit.log.%i log4j2.appender.audit.append = true log4j2.appender.audit.layout.type = PatternLayout log4j2.appender.audit.layout.pattern = %d{yyyy-MM-dd HH:mm:ss.SSS} [%-5.5p] [%-36.36c] - %m%n log4j2.appender.audit.policies.type = Policies log4j2.appender.audit.policies.size.type = SizeBasedTriggeringPolicy log4j2.appender.audit.policies.size.size = 8MB # OSGi appender log4j2.appender.osgi.type = PaxOsgi log4j2.appender.osgi.name = OSGI log4j2.appender.osgi.filter = * log4j2.logger.org_openhab_binding_ihc.level = TRACE log4j2.logger.org_openhab_binding_ihc.name = org.openhab.binding.ihc

Hi i'm new at Openhab. I have IHC controller v3 with firmware 3.3.9 and I installed Openhab 2.3.0 on my RPI3B+. After that i installed org.openhab.binding.ihc-2.4.0-SNAPSHOT.jar by copying the .jar file to the /usr/share/openhab2/addons folder with WinSCP. The binding found my in and outputs automaticaly, and it seemed to work perfect. I tried to manualy add channels from Paper UI. I tried to make a readonly channel to a Enum, and to a floating point number, but both failed. (they both just showed a "-") Then i tried to change the binding to org.openhab.binding.ihc_2.4.0.201812081313.jar, but now the binding failed, and is ofline. "Status: OFFLINE Initializing communication to the IHC / ELKO controller" Here underneath is a part of the log that shows that the bindings is added, but i can't figure out what fails. Where did i fail? How do i get on? 2018-12-14 16:47:37.582 [.ItemChannelLinkAddedEvent] - Link 'ihc_controller_4211b1f3_input3692636-ihc:controller:4211b1f3:input3692636' has been added. 2018-12-14 16:47:37.656 [.ItemChannelLinkAddedEvent] - Link 'ihc_controller_4211b1f3_input3692892-ihc:controller:4211b1f3:input3692892' has been added. 2018-12-14 16:47:37.698 [.ItemChannelLinkAddedEvent] - Link 'ihc_controller_4211b1f3_input3693148-ihc:controller:4211b1f3:input3693148' has been added. 2018-12-14 16:47:37.740 [.ItemChannelLinkAddedEvent] - Link 'ihc_controller_4211b1f3_output3134813-ihc:controller:4211b1f3:output3134813' has been added. 2018-12-14 16:47:37.796 [.ItemChannelLinkAddedEvent] - Link 'ihc_controller_4211b1f3_output8491613-ihc:controller:4211b1f3:output8491613' has been added. 2018-12-14 16:47:37.838 [.ItemChannelLinkAddedEvent] - Link 'ihc_controller_4211b1f3_output9286238-ihc:controller:4211b1f3:output9286238' has been added. 2018-12-14 16:47:45.653 [me.event.ThingUpdatedEvent] - Thing 'ihc:controller:4211b1f3' has been updated. ==> /var/log/openhab2/openhab.log <== 2018-12-14 16:47:46.002 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception java.time.format.DateTimeParseException: Text '2017/34' could not be parsed at index 4 at java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:1949) ~[?:?] at java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1851) ~[?:?] at java.time.ZonedDateTime.parse(ZonedDateTime.java:597) ~[?:?] at java.time.ZonedDateTime.parse(ZonedDateTime.java:582) ~[?:?] at org.openhab.binding.ihc.internal.ws.datatypes.WSSystemInfo.parseXMLData(WSSystemInfo.java:238) ~[?:?] at org.openhab.binding.ihc.internal.ws.services.IhcConfigurationService.getSystemInfo(IhcConfigurationService.java:39) ~[?:?] at org.openhab.binding.ihc.internal.ws.IhcClient.getSystemInfo(IhcClient.java:234) ~[?:?] at org.openhab.binding.ihc.internal.handler.IhcHandler.updateControllerProperties(IhcHandler.java:278) ~[?:?] at org.openhab.binding.ihc.internal.handler.IhcHandler.connect(IhcHandler.java:513) ~[?:?] at org.openhab.binding.ihc.internal.handler.IhcHandler.reconnectCheck(IhcHandler.java:785) ~[?:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?] at java.lang.Thread.run(Thread.java:748) [?:?] 2018-12-14 16:48:19.523 [ERROR] [ersey.server.ServerRuntime$Responder] - An I/O error has occurred while writing a response message entity to the container output stream. org.glassfish.jersey.server.internal.process.MappableException: org.eclipse.jetty.io.EofException at org.glassfish.jersey.server.internal.MappableExceptionWrapperInterceptor.aroundWriteTo(MappableExceptionWrapperInterceptor.java:92) [170:org.glassfish.jersey.core.jersey-server:2.22.2] at org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:162) [169:org.glassfish.jersey.core.jersey-common:2.22.2] at org.glassfish.jersey.message.internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1130) [169:org.glassfish.jersey.core.jersey-common:2.22.2] at org.glassfish.jersey.server.ServerRuntime$Responder.writeResponse(ServerRuntime.java:711) [170:org.glassfish.jersey.core.jersey-server:2.22.2] at org.glassfish.jersey.server.ServerRuntime$Responder.processResponse(ServerRuntime.java:444) [170:org.glassfish.jersey.core.jersey-server:2.22.2] at org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:434) [170:org.glassfish.jersey.core.jersey-server:2.22.2] at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:329) [170:org.glassfish.jersey.core.jersey-server:2.22.2] at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) [169:org.glassfish.jersey.core.jersey-common:2.22.2] at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) [169:org.glassfish.jersey.core.jersey-common:2.22.2] at org.glassfish.jersey.internal.Errors.process(Errors.java:315) [169:org.glassfish.jersey.core.jersey-common:2.22.2] at org.glassfish.jersey.internal.Errors.process(Errors.java:297) [169:org.glassfish.jersey.core.jersey-common:2.22.2] at org.glassfish.jersey.internal.Errors.process(Errors.java:267) [169:org.glassfish.jersey.core.jersey-common:2.22.2] at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) [169:org.glassfish.jersey.core.jersey-common:2.22.2] at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305) [170:org.glassfish.jersey.core.jersey-server:2.22.2] at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154) [170:org.glassfish.jersey.core.jersey-s

Jeg mener nu det giver meget mening at tilføre tilpas varme hele tiden i stedet for at gulvet nogen gange er koldt og andre gange er varmt. Hvis man bruger danfoss regulator eller KNX er der også med "rigtig" regulator. Jeg kunne også bruge det til at regulere fremløbstemperaturen efter udetemperatur.

Er der nogen der har udnyttet visual 3's gangemulighed til at lave en P eller PI regulator, til mere præcis gulvvarmeregulering. ? Hvis det allerede er lavet, vil jeg nemlig ikke gå igang med at lave det. Mvh. Knud Fredslund Toft

Har selv brugt samme løsning, til de dæmpere der bruges til spots, væglamper og udvendigt lys. Det er bare problematisk at den model ikke er opdateret, så den kan bruges til små LED belastninger. Lige nu bruger jeg kun lampeudtagsdæmperen.

Jeg har en plan om at lave noget belysning med 12 eller 24v DC LED bånd, men jeg har brug for at kunne dæmpe det, og foretrækker selvfølgelig at bruge wireless dæmper. Jeg forventer at jeg vil have omkring 30w LED bånd, men er meget i tvivl om hvilken driver der fungerer godt sammen med dæmperen. Er der nogen her med konkrete gode eller dårlige erfaringer, med specifikke produkter.