larryllix

This will be coming to Ontario some year soon. Applied and approved in 2020 but some board is waiting for Quebec and NY to co-operate also.

I like colour for On and Off devices and possible Lighter green for partially ON (1-99%) but don't want to see 15 different colours for temperatures, and other analogue things. Too much becomes a garden of visual nonsense. Alarms needs their own colours and that demands a plain background, again, so they don't disappear in a sea of colours. Of course there are blinking colours for alarm levels too.

Looks like it came back. My polisy is a mess now and needs PG3 nodes re-installs along with refreshing programs to use the rebuilt labels. I've had worse but this is annoying to have to recheck every node parameter. Thanks to whomever fixed it.

Eisy-ui told me all nodes were migrated and asked m if I wanted to remove my PG3 nodes. When I replied YES, all nodes ceased to function and ALL NODES WERE REMOVED from my polisy. None would function from eisy-ui. When I reinstalled RYSE, and others, nodes were generically installed again but no programs function. I have been busy renaming nodes and update jerking programs to use them again. Basically starting from scratch except dead programs still exist but do not activate any restored node. BTW: after saving each program (after a useless edit) eisy-ui complained about not saving the update each time I attempted to exit (it was). I had to click "Discard" each time to proceed.

Exception list after renewing java temporaray files and installing IoX Finder attempt.

Re-installed latest java. Firefox does not like and will not bypass the bad certificate this time.

I tried power cycling the ecobee stat and the got the same...no response

Thanks. 1,2 done, 3 skipped. 4 results in no feedback whatsoever. Am I missing something? Does the system jumping back and forth from PG3x to PG3 matter? I get a page wanting me to migrate to PG3 or back. Also, how would I tell if my ecobee is already paired to something? I have no Apple devices. Log always shows this file missing despite many UPGRADE PACKAGES completed. 2026-10-18 18:11:32.906 MainThread udi_interface ERROR udi_interface:write: import aiomqtt 2026-10-18 18:11:32.907 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError

Thanks but that takes me around in circles again. I cannot Discover anything. Reading the github webpages referes me to other github pages that refer me to more github xxx.MD pages. I am lost. HomeKitHub node always shows "NOT CONNECTED" I have tried about 5 different ecobee PINS now but I am not finding any title for the PIN. I have been using "hap_pin"

Does this Plug-in install into PG3x or PG3? Every time I see the Home screen it shows me random versions, so I am not sure if this is a problem or why there are two versions showing up. I have been reading github files for hours but nothing seems to work or apply. I have been trying to re-install, and restart the HomeKitHub many times and no ecobee stat shows up in a list. I have never seen a list, empty or otherwise. My ecobee shows a small QR code with an 8 digit number but no connection has ever been made, to my knowledge. HomeKitHub only ever shows CURRENT STATUS: "Disconnectd" in red. I is not clear where it is not connected, ISY or the Stat.

That is the 64 GB, fully captured by the polisy system.

I'm obviously not understanding this sector usage chart on my polisy but some things just don't seem to add up to 32GB being full. ---------------------------------------------------------------------------------------- [admin@polisy ~]$ df Filesystem 1K-blocks Used Avail Capacity Mounted on zudi/ROOT/default 60295013 4666919 55628093 8% / devfs 1 0 1 0% /dev procfs 8 0 8 0% /proc zudi/tmp 55628128 35 55628093 0% /tmp zudi/usr/home 55628183 90 55628093 0% /usr/home zudi/var/polyglot 10485760 55429 10430330 1% /var/polyglot zudi/var/isy 10485760 56322 10429437 1% /var/isy zudi/var/log 55628710 616 55628093 0% /var/log zudi 55628117 24 55628093 0% /zudi zudi/var/tmp 55628117 24 55628093 0% /var/tmp zudi/var/empty 55628117 24 55628093 0% /var/empty zudi/var/db 55629372 1279 55628093 0% /var/db zudi/var/run 55628142 48 55628093 0% /var/run zudi/var/crash 55628117 24 55628093 0% /var/crash zudi/var/db/pkg 55663864 35770 55628093 0% /var/db/pkg

Thanks but ll seems to be working now with the method I used. It doesn't seem to make sense I am using 32GB of SSD with this system though. Others didn't need the extra room, apparently.

I found info on expanding your freeBSD SSD drive partitions and so far...it seems totally successful. It took some nerves and some guessing at system naming but I got through it. https://kb.royalehosting.net/en/article/how-to-resize-a-freebsd-partition-eu4wlu/#2-3-resize-the-partition The last line needs to use "zudi" instead of the "zpool" as listed. The line number 5 referred to was line 3 in my system. I think I had to reboot my polisy when done as eisy-ui seemed a bit of a mess. Took a while to come back without insanity. Things are much better. Lines are still little too fat vertically but much, much better. From what I can remember now, those boxes can never be filled out to the edges in HTML code. Nice going @Javi (pat on the back)

I just realised that imagers require an image, not a file backup. Can the imagers produce an image from and existing HDD? I gave up on Rufus last time. It didn't appear to be able to handle and image larger than 2 or 16 GB. I d/l another program (diskimager) and it worked just fine. There still must be something wrong with 32 GB used up on this system. There has to be tonnes of spare space left, somewhere. Even the df counts don't add up to the totals. Three main folders show about 55MB each and a few others show 1-2MB each. I can't account for more than about 250 MB (0.25 GB). ????? Did you get your eisy-ui into your 32GB partition?