Workaround I use for “buggy” modules, is to periodically restart them. My rooted toon doesn’t always have the best wifi and the module for it tends to crash if it can’t reach it.
Periodical script I use to kick a module via a cronjob:
Just an update.
I havnt been able to get the binding to work at all.
Have tried MAC only, IP Only, Both…
Thing says online when using MAC and IP together, otherwise stays offline.
I’m not able to get any items to work, it literally get the bug above every 2 milliseconds in my log until after about 5 minutes openhab/rpi falls over and i have to reboot.
I’m running 2.4 release btw
Thanks for the feedback. Can you use telnet and confirm you can connect to port 3310 of your IntesisBox, and if you send ID , it returns information? https://www.intesisbox.com/intesis/product/media/intesisbox_wmp_protocol_specs_en.pdf?v=2.1 are the full protocol specs if you want to try other things. For now, the MAC address setting won’t do anything, since discovery isn’t implemented. My only other suggestion would be to attempt using a 2.5.0 snapshot, since that’s what the binding was compiled against. But it’s been a bit old. Other than that, which particular model of IntesisBox are you using? On the IntesisHome devices, we’ve confirmed that different models don’t behave the same (@pelnet’s MH-AC-WIFI-1 has a local API of some sort, but my FJ-RC-WIFI-1 does not).
So i have just tested (using terminus on ios).
I can connect to it on port 3310 and it periodically (about every minute but havnt timed it) sends back:
CHN,1:AMBTEMP,210
however if i type ‘INFO’ and press return it doesn’t seem to respond to it.
Not used telnet before so you may have to bear with me
And its a ME-AC-WMP-1
UPDATE:
Just downloaded the WMP Config program.
Was running firmaware 1.0.1, have just updated to 1.2.1 so ill test again (its also saying theres another new update)
Well, that’s good that it’s talking on the right port, and the protocol looks familiar. It may just be some feature of your HVAC that mine doesn’t support, and the binding isn’t handling it correctly.
I’ve not used terminus before, but the most likely reason is that it’s sending a newline, instead of a carriage return+newline that intesisbox requires (which is why I suggested telnet, instead of netcat).
TIL WMP Config program. I’m running 1.0.7, but I don’t see any way to do a firmware update (and I’d be kind of terrified to do one, anyway). I’m guessing firmware versions are unique to the device type.
Did you get around to looking into the error at all?
I can give you all the responses / allowed limits from my system now as I have got it all working through the tcp binding instead.
I’m using the Mitsubishi electric box for reference.
@ccutrer so having just started developing I thought I’d revisit this.
Downloaded your source files and loads of errors when importing into VSCODE.
Couldn’t resolve anything (like org.eclipse).
Created a new skeleton and copied over the content of all your files, compiled and tested…
Working now, however still getting the message on the tcp listener so I’ll have a look into it
Yeah, it was written in early 2.4 age, so before the massive refactor of the build system, and exit from the ESH foundation. I haven’t had a chance to update the code for those yet - my current build still works on 2.5 as is.
Wouldn’t work on my 2.5, didn’t ever connect.
Have at least confirmed it controls my a/c unit now.
Just need to do some research on the tcp listener to understand how it works.
Getting a null message back from somewhere
@ccutrer So done some testing.
Added closeConnection() under the inner exception catch for the tcp listener class
This stopped the log flooding so I could see what was going on.
What’s going on is…
If there is no message sent by either the client or server the connection times out after exactly 2 minutes.
For the time being I have added a send query (on/off) to below the connection check in polling job to keep the connection alive.
Interesting. I get updates pretty frequently from mine, but definitely less often than 2 minutes occasionally. I wonder if yours behaves differently because it’s controlling a different brand of minisplit, or if it’s an OS difference where you’re running OpenHAB.
I had an incline, I’m sure I read it somewhere in intesis’ docs along time ago about it closing the connection when idle but I can’t find it now. Once I stopped the flooding of the logs it was pretty easy to see the pattern.
Anyway, I’m finally up and running, thanks for the initial work.
Haven’t checked comms the other way yet so I’ll report back any errors I find.
Vanes are defo not working (command not supported) so I’ll look over the coming days.
Is there any way to dynamically set the channel ranges based on the return of the LIMIT command? My fan goes 1-5 so having up to 9 is irritating
Sure beats all the log flooding from the tcp binding.
I’ll prob look at adding auto discovery as well so I’ll send you my code if I get round to it
After a lot of research I found out that intesishome is different from intesisbox (this confusion is reported by some people in different forums). I would like to know, is there any way to open an intesishome port?
I bought any units intesishome (IS-IR-WIFI-1) and need work with fibaro =(
You could try using the http or exec binding (not sure what port it communicates on). You’ll need to sniff the urls it uses though. @ccutrer might be able to help as I believe he has a home version too.
One thing though, your reliant on their servers, if you can switch it out
@ccutrer binding with my fix here: (couldnt work out how to create as a pull request as wouldnt let me upload files)
and rebuilt for 2.5.2
just a couple of lines added in main handler to send a keep alive in your polling method and altered bottom method to stop log spamming
