Everything posted by Guy Lavoie
-
Do we have the new UI on Polisy?
Works for me. See the 6.0.0 support thread.
-
Questions after update to IoX v.6.0.0
-
Questions after update to IoX v.6.0.0
Now that this is officially released, I thought I'd at least give it a try on my lab rats. I have two Polisys (or is that Polisies?) that I use for testing. On the first one I tried, the upgrade seemed to go through, but the version was still 5.9.1 and the OS was still 14.1. So I logged in by ssh and watched the upgrade process (tail -f /tmp/udx.upgrade.log) and relaunched the upgrade in admin console. It was failing due to the filesystem being full. Interesting. using the unix "df" command showed that the zudi/ROOT/default filesystem had 6424805 blocks, and the heading indicated 512 byte blocks, and was full. Ok, so I sshed into my other Polisy to compare. That one has 25621361 blocks, and the heading is for 1K blocks. Makes a lot more sense for a 32 GB SSD. So I logged into Admin Console on that one, launched the update...and it worked. 6.0.0 in all it's glory! And on a Polisy! I finally got to take a look at easyui. It will take some getting used to... but I can get a feel for it and learn, and keep up with the new releases before making the actual plunge with my eisy. It certainly is "dark" mode. Hopefully we'll be able to customize the look at some point. Back to the Polisies (or is that Polisys?) I'm mostly posting this for others who might try it. The one that shows a much smaller filesystem size is one that I restored using rufus and an image file that UID sent me. Rufus seems to detect and leave existing filesystems in place, only restoring the contents. Both Polis...whatever have 32 GB SSDs, so I wonder if the filesystem setup or configuration was ever changed. The one that failed is an older unit, and it's Unit ID (MAC address) is lower. Anyways that would be the subject of a separate discussion, or if anyone has a thread or other hints on how to set it up. Just a hint for anyone else with a Polisy that's trying to install eisyui and runs into a similar problem.
-
What About POLISY?
Well, IoX 6.0.0 just got released now, and Polisy is included:
-
Linking new insteon devices not working
The "Pro" thing is a node limit in the ISY994i, which is different from the link limit in the PLM. It might still be worth checking out though.
-
Linking new insteon devices not working
What I said was "bring" it, not "bridge". Basically, install it temporarily near other working devices, and try linking. If it's a wall switch, connect the white and black wires to a power cord and plug it in. The idea is to determine if it's the switch itself that's the problem, or it's location. Plugging a lamp module into a long extension cord to bring it close is also a viable thing to try.
-
Linking new insteon devices not working
If you have spare dual band lamp modules handy, try putting one on each panel. They will act as phase couplers. If your nearest working device is 100' away from your new ones, then that would probably explain your problems with linking. Try temporarily bringing one of the new switches near your working ones and try again.
-
Linking new insteon devices not working
There is a limit of the number of links that the PLM can have. It's something around 1000 (or 1024). You really need a large amount of devices (a couple of hundred) to hit that. You see how many you have by going in Tools -> Diagnostics -> Show PLM Links Table. Click on Start and wait for the links to be retrieved. Then click on Count.
-
Linking new insteon devices not working
Look here. But if you're having trouble adding device types that are the same as some you already have, then something else might be wrong, like your PLM going bad.
-
Program running unexpectedly.
Else statements that actually perform actions should be very rare. Usually they'll just do something like reset a variable.
-
Accessory building on separate power meter
Well the REST api is when you want to go the other way: from an external device, computer, etc TO the polisy. Your initial post is about having the polisy send commands to the devices in the new building, over wifi. Assuming you want to control simpler things like lights or appliances, using devices that support Matter would probably be the most straightforward way to do that. If you use wifi based Matter devices (ie: not Thread) then your polisy should be able to do that already, if it is running IoX 5.9.1. Matter is still in beta development, so some testing would be required. Otherwise, you could use other IP based devices with an open protocol, and control them via a plugin if there is one, or using Network module commands.
-
Accessory building on separate power meter
If you are using Insteon dual band devices (like almost all of them currently are) then they should work, since it's rf based. It depends on how far apart the two systems are, for proper communications.
-
Replaced PLM, it will not talk to devices>>SOLVED!
I have an Elk ESM1 signal meter from my X10 days, and it has been handy for seeing Insteon powerline transmissions, and noise. Not perfect, but if the noise is bad enough, it can give you a quick hint.
-
Eisy will not come online after being powered down
You might need to hook up a hdmi monitor and keyboard, and see how it comes up. Have you tried reconnecting it back where it was to see what happens?
-
IoX 6.0.0?
I'm always leery about versions ending in 0.0. I have no real need to update yet so I'll wait until the initial issues are worked out.
-
Adding to Scene
Another thing with scenes is that when you launch one that has several Insteon responders, Insteon communications will be busy for a noticeable period of time, up to a couple of seconds. This is because of the "cleanup" messages that are sent back and forth between the devices. If you have programs that launch scenes, avoid any programming that sends more Insteon commands immediately after launching a scene. Wait a couple of seconds. Commands sent too soon might not be reliable, and might even cause a dreaded "all on" event.
-
IoX Launcher will not load LAN Console
We love happy endings! But...make a backup or three, right now! And clean the contacts on your SD card. Then you'll be all set for a while yet.
-
NEW....Hue Bridge Pro (New Black Unit)
I doubt that someone will rewrite the Hue plugin to use the V2 API. I'd try Matter, which is still in beta on the eisy. Matter was specifically created to allow interoperability between systems, and this is a good example of that. You'll probably get the basic functionality, minus some of the fancier features.
-
Using Z-wave as a scene controller
To avoid the loop, you could use a state variable as a timer, to disable the scene command trigger for a few seconds after having just sent one. But this only works correctly if you can detect the reception of the actual command (control), not a status change. Something like this: If zwave_control Turns ON And Variable_Timer = 0 Then set scene... Then Variable_Timer = 1 If Variable_Timer > 0 Then Variable_Timer +1 If Variable_Timer =5 Then Variable_Timer = 0
-
NEW....Hue Bridge Pro (New Black Unit)
A quick search turned up this AI answer: "No, the Hue Bridge Pro does not support the deprecated V1 API; it requires the V2 API to function". So that's that. You might need to access your Hue devices as Matter devices instead, which the new bridge supports.
-
New Network/ISY
Is your ISY994 configured to get it's IP address by DHCP? If so, did your old router have a reserved IP address for your ISY994's MAC address?
-
NEW....Hue Bridge Pro (New Black Unit)
I remember that the Hue api for a long time has been "version 1", and that they introduced a more secure version 2, hinting that version 1 would eventually be unsupported. Maybe that was the reason for requiring that you now log in to your Hue account on their phone app. If that's the case, then the plugin would need to be rewritten to use the newer api.
-
Using Z-wave as a scene controller
How about doing it through a program? If zwave_device turns ON Then set scene...
-
UD Mobile Lost It's Configuration
Maybe it wasn't unrelated. I would have worked on the Insteon discovery problem first and once fixed, tried reloading UDM after. You want the controller to be in a normal operating condition first.
-
Light turns on with command of Lamplinc.
It's a fanlinc that identifies as a lamplinc... Might it be part of a scene? If you look at the fanlinc device in Admin Console, do you see it as a responder to any other device.