MrBill

Larry gave you the answer to the question you asked, but the next question is why do you need it in a variable? what are you doing with it at that point? Valid reasons to do that might be a "Save" temp, to restore the thermostat later.... or if you want to manipulate the temp later. However if you're just wanting to display the temp or include it in the notification that can be done without the overhead of a variable.

Devices talk back... Scenes don't. Send ON to a device, the device responds to the sender. Send ON to a Scene, responders turn on but don't generate traffic. Device: Scene: I think the original design consideration (way back almost 20 years ago) was that acknowledgement of signal received was the thing X10 users wanted the most, therefor device ACKnowledge receipt of a signal. However due to the relatively slow speed of wireline transmission it's not practical to do that for more than 1:1 communication. Consider I have a scene use as "downstairs-All Off"... it has 40+ responders, if all 40 responders had to acknowledge it would take way to long and jamb up the network.

tagging @shbatm on this discussion because it involves Home Assistant, even tho you've manually reproduced and indicated the issue is on the IOX/ISY side.

known issue. there's at least a dozen threads with the same question. You don't have bad space, it's a bug that's been around since Polisy was released.

No, but there is a thread for Zigbee Device support requests... Basic zigbee switches might work, but there will be many devices that must be "supported" before they work.

(disclaimer: I didn't carefully read everything said after I saw the issue, but I did skim it and didn't see anyone really pointing this out directly.) It's much easier to use 3 or 4 scene's, one each for Low, Medium, High and optionally one for off, although you can really do off with any of the first 3 scenes). Once you've converted to the multi-scene method, then your programs, Home Assistant, etc can all turn on or off the appropriate scene and the buttons will stay in synch, rather than using all the helper programs you have to update buttons status afterwards.

Since your original issue appears solved, you might want to start a new topic in the UD Mobile section of the forum for better exposure.

Does the white match the white button that smarthome used to print? also the font? I have several places around the house I need to replace a single button because it's function changed. I would likely order an 8 button configuration but I wouldn't be using the buttons in that configuration, when they arrived i would use them piecemeal.

The admin console has program search available after right clicking a program name. it doesn't matter where in the tree you click from, the search will always start at the top of the tree. Its easier to use the various drop downs for objects such as variables/nodes/scenes. When using RAW text keep in mind case counts.

I wonder if @kclenden might get an email from this mention and hopefully log in. He’s the best at reading and interpreting logs and link issues of anyone that’s ever participated here.

Question 1: wired is always the best, plug it in. question 2: either there’s line noise blocking the signal, or something went wrong with the device. Try a factory reset of the device, then click the device in the admin console, right click and choose “Restore Device”. That’s a starting point.

the ISY portal node server is for geofences using occupancy. Not sure how to remove a PG2 node server once PG2 is gone... maybe @bpwwer can advise.

For ISY portal log into the portal. Select Tool > Occupancy Node Server > Configuration and press the remove button. For the other one, I can't guess. I started to say perhaps it's running in PG2, but the name preface "ST-" didn't get prepended until PG3. Do you have another instance of PG3 running?

I think the notification node server is now automatically installed. Not 100% certain of that tho.

@fman47 Do you already have the Polisy? If you purchased it awhile ago then you want to migrate to Polisy (more steps than just loading the backup). if you don't have the Polisy it's no longer for sale and you will be purchasing eisy. (Polisy was available for a relatively short period of time before a supply chain issue derailed its production, after which the 994 replacement became eisy) .

I'd never heard of Meross, but it looks like many of their devices are wifi. In that case if you can paste a url into a browser to control the device then it's pretty simply to interface to any IoX device using Network Resources.

that's not how it works... just stay in the same thread. then we don't have to ask the same questions already answered.

When you say "i have cleared everything in the java settings and rebooted" does that mean you checked all 3 boxes including for "Installed Applications and Applets"? which is not checked by default. Are you using Launcher or a copy of admin.jnlp? Win or Mac? You can also try deleting .state files.

Your best bet is to open a ticket. https://www.universal-devices.com/my-tickets/

it does sound like you've got a bad PLM

Interesting that the there's nothing happening before the reboots. First, Please make sure you have a current ISY backup even if you choose to ignore the rest of this post. There's really only two things that ever die on a 994, the power supply and the MicroSD card. (well the 3rd being the Ethernet port gets hosed by a surge but we can cross that off the list.) I'd try a new power supply first. You can try any power supply that outputs anywhere between 5 volt and 30 volts,center positive, 2mm barrel connector. For a MicroSD card, buy 32gb as it's the largest a 994 will support and the 32gb will be less expensive than 16GB or less. Also look for the newer A1 Rating (A2 is ok, but the ISY994 doesn't have the hardware component required to utilize A2). When replacing the MicroSD card, you must first load the firmware file for whatever firmware you are on. Use Help > Manually upgrade ISY. (The bootloader that gets the ISY online with a new card is not a full version of the firmware, nor is it current). After the reboot following new firmware then restore your ISY backup.

If rebooting the ISY doesn't work. Next open the Event Viewer, set level 3... clear the window then attempt to restore a node. The event viewer and/or the error log may give clues to what's going on.

DO NOT DELETE THE PLM. if you do you'll be starting over. As mentioned above did you "Restore PM", that needs to happen with a new PLM. The PLM must be powered up and stable BEFORE the ISY is booted. Usually plugging in the PLM and waiting 15 or 20 seconds is enough, then plug in the ISY. Have you tried a different cable? Although it's serial communication and not ethernet any standard networking cable will work. If these suggestions don't help, then I suggest you open a ticket rather than randomly trying things (like delete PLM).

The version called IoX Launcher installed on the desktop but start.jnlp downloads the correct admin console each time the admin console is opened. In Finder you're allowed to choose between "Lan" and "Cloud". Lan obtains the admin.jnlp file from the ISY and opens it. Cloud obtains the file from UD's cloud storage. The idea behind launcher is that it should always launch the correct version of the admin console to match the firmware of the ISY. If the ISY is a 994 then picking "cloud" will be faster, due to the 994 being slow at encrypting for TLS, the cloud will be much faster. This less of a concern for Polisy and eisy as they have much faster processors with more horsepower than is being used. Using admin.jnlp instead is fine, just rember to delete it, clear the java cache and re-download it with each firmware upgrade.

Start does make it seem like you're looking at the error log, but what should be of interest to you is what is before the Start. i.e. what caused the reboot. If you're not looking at the error log then yes that's what you need to analyze. if you're having trouble reading it post a few days worth of it.