larryllix

FRom your logs it appears your Dysan NS is not set up properly.

Tuya uses a complex interactive protocol like HTTPS does. I am not sure the protocol is available to code writers and I have never seen a hack of it....yet. For remote control usage only..right on the money. For HA usage...maybe never.

Lutron protocol seems to be a secret. I have found a dozen articles telling how other protocols and frequencies are no good but never anything disclosing what Caseta uses.

Most routers will not allow a reservation outside of the allocated IP address pool. The IP addresses they manage are only inside the allocation pool and some will not even allow access to other IP addresses outsdie of their IP management range. They are designed to work that way. AiMesh routers has a lot of problems. I went though hell and back with my AC68u for years. When I replaced it with a AX98u router more problems started. Then I discovered the AC68u router couldn't handle more than 51 devices. I would just forget some devices and my ISY and polisy were both found operating with IP addresses of 0.0.0.0 once after a total failure of function. In a desperate attempt to fix this I added a second AX92u router to my AiMesh and things got even worse. After swapping routers around a few times I discovered my Roku Stick+ would not stay connected to my 5Ghz band and I then discovered that most mesh routers turn the magnitude down to about 10-20% of what a router puts out, using other equipment. I contacted ASUS and paid the $40 shipping to have one router repaired. It came back as a different unit and things have worked well since. 5GHz is basically garbage but the WiFi6 6Ghz is fabulous. Magnitudes are still way down from whole home routers but the 1200 (even on 2.4GHz) and 2400Mbps connections are nice. The AC68u is being scrapped as an antenna finally broke off and it will not mesh anymore, which I cannot be bothered with. My old Netgear router runs circles around both my Ax92u units for my 35+ Magic Home lightbulbs and RGBW strips. They never disconnect now. Strange thing about these routers is when a WAN problem would happen they seemed to shut down the WiFi systems. When a bad router acted up the other router would disconnect from the WAN. It was very hard to pin down and I never really did. I suggest you find out which router is causing you problems (or best guess) and contact ASUS. They have put out some real bad models and they know it. Since I have contacted a few router companies and tried to find out how many connection their models can support. After a lot of garage answers about WiFi etc. I have discovered...they don't know. Support people don't even know what you are talking about.

If you want to use the resultant value in a program and be self triggering you need to do your calculations in an Integer variable and then transfer over to a State variable last line to avoid triggering the downstream program with every intermediate result of the calculation process.

yup if $sStatevar is not -99999 then $tempvar = %sStatevar $tempvar *= ratio else ---- You must have v5 to use fractional variables and ratio 230/801 Sent from my SM-G781W using Tapatalk

My mailbox lid gets up to about 54c on sunny days. It hasn't cooked yet though. Sent from my SM-G781W using Tapatalk

The 125V rating may be the North American receptacle configuration for that model.

Hey SG! If you have any Echoes or Google Home speakers, did you know you can install a skill for the Wireless Tags that you can just ask... ...Alexa! what is the TagName temperature? When asked the humidity, it replies "not available yet" but you will get the temperature back in thousandths of a degree. Nothing to do except hook the two accounts together on a prompted questionnaire.

Zwave appears to be the most popular protocol being sold and used right now. If you ever decided to migrate the polisy/IST994 it would be quite easily done and lives with WiFi devices mostly also.

Geeesh! You're right. This was a screen shot from a few years ago. Maybe I corrected that. hmmmm... I must have anew look now. Thanks! Update: I guess I worded that incorrectly. The "z" causes them to sort at the end of the constants "c" prefixed variables. I had so many variables to sort through in a small dropdown menu list I was trying to get some out of the way of every day programming needs. (reduce scroll hunting) I have since dumped the "z" subprefix as I have removed a few brands of RGBW bulbs and I only require constants for my MagicHome bulbs and strips now.

I wonder how the RF handles the mesh and hops. Just fire at random until you don't hear any interference, like Ethernet?

I guess the question in my mind then is: are the RF hops synchronised or not? I would think they may be synchronised with the powerline hops (each zero crossing) but cannot be using a simulcast technique. The RF frequency is too high to phase lock between devices, based on a 60Hz waveform zero crossing and would mostly be out of synch, confusing other signal senders. Powerline tech at 161 kHz? is obviously possible but different on 900MHz. Obviously Insteon RF is not self-reinforcing signals, as the powerline signals are but the RF may still be packet synced with powerline packets. Mesh packats need to not get ahead of each other.

That does seem to negate what I posted about needing synch on the RF. I believe it was in one of their white papers, but as I have stated before, white papers are usually only conceptual, and many fine details (like actual frequencies etc.) were not what what actually used in Insteon devices. Many tech companies do this to slow down hackers and protect their intellectual concepts. The other thing they do is release older software and then dump a later update on the market, as soon as some eastern country copies and releases it, Now the copy seems out of date, staying one step ahead. I also read somewhere in one of them that a dual band device only transmits RF when it receives a powerline signal and vice versa. I didn't believe that one from the moment I read it but...who knows?

Insteon RF is still based on 60Hz powerline frequency to synch the mesh simulcast....unfortunately. Divorcing the two would likely be a huge improvement in speeds but presents a lot of logical problems to be worked out.

I don't know if there is a 50Hz PLM but all devices would have to be 50Hz models also. Insteon is completely dependent on the powerline frequency. Signals are timed from a previous waveform and waveform period is critical.

Make sure you announce the PLM if you have one. People will be interested!! Sent from my SM-G781W using Tapatalk

The z in the name is so these sort to the last position order when looking for a variable in programming.

Nothing like self documenting code/variable names.

Make sure to set init-to to the same value so it never goes away. Also I found a bug that the last integer variable value gets cleared upon reboot. IIRC this was on ISY v5.3.4 so not likely fixed yet. I installed a dummy extra variable and it stopped disappearing. Sent from my SM-G781W using Tapatalk

I have inherited a 300 Zwave board. it has the LED and not sure if I want to break into Zwave yet but would like to test some things. IIRC it was v5.0.16c ? Do you remember the highest V5 version that can support it?

Gotta' love the way web pages constantly change their style. Just when you get familiar with something it changes locations again. Now feature buttons at the bottom of the pages where browsers sometimes can't even display them?

I have just started to try ISY on polisy. My LAN just became stable after a few years of fighting with three defective routers, so I have delayed trying to port ISY over to polisy until now. I didn't think it would get more complicated than this.

Not likely for hours Only the upgrade itself has been run. Here is what happening. I just noticed it complaining of a package not found. [admin@polisy ~]$ sudo pkg update Password: Updating FreeBSD-base repository catalogue... pkg: https://pkg.isy.io/FreeBSD-base/FreeBSD:13:amd64/latest/packagesite.pkg: Not Found FreeBSD-base repository is up to date. Updating udi repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 107 KiB 110.0kB/s 00:01 Processing entries: 100% udi repository update completed. 399 packages processed. All repositories are up to date. [admin@polisy ~]$ sudo pkg upgrade Updating FreeBSD-base repository catalogue... pkg: https://pkg.isy.io/FreeBSD-base/FreeBSD:13:amd64/latest/packagesite.pkg: Not Found FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. process with pid 1877 still holds the lock process with pid 1877 still holds the lock process with pid 1877 still holds the lock process with pid 1877 still holds the lock process with pid 1877 still holds the lock process with pid 1877 still holds the lock pkg: Cannot get an advisory lock on a database, it is locked by another process [admin@polisy ~]$

Thanks but it didn't change the errors reported. In addition: pkg: Cannot get an advisory lock on a database. It is locked by another process