Michel Kohanim

Hi SSS, Very similar. Please stay tuned. With kind regards, Michel

@SSS, Using native HomeKit support through the Matter protocol (no, you do not need ZMatter). We are working on the details. With kind regards, Michel

I am not sure since HB took too much resources and that's why we tried another approach. We shall keep you posted. With kind regards, Michel

All, an update. It's definitely doable and it does not require FreeBSD version because it's node.js/javascript/typescript based. We did get it to work but the overhead is just way too high and there's no clean integration that we could come up with. One of our customers is working on a streamlined version. So, we have not given up and please stay tuned. With kind regards, Michel

@jkosharek, I will submit to our discord channel. With kind regards, Michel

@RichTJ99, What exactly is the issue? It seems that the nodes are back, are they not? With kind regards, Michel

@ACastiglione, It seems that the install script was not run. Unfortunately you need to reinstall this plugin for the compilation to take place. If you still have problems, please do not hesitate to submit a ticket and we'll help you. With kind regards, Michel

I am glad you voted. Not strange because you have Polisy + millions of devices. So, Polisy is already busy and then it has to also compile this package. Time to "upgrade" to eisy. For me, it took about 5 minutes. With kind regards, Michel

Hello everyone, please try again: 1. Upgrade Packages 2. Install Dev Packages 3. <Restart IoX> 4. Reinstall Kasa (you must reinstall) 5. Ignore timeout ... compilation of kasa module takes about 5 minutes on eisy and 10 minutes on polisy With kind regards, Michel

@macjeff, Are you being patient? This process will try to recompile the required package. So, before saying "This didn't do anything for me", check the logs and make sure it's being compiled. Or, at the least, attach the logs. With kind regards, Michel

Hello everyone, We are looking into all these issues: 1. The UI is wrong on the first day after DST end 2. current day of the week is 0 instead of 1 3. Next scheduled run time is 1 hour ahead @ShawnW, Please upgrade (Admin Console | Configuration tab | Upgrade Packages). With kind regards, Michel

As of right now, everyone with this issue has the correct next schedule time. Do we have anyone that does not? If so, we desperately need access to that system. With kind regards, Michel

@johnstonf, Forum is not our medium for support. You don't want to submit a ticket, so be it and good luck. With kind regards, Michel

Hello all, Apologies for the problems. The UI in the Admin Console is definitely incorrect. This said, the program should be fine. Does anyone have any example (screenshot) of programs having the wrong next runtime (ether sunset/sunrise or both)? With kind regards, Michel

@whywork, 1. UD Mobile WiFi Setup is only for eisy 2. If you move to PG3x, and although you keep your WiFi configuration, you can no longer configure your WiFi setup using PG3x If your WiFi configuration works, please upgrade to PG3x as we are no longer maintaining PG3. With kind regards, Michel

@Panda88 is very active and engaged. With kind regards, Michel

@johnstonf, So, those correspond to your commands to GH? With kind regards, Michel

@AnthemAVM, they should be supported. The first thing I recommend is to go to Z-Wave | X-Ray | Choose DH Controller from the drop down, and then click on the Go button. Look for Frequency and make sure it's set to US. If it is, please submit a ticket. With kind regards, Michel

@johnstonf, Are you controlling ZW_009? With kind regards, Michel

@maxnorth, Have you contacted the author of the MQTT plugin? I will post your question on Discord. With kind regards, Michel

Hi Fred, It's not a rabbit hole. Just trying to see what the event viewer shows. With kind regards, Michel

@maxnorth, Apologies, it's gen.mosquitto.ud This is a plain mqtt broker. There are no documentations above and beyond those you can get from: man mosquitto With kind regards, Michel

Hi John, Based on what you are saying, I think it's signal/noise related. i.e. ISY retries 3 times during which time GH times out. The next experiment: 1. Open Event Viewer, change the Level to 3 2. Issue the commands again 3. What do you see in the Event Viewer? With kind regards, Michel

@Lore, Is it just the Hue or other node servers too? Also, does it come back on its own? With kind regards, Michel

@johnstonf, What's common between these devices? For instance, are they all dimmers or switches? What if you create a program that controls these devices and then call the program (using a differnet name). Does this work? With kind regards, Michel