larryllix

Are you attempting to connect the Tag manager to a secondary router (Actiontec) talking to your primary router (Netgear) via WiFi? Routers don't typically block any traffic from inside your LAN unless you enable those special features. Native router firewalls are for outside initiated traffic and this is not the case for a Tag Manager on your LAN. It doesn't require any port forwarding from outside to inside your LAN.. I doubt you had to punch holes in your router firewall to browse the Internet. You shouldn't have to, to allow your Tag Manager communicate to the outside world either, a basic router function. Once you enable those router features in your router then only specific IP addresses and ports may be allowed to pass, depending which method you blocked things with, usually one of two methods.... Block everything except the list I specify or Allow everything except the list I specify. I don't use any blocking features in my router for LAN traffic.

I thought of that and marked Home as a house over a block but the screen has so many lines worn into it I can almost feel a groove to my house

It's never a problem until it is....

A few have found with dual band routers that the antenna system just can't handle the power output into two frequencies. Turning the power output levels down in your router, or access point, increases the success of most device comms. Sent from a tiny keyboard. Response may be brief.

Your firewall will accept an IP address of the Tag manager that will allow it free reign to send whatever it wants. This has nothing to do with your router and/or port forwarding. The firewall is part of your OS. Port forwarding is not required for the Tag system. Port forwarding allows things from outside to get through your router into your LAN.

Too bad the module was not supported. It appears to be an easy to use Insteon to serial port bridge that ISY would only need to know standard on, off style commands. Sent from a tiny keyboard. Response may be brief.

The Tag manager requires no port forwarding or any special router treatment. I does it's own connecting just like your browser does. Look into your Firewall settings and make sure they allow the IP address of the TAG manager, to pass. For a test, turn it off.

Only the Program Summary program run times can tell you if the program ran each time. I don't see any other way to determine your program isn't starting to run, and then cancelling itself, due to some other hidden logic elsewhere modifying the variable. Running logic with "is Not 1" is the same truth table logic as "is 0" for a variable only used for boolean function (two values only as 1 or 0) The "is NOT" technique is only necessary with elements creating program triggers that are only True in their dynamic state, while being evaluated from their own event causes. eg. If ...switchlinc is switched On AND ...time is 7:30 PM can never be logically true, as both triggers are only ever true when called by their own logic. Neither have any true static state. Else will be run at 7:30 PM, always Else will be run when On is received, always. If ....switchlinc is NOT switched On will run Else when On is received, always None of this is necessary with logic elements having static logic states of On and Off.

Program logic gets re-evaluated every time a state variable in the logic changes. If the logic section is true the Then section runs. If the logic is false the Else section gets run, and the Then stops. In one of the v5.x versions the program got re-evaluated every time a value was installed in the state variable (think Rest also), instead of only upon a change. I believe this was corrected now to behave like other variable controlling methods. Program logic is not evaluated if the value doesn't change upon a variable value write. It would be a waste of ISY engine time.

From your first statement the success of the program running is intermittent. If this is the case, and I think oberkc gave some good troubleshooting techniques, is the running of the program recorded in the program summary tab when the program appears to fail from manually changing the variable? If the summary shows it ran by time synchro, and the program did not run then something is turning it off again, suggesting variable negative feedback or defective ISY engine processing. At that point, with absolute proof, I would do an ISY factory reset and test again, then UDI contact. Bad SD or contacts? Did you state which ISY revision you are using?

Have you manually changed the value of the variable to divide the problem into output or input from the variable value? Does the variable state have any dependency on the state of the humidifier? Creating a negative feedback loop. Is your program triggers enabled? Have you checked and compared the links in the output module? factory reset it and restored?

Really cool device but it seems very new and therefore no support for it would be installed in ISY994, yet. May be worth requesting support in the feature request thread to UDI.

I was going to become one but maybe later.

It was some debugging/testing process the code writer went through, that left some French residue in most of our voicebases by accident. Glad your working again!

The main problem is... ISY cannot parse inputs. Sent from a tiny keyboard. Response may be brief.

Once somebody brightens one light in a scene involving 20 devices, is the scene now on or off? Varying scenes is an oxymoron. Sent from a tiny keyboard. Response may be brief.

SH cares a lot about quality. Some indicators are there. They just have extremely poor management that don't understand how to effect it. Quality Assurance will never make good customer relations. Somebody is reading the failed 1970's management playbook,still, proven unworkable for so many years.

The temperature range given in the spec. is a conservative range for the electronics. The range I posted is from actual testing, as mentioned in my post. Look at the data stream in the Admin Console events and it soon will become apparent the data values, 0-255 counts, are 0 - 127.5 degrees C. Each binary increment is 0.5C. For 22.5C reading you will see a 55 value in the data stream. For 15.0C, the data stream will read 30. Humidity reads one for one percent. BTW:When external is selected on the stat, the value sent is one degree C for each count so the resolution is only 1.0c instead of 0.5c for the internal selection. The negative values are interpretations using standard signed 8 bits values. A value of 254 eauates to -1.0 degree C. This was never intended to happen and ISY does not interpret it as such as the value would also represent 128.0C, which would be the correct interpretation. Also, accuracies are probably out to lunch at these points, outside the stated range allowance.

That's 0 to 127 degrees Celsius in 0.5C increments. 0 to 254 counts on the binary transmission scale, the capability of one byte of data. I ran tests on one of my 2441ZTH units and it sent temperatures to ISY down to about -2.5C but the temperatures were not interpreted by ISY correctly, as they are sent as two's complement negative numbers, which ISY doesn't interpret. At that coldest temperature the stat electronics failed and resumed later, when the stat was warmed up.

Use some hot breath or a few seconds with a hairdryer to initiate a temperature change update. There is no other way except to wait for a temperature change of a few degrees. Query won't do it.

Just access the STATE variable tab in admin console. Type in a name for a variable and hit save. Write a test program to save a value into the variable. Check the variable page again to see your value stored there. Write another test program with an IF line using your variable testing if the variable is equal to 5. In the then section write lines to turn a light on or off as an indicator. Manually change the value of the variable, hitting enter each time and watching the indicator you wrote. You're using variables. Play, play, play. Sent from a tiny keyboard. Response may be brief.

Wc8 is web control board by CAI. A small controller board with inputs, outputs, and anslogue inputs and can shoot values into isy's variables via the test interface. Sent from a tiny keyboard. Response may be brief.

Many of us have isy slave RPis and or wc8 boards feeding data into our isy. It would be a simple job to detect the local LAN system and router is functioning inside isy. Sent from a tiny keyboard. Response may be brief.

I confess. I haven't tried it with v5.0.8 But the 2441zth can only send one. Sent from a tiny keyboard. Response may be brief.

Isy just ignores the external data that is sent. We proved it is sent in another discussion Sent from a tiny keyboard. Response may be brief.